Yes. Run a second page group with /pet-sits/{animal}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows where animal matches the slug and renders matching assignments. Dog, cat, bird, and exotic hubs all come from one source.

When a row's endDate 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 assignments to remain as social proof, route them to /past-pet-sits/{slug}/ via a second page group.

Yes. Store care notes as a JSON array column with values like daily-medication, senior, exotic, or behavioral-needs. A list mapping renders them as badges. Crawlers see the language searchers actually use when they need specialty care.

Add a sitterRouting or applicationRouting column with the sitter's email. Inject the value into a hidden form field via a selector mapping. Applications on each assignment URL go to the correct sitter automatically.

Map fields to a JSON-LD LocalBusiness or Service block via a meta mapping. Address, service area, animal type, and price range fill in per assignment. Validate one page with Google's Rich Results Test, then trust the template.

Each city hub lists different sitters, different animals, and different dates. 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.

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.

Use a careType column with values like overnight, daily-visit, drop-in, or boarding. Render the value as a badge through a tag mapping. The per-city hub can filter by careType too, so an overnight-care hub renders separately from a daily-visit hub.