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 provider 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 provider sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a provider row updates every page that references the provider, including per-provider, 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 integrations column. A /invoice-financing/quickbooks/ page filters providers whose integrations array includes QuickBooks, and a /invoice-financing/shopify/ page filters by Shopify. Each cut is a real landing page rendered from the source.

Yes. Add a financing_type column with values like financing, factoring, or hybrid. The template can render a clarifying block when financing_type is factoring, since the legal structure differs (true sale of receivable versus a loan against receivables). The same data source can drive both /invoice-financing/ and /factoring/ page groups with different filters.

Yes. The pairs sheet has its own verdict column. The per-provider 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 provider rows' verdict snippets, so the wording is yours to control per pair.

Update the weekly_fee_min and weekly_fee_max columns, and add a pricing_model column with values like flat or tiered. The template can render different copy and disclosure blocks based on pricing_model, and the pair page can show the model comparison side by side. This is the kind of structural change that breaks manual reviews until each page is rewritten individually.

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

Update the parent_company column and any related pricing or integration fields in the sheet. Every page that references the provider, per-provider, every pair, and any category page, reflects the new ownership after the cache window. This is the dimension manual builds drift worst on because nobody propagates ownership changes across dozens of pages by hand.