Not directly. SleekRank renders from your data source. If your sheet has a script that scrapes a platform's release notes or pulls from a published API, those values 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-platform, 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 boolean column. A /kubernetes/gpu-nodes/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Store mode data as separate columns or as a JSON object keyed by mode. List mapping renders the correct pricing per page. A comparison template can show side-by-side Standard pricing on one tab and Autopilot pricing on another, all from the same row.

Yes. The pairs sheet has its own verdict column. The per-platform 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 brand and slug columns. If the URL slug changes, add a 301 redirect from the old slug. Every page that references the platform reflects the rebrand after the cache window, so the catalog stays consistent without manual page edits.

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

Add a discontinued flag and a successor_slug column. The template renders a retirement 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.