Fresh as your cache duration allows. A 6-hour TTL means each station's predictions are refreshed every 6 hours from NOAA CO-OPS. NOAA does not change predictions intra-day, so a 12-hour or even 24-hour TTL is plenty for most operational use.

Both work. SleekRank resolves rows on demand by default, so a visitor request to a new station triggers the API call and caches the result. For sitemap completeness most sites pre-warm by running a one-time script that touches every station URL.

Yes. Pass a unit preference from the request or the row to the template and convert the predictions inline. Most US-facing sites stay in feet, but coastal Canada or international sites surface meters with a small bit of branching in the template.

Remove the row from the source. The page stops being routed, the cached prediction expires, and SleekRank stops emitting it in routes. Inbound links can be redirected to the nearest active station through a small Router rule if you want to preserve link equity.

Yes. Create a separate page group with a different URL pattern, like /currents/{slug}/, that points at the currents station subset of the CO-OPS network. The Twig template handles ebb and flood arrows. The two page groups share the same plugin install.

Yes. The row's latitude and longitude flow into a tile map block, and sunrise or sunset comes from a derived field computed at sync time. Both render conditionally so stations without coordinates fall back gracefully.

Set the cache duration to the longest interval acceptable for your use case, typically 6 to 12 hours. SleekRank only hits the API on cache miss, so a 3,000-station catalog with 12-hour TTL costs at most 6,000 calls per day, well below NOAA's free tier.

Yes. Title, meta description, Open Graph, and schema all read from the row, so each station gets distinct metadata. SleekPixel can render an OG image with the station name and next tide time burned in for share previews.