If the platform exposes JSON or a REST endpoint your WordPress server can reach, SleekRank can read it on the configured cacheDuration. Most directories normalise data from PartySlate, Honeybook, or direct venue feeds into an internal sheet first, then point a SleekRank page group at the normalised feed so the page schema stays consistent across venues.

Add a status column with values like active, booked-out, 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 couples searching the venue still find context plus alternatives in the same region.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic cards combining hero photo, capacity, and region. The meta mapping passes the asset URL per row so each venue 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 venue slug through hidden form fields so each enquiry lands in your pipeline tagged to the specific venue without manual matching.

Yes. Store peak, shoulder, and weekday pricing tiers as an array column and food and beverage minimums as separate scalar fields, then use a list mapping for the tier table and selector mappings for minimum-spend copy. The base page renders both blocks from the same row.

Add capacity-band and style columns and reference them in the urlPattern as /wedding-venues/{style}/{slug}/, or run parallel page groups per style with their own base pages. Each group reads the same dataset filtered at the data source level, keeping URLs distinct and rankable per intent.

Pricing reflects the dataset on the next render after cacheDuration expires or you clear the SleekRank cache manually. For engagement-season booking windows with frequent calendar shifts, set cache to hourly. For off-season months with steady inventory, daily 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 the row values into the schema on render so each venue page surfaces valid structured data for venue rich results.