No. SleekRank reads from your data source. If your sheet pulls APYs via a script or formula on a schedule, those flow through on the cache cycle. SleekRank does not scrape bank pages or call APIs directly. The pattern is a separate import job that updates the sheet, and SleekRank renders whatever is current in the source after a cache flush.

Both page groups read from the same HYSA sheet. The pairs page group joins two rows at render time using the slug pair from a pairs sheet. A row edit propagates to wherever the account is referenced after the cache cycle, including every pair page where the account is product_a or product_b. The data layer enforces consistency that manual page editing cannot.

Create a separate page group at /hysa/top-10/ that reads the same HYSA sheet, sorts by current APY descending, and renders the top ten rows in a ranked table via list mapping. The leaderboard updates with the same cache cycle as the per-account pages, so the ranking and the underlying detail pages stay aligned.

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

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

Update the promo_expiration_date column or null out promo_apy. Every page that references the account, including per-account, every pair page where it appears, and any leaderboard, reflects the change after the cache window. For automated rollover, a script can compare expiration_date to today and null the promo columns automatically before SleekRank reads them.

Add partner_bank, fdic_pass_through, and partner_bank_change_history columns. Render the partner-bank disclosure on the per-account page via tag mapping, and include it on pair pages so readers see whose certificate insures their deposit at each option. Partner-bank migrations are common on fintech HYSAs, and a single sheet edit propagates the disclosure update.

Yes. Store a time series of historical APYs in a separate JSON file keyed by account slug and render it as a chart via a chart library on the base template. The page reflects current APY from the main row plus historical context from the side dataset, joined at render time, which helps readers spot accounts that consistently lead versus those that bait with a one-month promo.