SleekRank renders whatever the data row carries, including pre-computed worked examples. For interactive input where readers type principal, rate, term, taxes, and insurance, ship an Alpine component on the base page that runs the standard amortization plus taxes-and-insurance formula. SleekRank handles the static SEO surface; the widget handles ad-hoc input.

Store rate ranges per scenario in the sheet and refresh them on a daily or weekly cadence depending on volatility. SleekRank caches per cacheDuration; setting it to a day keeps pages aligned with the sheet without thrashing. Editors update one row, every page picks up the change on cache flush.

Treat lender-specific quoted rates as their own page group with one URL per lender. Mortgage scenario pages give the typical range across the market; lender pages give one URL per lender with current advertised rates. Separate groups keep templates focused.

Either add a state column to the scenario sheet and split slugs like fha-loan-california, or build a sibling page group at /mortgage-programs/{state}/{slug}/ for state-specific scenarios. The choice depends on how many states have program variants worth a dedicated URL.

ARMs need extra columns: initial rate period, adjustment frequency, rate cap, lifetime cap. Add them to the sheet and render them via selector mappings only on rows where loan type is ARM. The template stays the same; the ARM-specific block renders only when those fields are non-empty.

SleekRank caches the source per cacheDuration set in seconds. Edit the sheet, clear the SleekRank cache via WP-CLI or admin, and the next request rebuilds the page with new data. For market-sensitive ranges, set cacheDuration to a day so updates land quickly.

Yes. Each generated URL is a real WordPress page included in the sitemap. The base template is excluded automatically so the scaffolding does not compete with real calculator pages. Run a rewrite flush after adding new slugs so the routes resolve immediately on production.

Yes, but that's a comparison hub rather than a per-scenario URL. Build /mortgage-calculators/ as a comparison table that pulls from the same sheet and shows term, rate range, and down-payment across scenarios. SleekRank handles the detail pages; the hub uses the same source as the single point of truth.