If the reservation system exposes JSON or a REST endpoint your WordPress server can reach, SleekRank can read it on the configured cacheDuration. Most cruise marketing teams normalise the reservation feed into an internal sailings dataset first, then point a SleekRank page group at the normalised feed so the page schema stays consistent across systems and seasons.

Add a status column with values like open, waitlist, and sold_out, then use a conditional in the base page to flip the fare-from block for a waitlist form or a sister-sailing link. The URL retains accumulated backlinks and ranking history, and travellers still find context plus the closest alternative.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic cards combining ship hero, region, departure date, and fare from. The meta mapping passes the asset URL per row so each voyage gets a unique social card without per-sailing design work.

No. SleekRank renders pages and does not process forms or fare quotes. Use your existing booking platform or enquiry form embedded in the base page through a selector-mapped enquiry URL, so each enquiry lands in your CRM tagged to the specific voyage without manual matching.

Yes. Store suite categories as a JSON array per row with name, sqft, occupancy, and fare from, then use a list mapping to render the category cards. The base page renders the suite grid from the same row without conditional templates per ship class.

Run sibling page groups with /luxury-cruises/{region}/ and /luxury-cruises/{ship}/ as URL patterns, each filtering the same roster at the data source. Mediterranean, Antarctica, and Japan each get a hub; Silver Moon, Seabourn Quest, and Crystal Symphony each get a hub; all from one sheet.

Fares reflect the roster on the next render after cacheDuration expires or you clear the SleekRank cache manually. For early-release windows with weekly fare adjustments, set cache to hourly. For mid-cycle inventory with steady pricing, daily is enough.

Yes. Add a Trip JSON-LD block to the base page template and reference row fields for itinerary, departureLocation, arrivalLocation, offers (price and priceCurrency), and provider. SleekRank pushes the row values into the schema on render so each voyage page surfaces valid structured data for travel rich results.