If your booking platform exposes a JSON, CSV, or REST endpoint, SleekRank can read it. Most liveaboard operators export their trip calendar to a Google Sheet that captures availability, pricing, and cabin types, then point SleekRank at the sheet for rendering.

Use a status column with values like available, low-availability, sold-out, and waitlist. The base page surfaces the right call to action conditionally, so sold-out trips show a waitlist form while keeping the URL alive and indexed for the next departure in the same destination.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic trip cards combining destination, dates, dive count, and a hero reef shot. Each trip gets a unique social card for shares in dive groups and trip-planning forums.

No. SleekRank renders pages and does not process bookings or payments. Embed your existing booking form in the base page, passing the trip slug through hidden form fields so the inquiry arrives in your CRM tagged to the right departure date and vessel.

Yes. Store master cabin, twin, and bunk pricing in separate columns and surface them via selector mappings into a pricing block. Each trip page shows the same cabin structure with its own pricing and availability count per tier.

Add a vessel column and group trips by vessel. You can either render the vessel name through a tag mapping on the trip page, or run a parallel page group at /vessels/{slug}/ that lists every trip operating on each vessel with its own dedicated content.

Yes. Add a comma-separated dive sites column and a list mapping, with optional latitude and longitude columns surfaced through a JavaScript map widget on the base page. SleekRank injects the coordinates; the widget renders the map dynamically.

Store an early-bird price and early-bird deadline as columns, surface them via selector mappings, and let the base page render the discount badge conditionally based on whether today is before the deadline. JavaScript on the base page handles the date comparison.