Skip to content

Updated

Proxy for Scraping Google Maps:
Terms, Limits, City IP

  1. Google Maps Platform terms say customers will not scrape Google Maps Content for use outside the services, which covers copying and saving business names, addresses and reviews, and google.com/robots.txt closes most of /maps/ to crawlers.
  2. The documented route to place data is the Places API.
  3. A proxy does not change those rules; where a city-level IP does help is checking how your own listing and local results look from a given city, with a Premium-line connection (US$5 per GB) set to that city, at a low rate.

Check it right after buyingExample output

curl -x http://USER:PASS@HOST:PORT https://ipinfo.io/json

ip
203.0.113.24
country
US
Matches the country you picked
Day 15
203.0.113.24
Same address for the whole term
Example addresses (203.0.113.0/24), not real exits
01 / 08What a proxy can and cannot do here

Read the terms first: they decide what you may collect. A proxy only sets where requests appear to come from.

What a proxy can and cannot do here

A proxy changes where your requests appear to come from. It does not give permission to collect or store data that the terms or robots.txt disallow, and it does not make a collection run any more allowed than it was.

What location does change is what a searcher sees: local results, ratings shown in a city and the order of businesses depend on the viewer location. That is why city-level IPs are used to check how a business appears from a city, for example before and after you update your own listing.

What the terms and robots.txt said when we opened them

What the terms and robots.txt said when we opened them
ItemWhat we readWhat it means for a project
Google Maps Platform Terms, section 3.2.3"No Scraping": the customer will not export, extract or otherwise scrape Google Maps Content for use outside the Services, for example by bulk downloading places information or copying and saving business names, addresses or user reviews; "No Caching" is a separate ruleFor anyone using the Maps Platform, collecting and storing place data this way is against the terms; the supported route is the API within its terms
Google (google.com)Group for all crawlers (*): /search, /maps? and /maps/ disallowed, with Allow exceptions such as /maps/search/ and /maps/@; no /finance rule other than an Allow for /m/financerobots.txt closes most of Maps and Search to crawlers; read it together with the terms, which say more

Sources: Google Maps Platform Terms of Service and google.com/robots.txt, opened 20 November 2026; the Places API (New) overview page was also read. Terms and files change; read the current versions. This is not legal advice.

If you need local business data

Start from the Places API: it is the documented way to read place data, with its own quotas, billing and terms. Plan around the caching and storage rules in those terms rather than around a scraper.

If your goal is to see how results look from a city (your own listing, your competitors' public positions as a searcher sees them), do it as a person would: a few manual checks or a low-rate script, one city per connection, with pauses, and stop at any check page or 429. Do not collect personal data of reviewers.

Confirm the city of your exit before looking at local results

import requests

# A Premium-line connection set to a city, copied from My assets
# (HTTP port 2222; the same login also works over SOCKS5 on 3333).
PROXY = "http://LOGIN:PASSWORD@proxy.proxy302.com:2222"
PROXIES = {"http": PROXY, "https": PROXY}

# Confirm where the exit appears to be before you look at any local results.
info = requests.get("https://ipinfo.io/json", proxies=PROXIES, timeout=(5, 20)).json()
print("country:", info.get("country"), "| region:", info.get("region"), "| city:", info.get("city"))

# Rerun a few times: each new connection can give another IP, and the city should stay the one you set.

Illustrative example: replace LOGIN and PASSWORD. It only reads the exit location from ipinfo.io; it does not collect any Google data.

Set up a city-level check in 4 steps

  1. Step 1: Use the Premium line

    Open Rotating Residential Proxies and pick Premium (US$5 per GB). City choice is on Premium; Budget is country level only, and neither line offers city level in Russia or Singapore.

  2. Step 2: Set the city

    Choose the country, state and city in the Region fields and generate a connection. Copy host, port, username and password from My assets.

  3. Step 3: Verify the exit

    Run the script above or open ipinfo.io through the proxy. Expected: the city you set; small towns and some connections exit at country level.

  4. Step 4: Look as a searcher would

    Open the results in a browser with the proxy set, note what you see with the date, and keep the volume small.

Quick fixes

The results show another city

Check The exit city differs from the one you set, or the connection exited at country level.

Fix Check the exit on ipinfo.io, reconnect and pick a larger nearby city.

Google shows an unusual-traffic page

Check Too many requests, or too uniform.

Fix Stop, wait, and cut the volume; do not rotate IPs to push through.

Results differ between runs

Check Local results change over time and with the viewer.

Fix Save the date and the exit city with every observation and compare like with like.

Google Maps data FAQ

Is it legal to scrape Google Maps?

We do not give legal advice. The Maps Platform terms we read say customers will not scrape Google Maps Content for use outside the services, so read them and consider the Places API.

Which proxy for Google Maps?

For city-level checks of local results, a rotating residential connection on the Premium line set to the city. A proxy does not make disallowed collection allowed.

How do I get local business data without scraping?

Through the Places API within its terms, quotas and billing.

Does city targeting work everywhere?

Not in Russia or Singapore, and small towns and some connections exit at country level; check the exit.

Further reading

Setup guides Proxy302 publishes on GitHub on the same topic:

Reference links

4
  1. Google Maps Platform Terms of Service

    Official documentation · Confirmed on:

    Opened on 20 November 2026: "No Scraping": the customer will not export, extract or otherwise scrape Google Maps Content for use outside the Services, for example by bulk downloading places information or copying and saving business names, addresses or user reviews; "No Caching" is a separate rule

    robots.txt is a crawler-etiquette file and can change; it is not a legal opinion and the site terms may say more.

  2. Google (google.com) robots.txt

    Official documentation · Confirmed on:

    Opened on 20 November 2026: Group for all crawlers (*): /search, /maps? and /maps/ disallowed, with Allow exceptions such as /maps/search/ and /maps/@; no /finance rule other than an Allow for /m/finance

    robots.txt is a crawler-etiquette file and can change; it is not a legal opinion and the site terms may say more.

  3. Places API (New) overview

    Official documentation · Confirmed on:

    Opened on 20 November 2026: the Places API (New) documentation lists search and place-details requests (Nearby Search, Place Details and others) as Google's documented way to read place data, with setup and billing sections.

    Pricing, quotas and terms change; read the current pages before you build.

  4. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts file of the site (dated 10 November 2026), read on 20 November 2026: per-GB prices of both rotating residential lines, traffic does not expire, countries and city targeting, protocols and ports, no free trial.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.