It depends on cacheDuration. Set it to 5 minutes for trackers people refresh frequently, or 1 hour for goals updated daily. SleekRank re-reads the sheet on the first request after the cache expires; subsequent requests within the window serve the cached value. Trade between data source quota and freshness.

Yes. Compute the percent on the row using a sheet formula (current_value / target_value), or use selector mapping to inject both values into the template and have a small inline script compute width. Either way, no per-page coding is needed; the same template renders the bar for every tracker.

Yes. SleekRank renders on top of any WordPress page, including those built with Bricks, Elementor, Gutenberg, or a custom theme. Build the tracker layout once on the base page and SleekRank handles per-row replacements through the mapping system without altering theme files.

Yes. SleekRank emits every generated URL into its sitemap and noindexes the base template page automatically. Submit the sitemap once in Search Console; new tracker rows start getting crawled after the next rewrite flush. Indexation quality depends on each tracker having real context and history, not just a number.

Yes. Add a layout or section_flags column on the milestones sheet and use selector mapping to inject or hide template fragments per row. A tracker with no history yet hides the timeline section; a fundraiser tracker can show a donor count block that a fitness tracker omits.

Delete the row from the sheet and flush the cache. The /tracker/{slug}/ URL stops resolving and returns a clean 404. If the page had backlinks, set up a 301 in your redirect plugin to a retrospective or a parent tracker page to preserve link equity before pulling the row.

Not if each tracker carries a real goal with real numbers and real history entries. The sheet structure forces goal_name, current_value, target_value, and history rows to be distinct per tracker; the work of writing context and logging milestones is what separates a tracker hub from a templated stub.

Yes. Trackers often write back to the sheet from a cron or a webhook, like a Stripe webhook that updates current_value when MRR changes, or a Strava integration that updates a training tracker. SleekRank reads whatever the sheet currently says, regardless of who or what wrote it last.