Yes, indirectly. Keep primary_model and a model_changed_date column in the sheet, and let your editorial team update them as the vendor announces a default swap. SleekRank reads whatever is in the source on the cache cycle, so the propagation is automatic once the row is updated. The detection itself is upstream of SleekRank, which handles the render layer.

Both page groups read from the same assistants sheet. The IDE group joins every assistant supporting a given editor at render time using an IDEs sheet. A change to an assistant row updates every page that references it, including per-tool, per-IDE, 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 a language_strengths array. A /code-ai/python/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Add columns for agent_mode_supported, tool_use_supported, file_edit_scope, and shell_access. The template renders an agent capability block via selector mapping, and a /code-ai/agent-mode/ landing page can list the relevant assistants as a separate page group filtered on the flags.

Yes. The IDEs sheet has its own verdict column. The per-tool verdicts handle solo pages, and the IDE verdict drives editor-specific recommendations. If an IDE row's verdict is empty, the template can fall back to a templated summary built from the top three assistants' verdicts.

Add columns for code_retention, training_data_use, and enterprise_privacy_addendum. The template renders a privacy block via selector mapping, so readers see the same disclosure shape across the catalog regardless of which editor wrote the original review.

Yes. Map an image URL column to og:image with the meta type, so each per-tool page renders its own social card. For per-IDE pages, you can render the IDE logo or a feature visualization. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying tool name, primary model, and context window on a styled background.

Add columns for self_hostable, on_prem_supported, and air_gapped_option. The template renders a deployment block via selector mapping when relevant, and a /code-ai/self-hosted/ landing page can list the relevant assistants as a separate page group filtered on the flag for security-conscious teams.