If your reservation tool exposes a JSON or REST feed your WordPress server can read, SleekRank can render from it on the configured cacheDuration. There is no direct integration with specific platforms like Campspot, RMS, or ResNexus. Most users build a small middleware that exports inventory nightly into a JSON feed the SleekRank page group reads.

Use a status column and drop sold or rotated rows from the feed at the urlPattern level so they fall out of the directory, or keep the URL alive with a not-currently-bookable block via a conditional in the base page. The first pattern returns 404 cleanly and the second preserves accumulated backlinks for units returning to the rental pool.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel for dynamic park-model cards combining rate, resort, and layout. Configure the meta mapping in the page group and each unit gets a unique social card for shares in snowbird Facebook groups or RV resort planning forums.

No. SleekRank renders pages and does not process bookings or payments. Add a booking URL column per row and link out to your reservation system, channel manager, or direct-booking widget through a selector mapping. Most operators link to their reservation system's branded booking page so OTA commissions stay manageable.

It updates as quickly as cacheDuration allows. Set the cache low for active inventory, often fifteen to sixty minutes, and clear the SleekRank cache manually for instant updates after peak-season rate moves. Pages reflect the feed value on the next request after cache expiry, so monitor cache hit rates against your refresh frequency.

Yes. Use multiple page groups, each with its own base page and urlPattern. Loft units route through a page styled for single-bedroom plus loft floor plans while two-bedroom deluxe units route through another with floorplan and dual-vanity blocks. Both groups read the same feed, filtered by layout at the data source level.

Each park model lists different layouts, different rates, and different lot views. Give each row a unique lead paragraph and amenity list driven by the row data, and the corpus reads as a real inventory directory rather than a templated swap. The template renders structure, the row data delivers variety.

Store rate and currency in separate columns and map them through tag and selector mappings. The base page renders "$149/night" for US units and "CAD 199/night" for Canadian park models in border resorts. For SEO targeting different markets, also surface a localised rate in the meta-description field so search snippets show the price in the visitor's likely currency.