No. SleekRank reads from your data source. If your sheet imports fees from a scraping script or a partner API, those numbers flow through on the cache cycle. The scrape is upstream of SleekRank, which is responsible for rendering whatever is current in the source consistently across solo and pair pages.

Both page groups read from the services 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 category roll-ups, after the cache window expires.

Define another page group with a different URL pattern, source from the same matrix, and filter on the coverage_cities column. A /food-delivery/austin/ landing page becomes its own SEO target with the matching subset rendered from the source. Per-cuisine or per-feature cuts work the same way.

Yes. Store the perks as a structured list per row, then render via list mapping into a dedicated perks block. Services without a subscription render an empty block or skip the section conditionally. Update the list in the sheet, and every page that references the service reflects the new perks on the next cache flush.

No. The verdict is yours, written in the sheet. SleekRank does not generate content, it injects content. For longer verdicts, store them in a separate JSON file keyed by service slug and join at render time. The render layer is mechanical; the editorial layer is yours.

Yes. Map an image URL column to og:image with the meta type. Each per-service page renders its own social card. Pairing with SleekPixel lets the OG image render dynamically from the row, overlaying service name, subscription tier, and starting fee on a styled background.

Update the coverage_cities column to remove the affected market, or set a status flag on the service. The template can render a not-available-in-your-city notice via selector mapping when the user's city is not in the coverage list. For a full shutdown, remove the row, and the URL stops generating on the next cache flush.

Add a promo_sub_price and promo_expires column. The template renders the promo price when the expiry has not passed and falls back to the standard subscription price afterward, via selector mapping with conditional logic. A weekly script can clear expired promos to keep the catalog from showing stale deals to readers who would lose trust on click-through.