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 Bookalet, SuperControl, or Sykes Cottages. Most heritage operators export inventory nightly into a normalised JSON feed that SleekRank consumes on each cache cycle.

Add columns for era, build year, architect, listed-status, and key historical facts, then map them through selector mappings. Each beacon then carries its full heritage 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 lighthouse cards combining era, region, and rate. Each beacon then gets a unique social card for shares in heritage-travel Facebook groups or bucket-list Pinterest boards.

No. SleekRank renders content and does not process bookings or payments. Add a booking URL or inquiry-form URL column per row and link out via a selector mapping. Most lighthouse stays run inquiry-first booking flows rather than instant booking, so the inquiry link is the standard call to action.

Yes. Run multiple page groups, each with its own base page and urlPattern. Cornish lighthouses route through one page styled for Atlantic-coast positioning, while Hebridean beacons route through another that surfaces remote-island context. Both groups read the same feed, filtered by region at the source level.

Use a status column and a restoration note. Either filter restoring rows out at the urlPattern level so they drop from the directory, or keep the URL alive with a closed-for-restoration block in the base page. The second pattern preserves backlinks across restoration phases, which matters for bucket-list listings that ranked for years.

Yes. Store rate and currency in separate columns and surface them via tag and selector mappings. UK Cornish beacons render "GBP 280/night" while Canadian Nova Scotia lightkeepers render "CAD 320/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.

Update the access column in the feed and clear the SleekRank cache. The change propagates on the next render. For seasonal causeway closures or boat-transfer suspensions, set a temporary access-status note via a selector mapping so guests booking during affected weeks see the on-arrival reality before they commit.