Not directly. SleekRank renders from your data source. If your sheet pulls from a vendor changelog feed or a scraper that watches pricing pages, those numbers flow through on the cache cycle. The import layer lives upstream of SleekRank, which is responsible for rendering whatever is current in the source.

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

Define another page group with a different URL pattern, source from the same sheet, and filter on the relevant column. A /headless-cms/graphql/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Store tier data as separate columns or as a JSON array keyed by tier. List mapping renders the correct lineup per page. A comparison template can show starter pricing on one tab and enterprise pricing on another, all from the same row.

Yes. The pairs sheet has its own verdict column. The per-CMS 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 platform rows' verdict snippets.

Update the owner and brand columns in the sheet. Every page that references the platform, the per-CMS page, every pair, and any category page reflects the new ownership after the cache window. Add a 301 from the old slug to the new slug if the brand name changes the URL.

Yes. Map an image URL column to og:image with the meta type, so each per-CMS page renders its own social card. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying platform name, tier, and price on a styled background.

Add a discontinued flag and a successor_slug column. The template renders a sunset banner via selector mapping when the flag is true, and the successor field links to the recommended replacement. Add a 301 redirect to the successor page to preserve link equity.