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 the monitoring_categories array. A /identity-theft-protection/dark-web/ page filters services whose array includes dark web monitoring, and a /identity-theft-protection/social-media/ page filters for social monitoring. Each cut is a real landing page rendered from the source.

Yes. Add a family_plan flag, family_members_supported integer, and family_price_per_month columns. The template can render a family plan block per service when the flag is true, and a /identity-theft-protection/family/ cut page filters services that support family coverage. The row drives both single and family page types without duplicating data.

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.

Add a parent_company column and let the template render the corporate context per service. LifeLock under Norton, Identity Guard under Aura, and the Allstate-owned services each carry different operational implications, and a clear parent_company field keeps that context consistent across per-service and pair pages.

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, insurance amount, and monitoring scope 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.