If your booking platform exposes a JSON or REST feed your WordPress server can read, SleekRank renders from it on the configured cacheDuration. There is no direct integration with Boatsetter, GetMyBoat, or Anchor. Most marinas build a small middleware that exports nightly into a JSON feed the page group reads.

Use a status column and drop rows from the feed at the urlPattern level so they fall out of the directory, or hide the booking block via a conditional in the base page while keeping the URL alive. The second pattern preserves accumulated backlinks and lets the URL flip back to bookable when the pontoon launches in spring.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel for dynamic listing cards combining length, capacity, lake, and a hero shot. Configure the meta mapping in the page group and each pontoon gets a unique social card for shares in lake-community Facebook groups.

No. SleekRank renders pages and does not process forms or payments. Use your existing booking widget or form plugin embedded in the base page, passing the pontoon slug through hidden form fields so reservations land in your pipeline tagged to the right boat without manual matching against the dock log.

It updates as quickly as cacheDuration allows. Set the cache low for active season, often fifteen to thirty minutes, and clear the SleekRank cache manually for instant updates after holiday rate jumps. Pages reflect the feed value on the next request after cache expiry, so cache hit rates should align with your update frequency.

Yes. Use multiple page groups, each with its own base page and urlPattern. Standard pontoons route through one page styled for family day-rentals while tritoons route through another with watersports specs and tow capability blocks. Both groups read the same fleet sheet, filtered at the data source level by boat class.

Store photo URLs in a JSON array on the row pointing at a CDN or your media library. The list mapping renders them in a gallery block on the base page. SleekRank does not host the photos, so even twenty-photo pontoon pages stay lightweight because the actual media loads from the CDN on demand.

Yes. Run multiple page groups, one per lake, each pointing at a lake-specific feed and a base page tuned to that lake. Lake of the Ozarks gets /ozarks/pontoons/{slug}/, Lake Lanier gets /lanier/pontoons/{slug}/. Both groups can share inventory but render with lake-specific copy, dock photos, and local SEO.