Not natively. If you connect a reservation REST API — Recreation.gov has limited public endpoints, some state systems publish their own — SleekRank refreshes that data at the configured cache interval, and pages update on the next request. For true real-time availability, embed the vendor widget on the base page; SleekRank handles the static fields around it.

No. SleekRank renders pages from data and links out to whatever reservation system the campsite uses — Recreation.gov, ReserveAmerica, individual state park portals, or first-come walk-up notes. The CTA button URL comes from the row, so a system migration is a column edit, not a page-by-page rewrite.

Define a fixed amenity vocabulary in the sheet (electricity, water, dump-station, showers, flush-toilet, vault-toilet, pet-friendly). The list mapping renders them with the same labels and icons on every page. A data validation rule on the column prevents editors from typing 'restrooms' on one row and 'washrooms' on another, which is the most common drift in manual campsite directories.

Yes. Add the column in the sheet, add a tag or selector mapping pointing to a target element on the base page, flush the cache, and every campsite page picks it up — no per-page editing. This is exactly the kind of incremental field that breaks manual directories and is trivial in a data-driven setup.

Reference image URLs in the data row and inject src attributes via selector mappings. SleekRank doesn't host images. Most sites use a hero_image and a gallery array column, point at the WordPress media library or a CDN, and let the base page handle the gallery markup. Pair with SleekPixel for per-campsite OG cards.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page so only campsite URLs get crawled. New campsites added to the sheet appear in the sitemap on the next cache refresh, useful when a state park system opens a new loop.

Add a status column (open, seasonal-closed, fire-closed, maintenance) and use a meta mapping to set robots=noindex when the value isn't open. The closed page still renders for direct visitors with a closure notice, but the sitemap drops it on the next refresh. When the closure lifts, flip the column back and the URL returns.

Yes. Add max_rv_length and slide_out_allowed columns to the sheet and use tag mappings or icon selector mappings to render them. For more granular per-loop restrictions, use an array column with one object per loop containing pitch numbers and length limits — a list mapping renders the table on the base page.