No. The amortization math runs in your existing calculator widget, whether that is a JavaScript block, an iframe, or a hosted tool. SleekRank only generates the state-specific landing page around the widget. It reads rate and tax rows from your sheet and renders the intro, rate averages, property tax notes, and FAQs unique to each state, then drops your existing embed into the same place on every page.

Yes, if your calculator widget accepts query-string presets. Map the avg_rate and property_tax_rate columns onto the iframe src or anchor parameters through a selector mapping. Each /mortgage-calculator/{state}/ loads the calculator with that state's average rate and property tax already filled in, so visitors get a meaningful estimate without typing.

Weekly is the common cadence because Freddie Mac publishes its Primary Mortgage Market Survey every Thursday. Set the SleekRank cacheDuration to 86400 seconds and run a Thursday-evening cache flush after updating the sheet. Daily refresh is overkill for averages but useful if you also surface a real-time rate ticker from a separate feed.

Each state row carries distinct intro copy, homestead and exemption notes, related-state links, and at least three state-specific FAQ entries. Texas and Oklahoma might use the same calculator and similar rates, but the homestead rules, closing-cost norms, and local market notes differ enough to make each page substantively unique. Avoid copying placeholder text across states.

Yes. Add a property_tax_table column that stores a list of county or city rows for that state. Use list mapping to render the table on each state page, so /mortgage-calculator/texas/ shows Harris County, Travis County and Bexar County rates while /mortgage-calculator/california/ shows Los Angeles, San Francisco, and San Diego. Each state row owns its own local breakdown.

Store program notes that vary by state in dedicated columns or as an HTML block per row. VA loan funding fees and FHA loan limits change by county, so state pages link to the federal program pages and surface the state-specific limit ranges. The shared calculator usually handles the math; the row carries the state-specific narrative around the embed for context.

Hide or remove the row, flush the SleekRank cache, and the /mortgage-calculator/{state}/ stops resolving. Set up a 301 to your default /mortgage-calculator/ page if the retired state URL had meaningful backlinks. A status column flagged active or archived makes audits easier once you start layering counties or metros on top of the state set.

Yes. Add a second page group with urlPattern /mortgage-calculator/{state}/{county}/ pointed at a county-level sheet. Each county row references its state slug so related-page logic can link counties up to their state and the state down to its counties. The same calculator widget serves both levels because the math does not depend on geography, only the inputs do.