No. SleekRank reads from your data source. If your sheet has a scraper or import job that pulls lender rate pages, those flow through on the cache cycle, but SleekRank does not call lender APIs or scrape sites directly. The right pattern is a separate import process that updates the sheet on a schedule, ideally weekly or after major Fed announcements.

Store prequalification_tiers as a JSON column with tier_name, new_estimated_apr, used_estimated_apr, and refi_estimated_apr per tier. The per-lender page renders a prequal estimate table from list mapping, and per-credit-tier landing pages at /auto-loan/credit-tier/{tier}/ filter to only show lenders whose prequal tiers include the current tier.

Store ev_loan_supported as a flag column and ev_apr_adjustment as a discount column. A second page group at /auto-loan/ev/ filters lenders whose ev flag is true, and the per-lender page conditionally renders an EV section with the rate adjustment when present. EV financing has become a distinct vertical and rewards its own landing pages.

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

The template can include a JavaScript loan calculator that reads the lender's APR range and term lengths from a data attribute on the page, which selector mapping fills from the row. Users adjust loan amount and term, and the calculator renders monthly payment for that specific lender's rate range. The widget is template-level; the lender-specific bounds come from the data.

Set a status column to discontinued and the template conditionally renders a closure notice in place of the apply CTA. The per-lender page stays live for historical reference but no longer offers commission-generating links, and pair pages where the lender appears can be deprecated via a second status check on the join.

Store membership_required as a flag column and membership_eligibility as a JSON array with eligibility paths (military, geographic, employer, family). Selector mapping injects a membership badge on every lender page, and a separate page group at /auto-loan/credit-union/ filters lenders whose membership flag is true.

Yes. The refinance variant page at /auto-loan/{lender}/refinance/ uses the refi_apr_range column and can include scenario-specific content (lowering rate, extending term, removing co-signer). Store typical_refi_scenarios as a JSON array per lender and list-map them onto the refinance variant page, with rate-impact estimates per scenario.