No. SleekRank reads from your data source. If your sheet has a script that pulls published service pages, those flow through on the cache cycle, but SleekRank does not scrape service sites or call APIs. The right pattern is a separate import job that updates the sheet on a schedule, and then SleekRank renders whatever is current in the source on the next cache flush.

Both page groups read from the same service sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a service row updates every page that references the service, including per-service, pair, and any category roll-up, after the cache window expires.

Define another page group with a different URL pattern, source from the same sheet, and filter on features arrays. A /credit-monitoring/dark-web/ page filters services whose features array includes dark web scanning, and a /credit-monitoring/with-vpn/ page filters by VPN inclusion. Each cut is a real landing page rendered from the source.

Yes. Add a free_tier flag and store both free_features and paid_features arrays. The template can render a tier comparison block per service, surfacing what is included free versus paid, and pair pages can compare paid-tier coverage on one side with free-tier coverage on the other. This is common for services like Credit Karma versus Experian where the free tier is the headline product.

Yes. The pairs sheet has its own verdict column. The per-service verdicts handle solo pages, and the pair verdict drives head-to-heads. If a pair row's verdict is empty, the template can fall back to a templated summary built from the two service rows' verdict snippets, so the wording is yours to control per pair.

Update the parent_company column and any related coverage or pricing fields in the sheet. Every page that references the service, per-service, every pair, and any category page, reflects the new ownership after the cache window. Intuit's acquisition of Credit Karma was exactly this kind of change, and a row update is cheaper than a thirty-page sweep.

Yes. Map an image URL column to og:image with the meta type, so each per-service page renders its own social card. For per-pair pages, you can render both service logos side by side. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying name, bureau coverage, and score model on a styled background.

Add a discontinued flag and a successor_slug column. The template can render a discontinued banner via selector mapping when the flag is true, and the successor field can link to the recommended replacement. If you would rather stop generating the URL entirely, drop the row, and the page falls out of the sitemap on the next cache flush. Add a 301 redirect to preserve link equity.