Not natively. SleekRank reads from JSON, CSV, Google Sheets, Notion, or a REST API at the configured cache interval. If you connect a snow-report endpoint as a separate REST data source, base depth and last 24-hour totals refresh on each cache cycle. For true real-time conditions, embed a vendor widget on the base page; SleekRank populates the static fields around it.

Yes. Store green/blue/black percentages as numeric columns or a JSON object in the row, then use selector mappings to set the values on a chart element you've placed in the base template. SleekRank doesn't draw charts itself — it injects values into whatever chart library you're already using, whether that's Chart.js, ApexCharts, or a CSS-only bar.

SleekRank doesn't generate maps. Reference an image URL or PDF link in the data row and inject the src or href via a selector mapping. Many sites store the resort's official trail map URL in a column and link out; others host SVGs in their media library and reference those. Either pattern works as long as the URL lives in the row.

Edit the affiliation column in the source — sheet, JSON, or wherever the data lives — and flush the SleekRank cache via WP-CLI or the admin UI. Every affected resort page re-renders on the next request with the new pass logo and partner footer block. Same flow handles seasonal additions like Ikon Base Plus tier changes.

Yes. Define a separate base page for the comparison view and point its page group at the same source. SleekRank can map array data into table rows, so a multi-resort comparison stays in sync with the per-resort URLs without a second dataset to maintain. List mappings handle the row repetition; tag mappings populate the cells.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page, so search engines only see the per-resort URLs. New resorts added to the sheet appear in the sitemap on the next cache refresh, which is critical when announcing season openings in November.

Either flatten them into one page with array fields for each base area's elevation, lift count, and amenities, or split them into separate slugs (whistler-creekside, whistler-village) sharing a parent. The sheet shape determines URL granularity. Most sites pick one approach per resort and document it in a notes column.

Yes. Add scheduled_open and scheduled_close columns in ISO format and use tag mappings to inject formatted dates into the resort page. For multi-year tracking, use an array column with one entry per season — list mappings render the history as a timeline below the current dates.