Real Estate & Map Portals: Containing Bounding-Box Coordinate Crawl Traps
Every 1-pixel map drag generates a unique coordinate URL (?ne_lat=51.521&sw_lng=-0.138) that traps search bots in millions of empty map states.
Dmitry K., Technical SEO Lead · SEO Space
1. Why Interactive Map Coordinates Destroy Property Portal Crawl Budget
Map-first property portals update URL query parameters (`?bbox=51.48,-0.19,51.53,-0.08&zoom=13`) on every user pan or pinch-zoom gesture. When share links or crawlable pagination preserve those bounding boxes, Googlebot falls into infinite floating-point coordinate loops.
Real organic demand searches named human geographies (`2 bedroom apartments in Eixample`), never floating-point bounding boxes.
- Store map viewport coordinates in hash state (`#map=13/51.50/-0.12`) or `history.replaceState` outside crawlable `<a>` elements.
- Block `?bbox=`, `?ne_lat=`, `?sw_lng=`, and `?zoom=` explicitly in `robots.txt` for legacy links.
- Invest internal links into static Neighborhood, School District, and Metro Station landing hubs backed by clean breadcrumbs.
2. Clean Boundary Separation Between Map Panning & Static Hubs
Keep interactive map fetch endpoints cleanly separated under `/api/map-listings` while SSR hub pages render paginated HTML cards cleanly.
Protect neighborhood hubs and active listings from coordinate query noise.
| Portal Route | Crawl & Index Rule | Internal Link Strategy |
|---|---|---|
| /apartments/berlin/mitte/ | 200 OK · index, follow | Static geo hierarchy & breadcrumbs |
| /map?bbox=52.5,13.3... | Disallow + noindex | JS map state only |
| /property/sold-id-918/ | 200 comparable recs or 410 | Remove from active XML sitemap |
# robots.txt real-estate coordinate block
User-agent: *
Disallow: /*?*bbox=
Disallow: /*?*ne_lat=
Disallow: /*?*sw_lng=
Disallow: /*?*zoom= Need this indexation setup audited on your domain?
Send your website URL. We check raw HTML parity, log crawl hits, canonical discipline, and sitemap architecture manually within 24 hours.