If you search "dentists in Miami" on Google Maps and scroll to the bottom of the list, it stops at around 120 places. There are far more than 120 dentists in Miami. That ceiling is the single biggest reason lead lists built from Google Maps come out incomplete.
This guide explains where the limit comes from, why the usual workarounds fail, and the method that actually returns every business in an area.
Where the 120 limit comes from
Google Maps returns results in pages of 20 and stops after about six pages. The cap applies per search, regardless of how many businesses match. Google's own Places API has a similar ceiling of 60 results per text query, so even developers using the official API run into it.
The result: any tool that runs one search and scrolls to the end will hand you at most ~120 rows — and it won't tell you how many it missed.
Why the usual workarounds don't work
| Workaround | What actually happens |
|---|---|
| Scroll longer | The list ends at the cap. There is nothing more to load. |
| Zoom in | You get a different 120, not more. |
| Add more keywords ("dentist", "dental clinic", "orthodontist") | Helps a little, but each search still caps, and overlap is heavy. |
| Search by neighbourhood names | Better, but neighbourhood boundaries are irregular, dense areas still cap, and you have to merge lists by hand. |
All of these share the same flaw: you never know whether you've got everything.
The method that works: grid splitting
The reliable approach is geographic:
- Draw a grid over the area. Split the city's bounding box into cells.
- Search each cell for the same term.
- Subdivide any cell that hits the cap. If a cell returns ~120, there are probably more inside it, so split that cell into four and search again. Repeat until no cell is capped. This is a quadtree, and it adapts automatically: a dense downtown gets many small cells, suburbs get a few big ones.
- Merge and de-duplicate. Cells overlap at the edges, so the same business appears more than once. De-duplicate on Google's place_id, not on name or address — two branches of a chain share a name, and addresses are written inconsistently.
When no cell is capped, the merged list is complete for that area. If some cells are still capped at the smallest size you allow, you know the result is a lower bound and roughly how much is missing.
Count before you spend
Grid splitting has a cost: a big city can mean hundreds of searches. That's why it pays to count first. Run the quadtree probe without writing any rows, and you learn the size of the search ("about 3,400 businesses") before you spend a single credit on it.
This is how MapScraper works: the pre-count probe tells you how many places a search contains — exactly when no cell is capped, as a range when some are — and only then do you decide whether to run it.
What fields to pull once you have the full list
Getting every business is half the job. For outreach you usually want:
- Name, category, address, coordinates — for segmentation and routing
- Phone and website — the basics for calling and qualifying
- Rating and review count — a quick filter for business size and activity
- Email and social profiles — not on the Maps listing itself; they come from crawling the business's website
See the full field reference for all 41 fields MapScraper exports.
A quick way to check whether a tool is hitting the cap
Run the same search in the tool and count the rows. If you get 100–125 rows for a term like "restaurants in Chicago", the tool is almost certainly running a single capped search. A tool that splits the area will return thousands.
Summary
- Google Maps caps every search at ~120 results.
- Scrolling, zooming and keyword stuffing don't remove the cap.
- Splitting the area into a self-subdividing grid and de-duplicating on place_id returns the complete list.
- Count first, so you know the size and cost before you run it.
You can try this on your own search with the free plan — 300 leads, emails included, and the pre-count is free.