No. SleekRank reads from your data source. If your sheet has a script that ingests the SBA's quarterly loan volume reports, those flow through on the cache cycle, but SleekRank does not call SBA APIs directly. The right pattern is a separate import job that updates the sheet when each report drops, and then SleekRank renders whatever is current in the source on the next cache flush.

Both page groups read from the same SBA lender 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-up, after the cache window expires.

Define another page group with a different URL pattern, source from the same sheet, and filter on the programs or industry_focus columns. A /sba-loans/7a/ landing page filters lenders whose programs array includes 7(a), and a /sba-loans/restaurants/ page filters lenders whose industry_focus array includes restaurants. Each cut is a real landing page rendered from the source.

Yes. The row schema does not assume a particular charter. Add an institution_type column and let the template adjust copy and badges per type, so non-bank SBLCs, banks, and credit unions get accurate framing in the same comparison set without separate page groups per type.

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, so the wording is yours to control per pair.

Update the plp_status column. Every page that references the lender, per-lender, every pair, and any category page, reflects the new status after the cache window. The template can render a downgrade banner via selector mapping when the status changes, so readers are not surprised by a stale Preferred badge on a comparison page.

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, PLP badge, and annual volume on a styled background.

Add a regions_served array column and a state_coverage column for finer granularity. List mapping renders the coverage on the per-lender page, and a regional cut page group can generate /sba-loans/california/ or /sba-loans/southeast/ landing pages that filter the same source, joined at render time.