Yes, indirectly. Keep a platforms array column in the sheet, and let your editorial team or a changelog monitoring job update it as launches land. 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, not the changelog monitoring layer.

Both page groups read from the same tools sheet. The feature group filters the rows at render time using the automation_features or reporting_features arrays. A change to a tool row updates every page that references the tool, after the cache window expires.

Define another page group with a different URL pattern, source from the same sheet, and filter on a budget_fit column or minimum_recommended_spend field. A /ppc/small-budget/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Add an agency_pricing flag, agency_features array (white_label, multi_client, hierarchy_billing), and account_minimum field. Selector mapping renders the agency-specific badges on every per-tool page, and a /ppc/agencies/ subset filters to tools with agency pricing or features set.

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

Update the parent_company column and a renamed_from field where applicable. Every page that references the tool reflects the new owner after the cache window. For sunsets, add a discontinued flag and a successor_slug column to render a banner and link to the recommended replacement.

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

Store billing_model as flat, percent_of_spend, or hybrid, and add percent_of_spend_rate plus minimum_management_fee fields where relevant. Selector mapping renders the rate range and minimum on every per-tool page, separating tools with disclosed pricing from sales-only quotes.