Not directly. SleekRank renders from your data source. If your sheet pulls from a vendor NAV feed 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 ETFs sheet. The pairs group joins two rows at render time using a ticker pair from a pairs sheet. A change to an ETF row updates every page that references the fund, including per-ETF, 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 index_tracked. A /etfs/sp500/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Store sector exposure as a JSON column or a primary_sector field on each row. A /etfs/technology/ landing page filters on that column, list mapping renders the matching tickers, and the same expense and tracking-error columns flow through to each sector page.

Yes. The pairs sheet has its own verdict column. The per-ETF 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 nuance is needed.

Set a closed_date column on the row. Selector mapping renders a closure banner on the affected per-ETF page, and pair pages can either keep the comparison for historical search traffic or drop the fund from the ranking via a template conditional on closed_date.

Yes. Map an image URL column to og:image with the meta type, so each per-ETF page renders its own social card. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying ticker, expense ratio, and AUM on a styled background.

Add prospectus_url and disclosures columns on each row. Selector mapping renders the prospectus link and any required disclosure inline on each per-ETF page. Sitewide regulatory language sits in a global config and renders via a shared footer component so it stays consistent across the catalog.