Not directly. SleekRank renders from your data source. If your sheet has a script that scrapes a provider's order form or pulls from a referral feed, 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 providers sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a provider row updates every page that references the provider, including per-provider, 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 cpu_family or region column. A /dedicated/amd-epyc/ landing page becomes its own SEO target with the matching subset rendered from the source. Per-storage-type cuts work the same way.

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 side-by-side entry-level pricing on one tab and high-end pricing on another, all from the same row.

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

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

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

Add a discontinued flag and a successor_slug column on the plan row. The template renders a retired-plan banner via selector mapping when the flag is true, and the successor field links to the closest current plan. If you would rather drop the URL entirely, remove the row and add a 301 to preserve link equity.