No. SleekRank reads from your data source. If your sheet pulls in sample rates via a script on a schedule, those flow through on the next cache cycle. SleekRank does not scrape OTA sites or call rate APIs directly. The right pattern is a separate import job that updates the sheet, then SleekRank renders whatever is current in the source after a cache flush.

Both page groups read from the same providers sheet. The pairs page group joins two rows at render time using the slug pair from a pairs sheet. A row edit propagates to wherever the OTA is referenced after the cache cycle, including every pair page where the site is product_a or product_b. The data layer enforces consistency that manual page editing cannot.

Add columns for primary_region and inventory_strength_by_region, stored as JSON arrays. The per-site page can render a regional strength block via list mapping, and a per-region page group can filter the sheet by primary_region to generate /booking/asia/ or /booking/europe/ landing pages from the same 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 site slug and join at render time. The verdict text is yours, the render layer is the responsibility of SleekRank.

Yes. Map an image URL column to og:image with the meta type. Each OTA page can render a custom social card via that mapping. For dynamic per-site OG images that overlay the site name and current promo over a styled background, pair with SleekPixel which renders OG images from data on demand. Per-pair OG images can show both logos side by side.

Update the refundable_window and change_fee columns in the sheet. Every page that references the OTA, including per-site, every pair page where it appears, and any category roll-up, reflects the new policy after the cache window. This is the dimension manual reviews drift on hardest, since policy edits rarely propagate across dozens of pages by hand.

Add a bundles column with JSON describing supported bundle types, savings band, and any restrictions. Map it to a structured callout via list mapping, and the bundle block renders consistently on every page that mentions the OTA. A separate page group can target /booking/bundles/{slug}/ for buyers researching bundle deals specifically.

Yes. Store a time series in a separate JSON file keyed by OTA slug and render it as a small chart via a chart library on the base template. The page reflects current fees from the main row plus historical context from the side dataset, joined at render time, which helps readers understand whether a fee change is one-off or part of a trend.