Yes. Run a second page group with /roommates/{city}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows where city matches the slug and renders matching listings. One sheet, multiple URL patterns, no duplicate maintenance.

Add a householdFilled column. When it equals householdSize, either filter the row at the data source or remove it. The URL returns 404 on the next cache refresh and the sitemap regenerates. If you want past listings to remain as social proof, route them to /past-roommates/{slug}/ via a second page group.

Yes. Configure a form that writes a row back to the same Google Sheet or form-backed table. 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 approval step before pages render.

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

Use a preferences JSON array column to store the listing's stated preferences. Render them through a list mapping. The host is responsible for compliance with fair-housing rules in their jurisdiction; SleekRank renders whatever the sheet provides.

Each hub lists different rooms, different rents, and different available dates. Give each one a unique meta description and intro paragraph driven by the neighborhood row, and the corpus reads as a real local directory rather than a templated swap.

Yes. Store image URLs as a JSON array column. A list mapping renders them into whatever gallery block lives on the base page. The data supplies URLs; the gallery design lives in WordPress.

Update the householdFilled and availableDate columns directly in the sheet. The URL re-renders on the next cache refresh with the latest household status and any updated preferences. Hosts manage the dataset; SleekRank handles the publish step.