No. SleekRank reads from your data source. If your sheet has a script that pulls published carrier scorecards or industry benchmark data, those flow through on the cache cycle, but SleekRank does not scrape carrier sites or call EDI feeds. 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 carrier sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a carrier row updates every page that references the carrier, including per-carrier, pair, and any lane 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 lanes_served array. A /freight/california/ page filters carriers serving California, and a /freight/cross-border-mexico/ page filters carriers that include Mexico in their lanes. Each cut is a real landing page rendered from the source.

Yes. The service_types array on each carrier row holds whichever modes apply. The template can render a service block per mode, and cut pages like /freight/ltl/ or /freight/ftl/ filter the same source by service type. A carrier that runs LTL and intermodal appears on both cut pages without duplication.

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

Update the parent_company column and any related lane or service fields in the sheet. Every page that references the carrier, per-carrier, every pair, and any lane 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.

Yes. Map an image URL column to og:image with the meta type, so each per-carrier page renders its own social card. For per-pair pages, you can render both carrier logos side by side. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying name, service types, and on-time performance 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 carrier. 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 preserve link equity. The Yellow Corp shutdown was exactly this kind of event, and a single row change there is far cheaper than a thirty-page sweep.