No. SleekRank reads from your data source. If your sheet pulls CD APYs via a script 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 CD 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 CD is referenced after the cache cycle, including every pair page where the CD is product_a or product_b. The data layer enforces consistency that manual page editing cannot.

Create a page group at /cds/{term}/ that filters the CD sheet by term and ranks rows by APY descending. A six-month, one-year, three-year, and five-year leaderboard page can all read from the same sheet with different filters, and the per-CD detail pages link back from each term page.

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 CD 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 CD page can render a custom social card via that mapping. For dynamic per-CD OG images that overlay APY, term, and early-withdrawal penalty over a styled background, pair with SleekPixel which renders OG images from data on the fly.

Add the promo as a new row with a distinct slug and a promo_expiration_date column. Every leaderboard and pair page sees the new CD at the next cache cycle. When the promo expires, edit or remove the row, and the catalog reflects the change without manual edits to dozens of pages.

Add a special_feature column with values like standard, no_penalty, step_up, bump_up, callable. Render the feature pill on the per-CD page via tag mapping, and include it on pair pages so readers see the structural difference at a glance. A separate page group at /cds/no-penalty/ can filter the sheet for that feature.

Yes. Create a separate page group at /cds/ladder-examples/ that combines multiple CD rows into ladder structures, joining the CD sheet on bank and term. Each ladder example shows the constituent CDs with current APYs, blended yield, and rollover schedule, all driven from the same source so the ladder examples stay current as individual CD rates move.