Not directly. SleekRank renders from your data source. If your sheet has a script that scrapes ADV Part 2 brochures or you maintain it editorially, those values flow through on the cache cycle. The import layer is upstream of SleekRank, which is responsible for rendering whatever is current in the source consistently across solo and pair pages.

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 supported_account_types array. A /tax-loss-harvesting/joint/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Direct indexing is a related column on each provider row. A separate page group can publish /direct-indexing/{provider}/ from the same source, filtering for direct_indexing_available true and rendering the same broker, fee, and threshold blocks.

Yes. The pairs sheet has its own verdict column. The per-provider verdicts handle solo pages, and the pair verdict drives matchup-specific recommendations. If a pair row's verdict is empty, the template can fall back to a templated summary built from the two solo verdicts. You control the wording per matchup when the recommendation deserves nuance.

Update the minimum_balance_for_tlh column to reflect the new policy or set a not_offered_at_tier flag. Selector mapping can render a notice on the affected per-provider page, and pair pages drop the provider from any TLH-specific recommendation logic on the next cache cycle.

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, management fee, and minimum balance on a styled background.

Add a disclosures column on each provider row and a sitewide footer disclosure component that reads from a global config. Selector mapping renders the provider-specific disclosure on each per-provider page, and the global footer covers general regulatory language that applies across the catalog.