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 membership and events platforms into an internal sheet first, then point a SleekRank page group at the normalised feed.

Add a status column with values like active, off-bloom, and closed, then use a conditional in the base page to flip the enquiry block for a next-season block while keeping the URL alive. The URL retains accumulated backlinks and ranking history, and couples searching the garden still find context plus the next bloom window.

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

Yes. Store bloom estimates as a versioned array column, then use a list mapping for the calendar block. The base page renders the current and forecast bloom windows from the same row without conditional templates.

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

Bloom updates reflect the dataset on the next render after cacheDuration expires or you clear the SleekRank cache manually. For peak bloom weeks with weekly horticultural updates, 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 garden page surfaces valid structured data for venue rich results.