Yes. Run a second page group with /estate-sales/{city}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows where city matches the slug and renders upcoming sales for that metro. One sheet, two URL patterns, no duplicate maintenance.

When a row's sale_end date passes, you can either remove the row or filter it out at the data source. Either way, the URL returns 404 on the next cache refresh and the sitemap regenerates without it. If you want past sales to remain as social proof archives, route them to /past-sales/{slug}/ with a second page group instead.

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

Map fields to a JSON-LD block in the page head via a meta mapping. Sale title, dates, location, and image fill in the Event schema per row. Validate one page with Google's Rich Results Test, then trust the template across the entire corpus.

Use two columns, preview_dates and sale_dates, and render both via selector mappings into different blocks on the page. Search-friendly text can spell both out, while the structured data uses the actual sale window for the Event schema.

Yes. Configure a form that writes a row back to the same Google Sheet. The new row appears in the next cache refresh and the URL goes live without an editor in the loop. Pair with a status column if you want a manual approval step before pages publish.

Each city hub lists different sales, different addresses, and different categories. Give each one a unique meta description and intro paragraph driven by the city row, and the corpus reads as a real local directory rather than a templated swap. Variation comes from the data, not from forced rewrites.

Yes. Build the form once into the base WordPress page using your usual form plugin and inject the sale lead's email or routing ID via a selector mapping into a hidden field. Inquiries on each sale URL go to the correct person automatically.