Yes, indirectly. Keep a category column plus a warehouse_native flag in the sheet, and let your editorial team update them as the vendor's posture changes. 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 positioning monitoring layer.

Both page groups read from the same CDPs sheet. The use-case group filters the rows at render time using a use_cases array. A change to a CDP row updates every page that references the CDP, including per-platform, use-case, and any category roll-ups, after the cache window expires.

Add a composable flag and a composable_components array. A dedicated /cdp/composable/ page filters the sheet on the flag and renders the components each platform provides (identity, segmentation, activation), letting readers see which tools handle which layer of a composable stack.

Yes. Add columns for mtu_pricing flag, mtu_tier_breakdown JSON, and starting_mtu. Selector mapping renders the pricing model on every per-platform page, and a /cdp/transparent-pricing/ subset can filter to vendors with disclosed tier breakdowns, separating them from sales-only CDPs.

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

Update the parent_company column and an acquired_at field. Every page that references the CDP 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-CDP page renders its own social card. For use-case pages, you can render the use-case icon or a sample data flow. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying CDP name, category, and integration count on a styled background.

Store integrations as an array of objects with name, category, and minimum_tier fields. Selector mapping renders the integration list with a tier badge on each pill, so readers see at a glance which destinations require an enterprise contract versus which are available on the starter plan.