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 Streamline, Track, or Escapia. Most lake-region managers export the inventory nightly into a normalised JSON feed that SleekRank consumes on each cache cycle.

Yes. Add a lake column and use it in the urlPattern as /lake-houses/{lake}/{slug}/, or run a single flat tree with the lake column surfaced via tag and selector mappings. Multi-lake operators typically prefer the nested tree because it lets each lake accumulate its own SEO equity around the lake name.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel for dynamic lake-house cards combining lake, sleeps, and rate. Each home then gets a unique social card for shares in lake-house enthusiast Facebook groups or family-vacation planning WhatsApp threads.

No. SleekRank renders content and does not process bookings or payments. Add a booking URL column per row and link out via a selector mapping. Most lake-region managers link to their 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. Tahoe homes route through one page that emphasises ski-lake-ski cross-season positioning, while Como villas route through another that surfaces lakeside-village context. Both groups read the same feed, filtered by lake at the source level.

Use a season-window column. Either filter closed rows out at the urlPattern level so they drop from the directory, or keep the URL alive with a closed-for-winter block in the base page. The second pattern preserves backlinks across summers, which matters for homes that ranked across multiple boat seasons.

Yes. Store rate and currency in separate columns and surface them via tag and selector mappings. US Tahoe homes render "$680/night" while Italian Como villas render "EUR 920/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 dock column in the feed and clear the SleekRank cache. The change propagates on the next render. For mid-season dock rebuilds or hoist-out periods, set a temporary dock-status note that surfaces through a selector mapping, so guests booking during the affected weeks know what access looks like before they commit.