Yes. Run a second page group with /house-swaps/{month}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows where swapStart falls inside the month bucket and renders matching properties.

When a row's swapEnd date passes, either remove the row or filter it out at the data source. The URL returns 404 on the next cache refresh and the sitemap regenerates. If you want past swaps to remain as social proof, route them to /past-swaps/{slug}/ via a second page group.

Yes. Store amenities as a JSON array column. A list mapping renders them as badges on the page. Crawlers see pool, central, family-friendly, or ski-near in the HTML, which lifts ranking for amenity-specific searches.

Add a hostRouting or inquiryRouting column with the host's email. Inject the value into a hidden form field via a selector mapping. Inquiries on each property URL go to the correct host automatically.

Map fields to a JSON-LD Accommodation block via a meta mapping. Address, number of rooms, amenity feature, and dates fill in per property. Validate one page with Google's Rich Results Test, then the template covers the entire corpus.

Each region hub lists different properties, different dates, and different amenities. Give each one a unique meta description and intro paragraph driven by the region row, and the corpus reads as a real travel directory rather than a templated swap.

Yes. Configure a form that writes a row back to the same Google Sheet. The new row appears on the next cache refresh and the URL goes live. Add a status column with values like pending and approved if you want an editor review step before pages publish.

Store image URLs as a JSON array column. A list mapping renders them into whatever gallery block lives on the base page, whether that is a slider, lightbox, or grid. The data supplies URLs; the gallery design lives in WordPress.