If your booking system exposes a JSON or REST feed your WordPress server can read, SleekRank can render from it on the configured cacheDuration. There are no direct integrations with platforms like SuperControl, Sykes Cottages, or Bookalet. Most heritage operators export the inventory nightly into a JSON feed that SleekRank consumes on each cache cycle.

Add columns for era, architectural notes, listed-building status, and key historical facts, then map them through selector mappings. Each home then carries its full period context on its own URL without you maintaining that copy in WordPress directly. The source of truth stays in the feed, and the long-form content surfaces wherever the base page positions it.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel for dynamic heritage cards combining era, region, and rate. Each home then gets a unique social card for shares in country-house Facebook groups or heritage-travel Pinterest boards.

No. SleekRank renders content and does not process bookings or payments. Add a booking URL column per row and link out to your booking system via a selector mapping. Most operators link to a hosted booking platform widget or a deep link into their channel manager booking page.

Yes. Run multiple page groups, each with its own base page and urlPattern. Georgian townhouses route through one page that emphasises sash-window galleries and rooftop city views, while medieval manors route through another that surfaces stone-walled great halls and grounds. Both groups read the same feed, filtered by era at the source level.

Use a status column and a renovation note. Either filter renovating rows out at the urlPattern level so they drop from the directory, or keep the URL alive with a closed-for-renovation block in the base page. The second pattern preserves backlinks and lets the URL flip back to active when the restoration completes and bookings reopen.

Yes. Store rate and currency in separate columns and surface them via tag and selector mappings. UK properties render "GBP 320/night" while US colonial homes render "$420/night". For SEO targeting different markets, surface a localised rate in the meta-description field so search snippets show the currency a visitor likely expects.

Store photo URLs in a JSON array pointing at a CDN or your media library. The list mapping renders them in a gallery block on the base page. Heritage stays often carry sixty to a hundred photos across rooms, exteriors, and grounds, and SleekRank stays lightweight because the actual media loads from the CDN on demand rather than the WordPress uploads folder.