Google Maps Lead Scraping: What Is Possible and Legal

Google Maps is the largest directory of local businesses in the world, so it is the first place many sales teams look for leads: every dentist in Dubai, every logistics company in Toronto, every restaurant within five kilometres of a new branch. Plenty of tools promise to "scrape Google Maps" in a click.

We build data pipelines for a living, and scraping Google Maps is one of the most requested jobs we get. It is also one where the honest answer has more nuance than most tools admit. This article explains what data is available, the official route versus scraping, what Google's terms and privacy law say, and how to build a lead list you will not regret.

This is general information, not legal advice. Laws differ by country and change over time. For a commercial project, check with a lawyer who knows your market.

What data is on a Google Maps listing?

A typical business profile shows:

• Business name, category and description
• Address, coordinates and service area
• Phone number and website
• Opening hours
• Average rating and number of reviews
• Individual reviews, with reviewer names and photos
• Photos, popular times and attributes such as "wheelchair accessible"

For lead generation, the useful fields are usually name, category, address, phone, website and rating. Reviews are rarely needed, and they are where most of the personal data sits.

The official route: the Places API

Google sells this data through the Google Maps Platform Places API. You search by text or by location, get back place IDs, and request details for each place. You pay per request, and the price depends on which fields you ask for, so you only pay for what you use.

What to know before relying on it:

• It is the sanctioned way to use Google's place data in a product, and the one that carries no terms-of-service risk.
• Results per search are capped. A broad query such as "restaurants in London" will not return every restaurant. Covering a city means running many narrower searches by area and category.
• Storage is restricted. At the time of writing, Google's terms allow place IDs to be stored indefinitely but limit how long most other content can be cached. That matters if you want to build a permanent database. Read the current Maps Platform terms before designing your storage.
• Attribution rules apply when you display the data.

For many lead-generation use cases, the Places API plus a well-designed search grid is enough, and it is the option we recommend first.

Scraping Google Maps: what the terms say

Scraping means collecting the data from the Google Maps website or app with automated tools, outside the API.

Google's terms do not allow it. Google's general Terms of Service restrict automated access to its services, and the Maps Platform terms explicitly prohibit scraping or exporting Maps content outside the permitted uses. Scraping Google Maps is a breach of those terms, whatever the tools selling it suggest.

What a breach means in practice is mostly contractual: blocked IP addresses, CAPTCHAs, suspended Google accounts, and in principle a civil claim. It is a different question from whether scraping public web pages is a crime.

Is scraping public data illegal?

This depends heavily on the country, so here is a short, simplified tour.

United States. Two developments shaped the current view. In Van Buren v. United States (2021), the Supreme Court read the Computer Fraud and Abuse Act narrowly, focusing on whether someone accesses areas of a system they are not entitled to enter. In the long-running hiQ Labs v. LinkedIn dispute, the courts indicated that scraping data anyone can see without logging in is unlikely to be "unauthorized access" under that act. That same case, though, ended with hiQ found to have breached LinkedIn's user agreement. The practical lesson: public-data scraping is not generally treated as hacking, but terms of service are enforceable contracts.

European Union and United Kingdom. The GDPR applies whenever the data identifies a person. Many business listings do: sole traders, doctors, lawyers and agents often list personal phone numbers or trade under their own name. Collecting it needs a lawful basis, usually "legitimate interest", with a documented balancing test. You generally also have to tell people you hold their data, within a set period, when you did not collect it from them directly.

Canada. PIPEDA governs personal information in commercial activity, and CASL governs commercial electronic messages. CASL requires consent to email someone commercially. It recognizes implied consent when an address is conspicuously published and the message relates to the person's business role. That covers some, not all, of the scraped-list use cases.

Everywhere. Sending marketing messages is regulated separately from collecting data. A lawfully collected list can still be unlawful to email or call without the right consent.

Why "is it legal?" is the wrong first question

Most scraped lead lists fail for business reasons before legal ones:

• Data decays fast. Businesses close, move and change numbers. A list scraped once and used for a year is largely stale.
• Cold outreach to scraped contacts converts poorly when it is generic, and it damages your sender reputation when it bounces.
• Blocks make pipelines fragile. A scraper that fights Google's defences needs constant maintenance, so the "free" data is not free.

A smaller, fresher, well-targeted list almost always beats a large scraped one.

How to build a Maps-based lead list responsibly

Here is the approach we recommend to clients:

1. Start with the Places API. Cover the area with a grid of narrow searches by category and neighbourhood, and store place IDs.
2. Collect only business fields. Name, category, address, website, public business phone. Skip reviewer data entirely.
3. Enrich from the business's own website. Contact pages and structured data on a company's own site are a better, more current source of business contacts than a map listing. Respect each site's robots rules and rate limits.
4. Refresh on a schedule using place IDs, instead of treating the list as a one-off export.
5. Document your lawful basis if you operate under the GDPR or similar laws. Record where each record came from, and honour opt-outs and deletion requests promptly.
6. Get marketing consent right for your channel and country before the first email or call.

Where scraping still comes up

Some clients have needs the API does not cover, or data outside Google entirely: industry directories, marketplace seller lists, association member pages. For those we review each source before quoting. We check the site's terms, robots rules, whether the data is personal, and the volume and refresh rate involved. We do not scrape behind logins or paywalls, and we do not collect personal data without a clear legal basis. Some requests end with the recommendation to use an official API or a licensed data provider instead. That is a legitimate outcome.

If you need a lead or local-business data pipeline built properly, see our web scraping service. For a related use case, read how to monitor competitor prices with web scraping.