Is it legal to scrape Google Maps?
Scraping Google Maps for business names, addresses and phone numbers is almost always against Google’s terms, whether you use a browser bot or the paid Places API beyond its storage rules. This is not legal advice. The practical risk sits on the account, keys and IP that make the requests. Licensed public registers are usually the better store of record.
What do Google’s terms actually forbid?
Google’s consumer Maps terms and the Maps Platform terms both treat automated extraction of listings as prohibited use. You may not copy, scrape or create a competing database of places from the maps interface. A headless browser that pages through results, a mobile-app replay, or a third-party “Maps scraper” SaaS is the same act: bulk collection of content Google did not licence you to keep.
The paid Places API is not a loophole. It is a licence to display place details in your product under strict caching and attribution rules. Storing names, formatted addresses, phone numbers, websites and reviews as a reusable lead list is typically outside that licence. Place IDs may be kept longer so you can look a venue up again; the human-readable fields usually may not become your CRM. If you need a local copy, read the current Maps Platform terms and the Places field-specific caching table rather than a blog summary.
Why does the risk land on the account doing it?
Enforcement is commercial, not theatrical. Google can disable Maps Platform billing accounts, revoke API keys, and refuse new projects tied to the same identity. Consumer Google accounts used to drive the website can be locked. Downstream, a lead vendor who sold you a scraped file does not absorb that loss; your keys and invoices do.
Civil claims for breach of contract or database rights are possible in some jurisdictions, but the everyday outcome is simpler: the pipeline dies and the list you already stored remains legally awkward to use. A simpler tool — typing a query into Maps yourself, or buying a list from a firm that licences the source — is the better choice when you only need a few dozen local names.
- Account
- The Google identity and billing project that issued the key or signed into Maps. Suspension hits here first.
- Key and quota
- Server or browser keys, referrer locks and daily caps. Shared keys spread the ban to every app that uses them.
- IP and device
- Datacentre ranges, residential proxies and phone farms are easy to fingerprint. A block follows the network, not the script.
- Stored copy
- Names and addresses already in your CRM are still subject to the licence you never had. Deleting the scraper does not clean the file.
What does an IP block look like in practice?
It rarely arrives as a letter. First you see CAPTCHAs, then HTTP 429 and 403 responses, then empty or shuffled result sets. After that, the same IP may load Maps for a human but refuse pagination, or the Places key returns REQUEST_DENIED. Residential proxy pools burn quickly because many tenants already abused them.
Retrying harder makes the fingerprint worse. Backing off, rotating identities, or “just using Selenium like a user” is still scraping if the purpose is bulk extraction. Treat a block as a stop signal, not a puzzle.
| Signal | What it usually means | What it is not |
|---|---|---|
| CAPTCHA wall on pagination | Automated traffic detected | A licence to continue after solving |
| 429 / quota errors | Rate or project limits hit | Proof the data may be stored |
| REQUEST_DENIED on Places | Key, billing or ToS issue | A bug in your JSON parser |
| Empty local results | Soft block or result poisoning | Evidence the venue does not exist |
Which business data can you store and reuse instead?
Use sources that grant a reuse licence in writing. OpenStreetMap place nodes are available under ODbL if you keep attribution and share-alike on the database. National company registers (for example Companies House in the United Kingdom) publish official names and registered offices under stated open-government licences. Some statistical agencies release address products for a fee with clear commercial terms. Trade directories that sell a licence, not a scrape, exist for a reason.
These sets are messier than a Maps pack: fewer phone numbers, slower refresh, more closed shops. That is the trade-off. You may store, join and resell only what the licence allows. Combining an OSM point with a register row is ordinary data work. Pasting a Maps screenshot into a sheet is not. For one-off research, a spreadsheet and the public website of each firm remains the least contested path.
- Prefer a written licence over a richer unlicensed scrape.
- Keep Place IDs only if you will re-fetch display fields through the API under current rules.
- Do not treat “everyone does it” as a term of use.
- If a vendor will not name their source and licence, do not load the file.
Common questions
Is scraping Google Maps illegal or just against the terms?
It is first a breach of contract with Google. Whether it is also a civil or criminal offence depends on local law, computer-misuse statutes and how access was obtained. Most operators never reach a courtroom; they lose API access and the list they stored. This is not legal advice. Read the current terms and, if the list matters, ask a solicitor.
Can I save names and addresses from the paid Places API?
The paid API licences display and limited caching, not a permanent lead database. Place IDs are often kept so you can request the place again. Names, formatted addresses, numbers and reviews are usually time-limited and for end-user display with attribution. Building a reusable CRM from those fields is the storage use the terms are written to stop. Check the live field-caching table before you write a row.
What happens when Google blocks an IP used for Maps scraping?
You typically see CAPTCHAs, then 403 or 429 responses, then empty pages or REQUEST_DENIED on keys. The block follows the network and often the billing account, not only one script. Proxies delay the same outcome. Stopping the job is the rational response; more rotation is still the prohibited collection.
What openly licensed data can replace a Maps lead scrape?
OpenStreetMap under ODbL, national company registers with stated open licences, and some government address products sold with commercial terms. They lack Maps’ phone coverage and freshness. You may store and reuse only what each licence grants, with attribution where required. Licensed directories beat an unlicensed scrape when you need a file you can keep.
For product terms and current prices, see Pricing and the Help Centre.