InHomeDayCareMap
I designed a directory for licensed in-home daycare providers with crawlable geography, a useful map, normalized imports, and privacy rules for home-based locations.
What needed to change
A useful provider directory has two different consumers: people need fast geographic discovery, while crawlers need stable state, city, facet, and provider paths that do not depend on the map UI.
The constraint shaping the build
Provider locations can be sensitive. Search discovery, structured data, imports, and freshness checks must work without exposing precise private-home coordinates.
See whether this starting point fits your workflow
The matching system explains who it is for, what a first release includes, and the rough cost. Supporting links show the implementation evidence.
How I built it
- Separate crawlable state, city, facet, and provider resources from the interactive map layer.
- Normalize provider imports and track source freshness before generating public routes.
- Use approximate locations and explicit privacy rules for sensitive provider records.
- Generate JSON-LD and size-limited sitemaps from the same canonical route model.
What I verified
- Provider import normalization
- State/city/facet/provider route model
- Live search and map UI
- Approximate-location handling
Current state: The architecture and route model exist. This is not presented as a live directory or a traffic result.