No. SleekRank reads from your data source. If your sheet has a script that pulls published rate pages, those flow through on the cache cycle, but SleekRank does not scrape lender sites or call rate APIs. The right pattern is a separate import job that updates the sheet on a schedule, and then SleekRank renders whatever is current in the source on the next cache flush.

Both page groups read from the same providers sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a lender row updates every page that references the lender, including per-lender, pair, and any category roll-ups, after the cache window expires.

Define another page group with a different URL pattern, source from the same sheet, and filter on the loan_type column. A /business-loans/term/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source. The same approach works for SBA, line of credit, equipment financing, or merchant cash advance cuts.

Yes. Add columns for is_marketplace flag, partner_count, and representative APR range. For a marketplace like Lendio or Fundera, the per-lender page can render a different layout block when the flag is true, surfacing the partner count and routing model. The pair template can also adjust its verdict logic so marketplace versus direct comparisons are framed honestly.

Yes. The pairs sheet has its own verdict column. The per-lender verdicts handle solo pages, and the pair verdict drives head-to-heads. If a pair row's verdict is empty, the template can fall back to a templated summary built from the two lender rows' verdict snippets. Either way, you control the wording per pair when the comparison deserves it.

Update the relevant columns in the sheet, parent_company, apr_min, apr_max, min_revenue, or time_in_business_months. Every page that references the lender, per-lender, every pair, and any category page, reflects the new facts after the cache window. This is the dimension manual builds drift worst on because nobody propagates policy changes across dozens of pages by hand.

Yes. Map an image URL column to og:image with the meta type, so each per-lender page renders its own social card. For per-pair pages, you can render both lender logos side by side. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying name, APR range, and funding speed on a styled background.

Add a discontinued flag and a successor_slug column. The template can render a discontinued banner via selector mapping when the flag is true, and the successor field can link to the recommended replacement. If you would rather stop generating the URL entirely, drop the row, and the page falls out of the sitemap on the next cache flush. Add a 301 redirect to the successor page to preserve link equity for any backlinks the discontinued lender accumulated.