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_credit_tiers as a JSON column with tier_name and estimated_apr per tier. The per-lender page renders a prequal estimate table from list mapping, and the per-credit-tier landing page at /personal-loan/credit-tier/{tier}/ filters to only show lenders whose prequal tiers include the current tier with an estimated APR.

Store supported_loan_purposes as a JSON array column, then a second page group at /personal-loan/purpose/{purpose}/ filters lenders whose array includes the requested purpose. Each cut is a real landing page with purpose-specific intro copy and the matching subset rendered from the source.

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.

Yes. Map an image URL column to og:image with the meta type. Each lender page can render a custom social card via that mapping. For dynamic per-lender OG images that overlay lender name, current APR range, and minimum credit score over a styled background, pair with SleekPixel.

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 as one half can be deprecated via a second status check on the join.

Store origination_fee_min and origination_fee_max as columns. Tag mapping renders the fee range on every lender page, and selector mapping injects a visual badge for lenders with no origination fee. Pair pages render both lenders' fee structures side by side with a winner indicator on which has lower total cost at typical loan amounts.

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