No. SleekRank reads from your data source. If your sheet has a scraper or import job that pulls provider rate pages, those flow through on the cache cycle, but SleekRank does not call provider 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.

Both page groups read from the same providers sheet. The pairs page group joins two provider rows at render time using the slug pair from the pairs sheet. A change to a row updates wherever that provider is referenced after the cache cycle, including every pair page where the provider is product_a or product_b.

Define another page group with a URL pattern like /hsa/no-fee/ and the same providers sheet as source, filtered to rows where monthly_fee equals 0. The filter logic lives in the page group config, so adding a no-fee HSA to the sheet automatically populates the no-fee landing page on the next sync.

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 provider slug and join at render time.

Yes. Store the fund lineup as a JSON array column with name, ticker, and expense_ratio per fund. List mapping renders the array as a table on every provider page, and a selector mapping injects an average_expense_ratio summary stat. The fund details update wherever the provider appears when the array updates.

Update the investment_provider column and the fund lineup array, and every page that references the HSA, the per-provider page, every pair page, and any category roll-up reflects the change after the cache window. This is the dimension manual builds drift worst on, because nobody propagates investment-side changes across dozens of pages by hand.

Store eligibility tiers as a JSON column with self_employed_supported, employer_groups_supported, and minimum_employer_size. The template renders the correct eligibility section per page, and a per-segment page group at /hsa/self-employed/ filters providers whose eligibility array includes self-employed.

Yes. Store a time series in a separate JSON file keyed by provider slug with apy_history entries (date, rate). Render it as a small chart on the provider page via a chart library on the base template. The current rate comes from the main row, and historical context comes from the side dataset, joined at render time.