No. The schedule math runs in your existing amortization widget, whether that is a JavaScript block, an iframe, or a server-rendered table. SleekRank only generates the variant landing page around the widget. It reads loan rows from your sheet and renders the intro, summary numbers, related-variant links, and FAQs unique to each term and principal pair, then drops your existing embed into the same place on every page.

Yes, if your widget accepts query-string presets. Map the principal, term_years, and typical_rate columns onto the iframe src or anchor parameters through a selector mapping. Each /amortization/{variant}/ loads with the principal, term, and rate already filled in, so visitors see the full schedule on arrival without typing into any input field.

Each variant row carries distinct intro copy, loan-type-specific FAQs, and at least three related-variant links. The 30-year and 15-year mortgage pages might share a template, but the trade-offs they discuss (lower payment vs less total interest) and the typical buyer profile differ enough to keep each page substantively unique. Avoid copying placeholder intros across variants.

Yes. Add columns for extra_payment_savings and biweekly_payoff_delta and render them as summary stat blocks beneath the main schedule. The shared widget handles the base schedule; sheet columns drive the scenario summaries that vary by loan type. Mortgage variants emphasize biweekly payments; auto-loan variants emphasize one-time extra principal.

Add a loan_subtype column flagged fixed, interest_only, or ARM. Use it to switch the schedule template through a selector mapping that injects the relevant disclosure copy and adjusts the table layout. A single page group can serve fixed-rate, interest-only, and ARM variants if the underlying widget supports the variation; otherwise spin up a second page group with its own base page.

Store a loan_limit_note column that varies by principal and year. The 2024 conforming limit changes by county; jumbo variants carry their own underwriting expectations. Render the note as a banner on variants that cross the limit so /amortization/900000-30-year-fixed/ flags the jumbo classification while /amortization/200000-30-year-fixed/ confirms conforming status.

Yes, because the actual amortization math runs in your widget. The sheet stores the balloon amount or the partial amortization note in a column, and the widget honors that value when computing the schedule. The variant page surfaces a balloon disclosure block above the schedule and an FAQ entry that walks through what happens at the balloon date for that specific variant.

Hide or remove the row, flush the SleekRank cache, and the /amortization/{variant}/ stops resolving. Set up a 301 to the closest live variant if the retired URL had meaningful backlinks. A status column flagged active or archived makes the audit straightforward once your variant catalog crosses a hundred rows and assumptions need a periodic refresh.