Not by itself. If you connect a conditions REST API — a partner dive shop's reporting system, a tide or current API, or a custom logger — SleekRank refreshes the data at the configured cache interval and pages update on the next request. For real-time current rating, embed the vendor's widget on the base page; SleekRank handles the static fields around it.

Yes. Add a best_season column in the sheet, add a tag or selector mapping pointing to a target element on the base page, flush the cache, and every dive-site page picks it up. The old pages don't need touching — the data layer drives the new field. This is exactly the kind of update that's painful in a manual setup.

Store depths as numbers in meters in a single column and format them once in the base template — meters with optional feet conversion alongside. Every page renders the same units the same way. Mixing m and ft in the source is the most common cause of dive-site page drift, and a single-column rule eliminates it entirely.

Reference image URLs in the data row, then use selector mappings to set image src attributes on the gallery elements in the base page. SleekRank doesn't host images itself — point at your media library, a CDN, or the dive shop's hosted photos. For OG cards, pair with SleekPixel to generate per-site dynamic images.

Yes. Define a region listing page group whose template aggregates sites by location column, alongside the per-site URLs. SleekRank can read the same Google Sheet or JSON file from multiple page groups, so the region index, cert-level filter pages, and per-site pages all stay in sync from one source.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page so only the per-site URLs get crawled. New sites added to the sheet appear in the sitemap automatically on the next cache refresh, useful when adding seasonal sites.

Add a status column (active, closed, restricted) and use a meta mapping to set robots=noindex when the value isn't active. Alternatively filter closed sites out of the source query. Either approach removes them from the sitemap on the next refresh while keeping the historical row for reference.

Either store cert_level as an array — Open Water for the shallow plateau, Advanced for the deep wall — and render with a list mapping, or split into separate columns for cert_min and cert_recommended and use two tag mappings. Most sites use the array approach because it scales to multi-profile sites like Cenote Dos Ojos.