If the marketplace exposes JSON or a REST endpoint your WordPress server can reach, SleekRank can read it on the configured cacheDuration. Most directories normalise data from Peerspace, Splacer, or direct hotel feeds into an internal sheet first, then point a SleekRank page group at the normalised feed.

Add a status column with values like active, renovation, and closed, then use a conditional in the base page to flip the enquiry block for an alternate-venue block while keeping the URL alive. The URL retains accumulated backlinks and ranking history, and planners searching the rooftop still find context plus alternatives in the same city.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic cards combining hero photo, city, and view. The meta mapping passes the asset URL per row so each rooftop gets a unique social card without per-venue design work.

No. SleekRank renders pages and does not process forms or payments. Use your existing CRM or form plugin embedded in the base page, and pass the rooftop slug through hidden form fields so each enquiry lands in your pipeline tagged to the specific rooftop.

Yes. Store rain-plan capacity and covered area as scalar fields, then use selector mappings for the headline rain plan and list mappings for the covered-area inventory. The base page renders both blocks from the same row.

Add city and view columns and reference them in the urlPattern as /rooftop-venues/{city}/{slug}/, or run parallel page groups per city with their own base pages. Each group reads the same dataset filtered at the data source level.

Pricing reflects the dataset on the next render after cacheDuration expires or you clear the SleekRank cache manually. For peak event windows with weekly calendar shifts, set cache to daily. For winter months with steady inventory, weekly is enough.

Yes. Add an EventVenue JSON-LD block to the base page template and reference row fields for name, geo, address, maximumAttendeeCapacity, and priceRange. SleekRank pushes row values into the schema on render so each rooftop page surfaces valid structured data for venue rich results.