No. SleekRank reads from your data source. If your sheet has a scraper or import job that pulls broker promo pages, those flow through on the cache cycle, but SleekRank does not call broker APIs or scrape sites directly. The right pattern is a separate import process that updates the sheet on a schedule, and then SleekRank renders whatever is current in the source on the next cache flush.

Store promo_expires_at as an ISO date column. The template (or a small filter in the sleekRank/data/item filter on the PHP side) compares it against today's date and conditionally renders the promo block or hides it. Pages where the bonus has expired show a generic Open Account CTA instead, so no stale offer stays live across the catalog after a campaign ends.

Define a second page group with /ira/{broker}/{account_type}/ as the URL pattern and the same providers sheet as the source, filtered by supported_account_types containing the requested type. Each account type page renders the same broker data with type-specific intro copy, and the supported_account_types column drives whether the page generates at all for a given broker.

No. The verdict is whatever you write in your sheet. SleekRank does not write content, it injects content. For longer-form verdicts that exceed a sheet's column-character comfort, store them in a separate JSON file keyed by broker slug and join at render time. The verdict text is yours; the render layer is SleekRank's responsibility.

Yes. Map an image URL column to og:image with the meta type. Each broker page can render a custom social card via that mapping. For dynamic per-broker OG images that overlay broker name, current promo, and fee tier over a styled background, pair with SleekPixel which renders OG images from data on the fly.

Update the parent_company column and any related fee or account type fields in the sheet, or merge the two rows into a single row with a redirect note. Every page that references the broker, the per-broker page, every pair page where it appears, and any category roll-up updates after the cache window.

Store features as a JSON array column (robo_advisor, fractional_shares, mobile_app, research_tools), then list-map it into a features list on every broker page. For a per-feature landing page like /ira/robo-advisor/, define a second page group that filters brokers whose features array includes the requested feature, rendering each as a card on a feature-specific overview.

Yes. Store fee schedules per tier as JSON columns or separate columns (under_25k_fee, 25k_to_100k_fee, over_100k_fee). The template renders the correct schedule per page tier and the comparison template can show side-by-side mass-market pricing on one row and high-net-worth pricing on another, all from the same broker row.