Not directly. SleekRank renders from your data source. If the sheet or a side dataset is updated by a scraper or your editorial team on a regular cadence, the new evaluator list flows through on the next cache cycle. The data acquisition layer lives upstream of SleekRank, which renders whatever is current in the source consistently across solo and pair pages.

Both page groups read from the 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 a per-evaluator side dataset, and join with the platforms sheet via a many-to-many table. A /eval/factuality/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source. The same approach works for toxicity, hallucination, or domain-specific evaluators.

Yes. Use hosting_model with comma-separated values or a side dataset listing each offering per platform. The template renders both options when present and a single mode otherwise. Pricing columns can carry managed pricing while a notes column references the OSS license and self-host operational story.

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. Either way, you control the wording per pair when the comparison deserves it.

Add a status column and a successor_slug column. The template renders a pivot or sunset banner via selector mapping when status changes. Or drop the row entirely so the URL stops generating, and add a 301 redirect to the closest successor to preserve link equity for backlinks the page accumulated.

Yes. Map an image URL column to og:image with the meta type, so each per-platform page renders its own social card. For per-pair pages, you can render both platform logos side by side. Pairing with SleekPixel lets the OG image render on the fly from the row, overlaying platform name, license, and starting price on a styled background.

Store judge_model details in a side JSON file keyed by platform slug, with rows for judge model name, provider, and per-call cost. The template renders a judge model block joined at render time. Changes flow through whenever the side file updates, without bloating the main platform sheet.