Google Maps residential proxies
Google Maps rides on Google's proprietary anti-automation stack, but the harder problem is geographic accuracy: business listings, ratings, "popular times," and the local pack are all computed relative to the requester's location, so the IP's city literally changes the answer. Automated Places and review collection also runs into tight per-IP rate limits and reCAPTCHA on flagged ranges. City-level residential exits give you both the trust and the geo precision to see what a real local user sees.
Local results are location-derived, so accurate Maps collection depends on city- and sometimes ISP-level exits - Premium's country-only rotation returns the wrong metro's listings, which is why this is an Elite job.
Why Google Maps is hard
- Listings, rankings, and "near me" results are computed from the requester's coordinates, so country-only IPs miss the target metro entirely.
- Places and review endpoints are rate-limited hard per IP, throttling review-history and photo collection.
- Google serves reCAPTCHA on flagged ASNs, so datacenter exits fail quickly on any sustained Maps crawl.
- The same business can rank differently block-to-block, so coarse geo produces misleading local-pack data.
How to approach Google Maps with Aethyn
Targeting & session tips
- Always set -city-<name> for local-pack and "near me" queries; -country alone won't place you in the right metro.
- In dense markets, compare multiple neighborhoods since ranking shifts within a single city.
- ISP-level (Elite) exits add trust when collecting large review or photo sets over long sessions.
See the full targeting reference for username suffixes.