Yes. Store weekly rates per week as a JSON array on the row, indexed by week number or season label like "Christmas" or "February half-term". Render the matrix via a list mapping into a table block on the chalet page. Each row in the table shows the date range and the rate for that week.

Use a season column and filter on it in the base page so summer-closed chalets render with a closed-for-summer block while keeping the URL alive for SEO continuity. Re-renaming the slug breaks accumulated backlinks, so prefer the conditional render. The Val d'Isere chalet survives the May-November closure with the URL intact.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel for dynamic chalet cards combining resort, weekly rate, and sleeps. Each chalet gets a unique social card for shares in ski-group WhatsApp chats, ski-club Facebook posts, and corporate ski-week LinkedIn referrals.

No. SleekRank renders pages and does not process bookings or payments. Add a booking URL column per row and link out to your reservation system, sales CRM, or direct-enquiry form through a selector mapping. Most operators link to a sales-form page that captures party size, dates, and dietary requirements.

It updates as quickly as cacheDuration allows. Set the cache to a few hours during the booking window when rates shift weekly with availability, and clear the SleekRank cache manually for instant updates after rate revisions or last-minute discount drops. Pages reflect the feed value on the next request after cache expiry.

Yes. Use multiple page groups, each with its own base page and urlPattern. Catered chalets route through a page styled for chef bios, menu samples, and staff-included blocks while self-catered chalets route through another with kitchen specs and supermarket-delivery notes. Both groups read the same feed, filtered by catering at the data source level.

Each chalet lists different resorts, different sleeps configurations, different catering tiers, and different slope distances. Give each row a unique lead paragraph and amenity list driven by the row data, and the corpus reads as a real chalet directory rather than a templated swap of generic Alpine boilerplate.

Map fields to a JSON-LD LodgingBusiness block via a meta mapping, with amenityFeature entries for ski-in-ski-out, hot-tub, sauna, chef-included, and starRating where the operator categorises chalets by stars. Validate one page with Google's Rich Results Test, then the template covers the entire corpus.