Stalled captures, blank emails, a run that stops at 120 results. Here is what each symptom means and how the free Vonsel extension fixes it.
Extension··8 min read
Key takeaways
Most "capture failures" are not bugs. They are Google limits, blank source fields, or a search that was too broad to finish cleanly
The Vonsel extension is the means: it captures listings in the browser. The Vonsel dashboard is the end, where history, enrichment, and review analysis turn a list into pipeline
You never have to re-scrape. Reopen a past capture, add more businesses, and attach reviews to the ones you already have
Start here
A capture problem is usually a signal, not a failure
When a Google Maps capture stalls, returns half the fields blank, or stops earlier than you expected, the instinct is to blame the tool. In practice most of these symptoms are the map itself telling you something: the search was too broad, the businesses simply do not publish that field, or you hit a limit Google enforces on everyone.
The good news is that each symptom maps to a clear fix. The Vonsel extension is only the capture layer. The real work happens afterward in the Vonsel dashboard, where a raw list becomes a mapped CRM with enriched contacts, review intelligence, and an AI email drafted for each business. Once you know where the boundary sits, the fixes are quick.
This guide walks through the issues we see most often, in the order they usually appear during a capture session.
Not running the extension yet?
Install it in a couple of minutes and follow along with a live search. Free download. No trial, no credit card.
Before you touch a setting, find your symptom in the table below. Nine times out of ten the cause is on the Google side or in how the search was framed, not in the extension.
Symptom
Likely cause
Fix
Capture stops around 120 results
Google's per-search result ceiling
Split into tighter keywords and smaller areas
Emails or phones blank
Field not published on the profile
Turn on website enrichment
Capture stalls mid-run
Page not fully loaded or tab switched away
Keep the Maps tab active, scroll the panel
Duplicate rows
Overlapping searches merged
Dedupe in the dashboard, not by hand
Reviews missing
Reviews are a separate capture step
Add reviews to captured businesses
Wrong area captured
Map viewport drifted before starting
Frame the map, then start the capture
The rest of this article expands on the three that cause the most confusion: the 120 ceiling, blank contact fields, and a run that seems to freeze.
Issue one
Your capture stops at 120 results
This is the most reported "problem" and it is not a problem at all. Google Maps returns roughly 120 places for any single search, then stops paginating. Every browser-based tool hits the same wall because the wall belongs to Google, not to the extension. We break the reasoning down in why Google limits results to 120.
The fix is to stop asking Google one huge question and start asking many small ones. Instead of "restaurants in London", run "restaurants in Camden", "restaurants in Shoreditch", and so on, or narrow by category with "sushi restaurants", "vegan restaurants", "pizzerias". Each tighter query returns its own set of up to 120 places.
Then you merge. Because every capture lands in your Vonsel history, you can reopen a previous run and add the new businesses to the same list rather than juggling a dozen spreadsheets. The 120 cap limits one search, not your database. Google documents its own coverage model in the Places API overview, and the ceiling shows up there too.
Issue two
Emails, phones, or socials come back blank
A Google Maps profile only carries the fields the business chose to publish. Plenty of listings show a website but no email, or a phone but no social handle. When those cells are empty in your export, the raw source was empty too. A basic scraper stops there and hands you the gaps.
Vonsel closes many of them with website enrichment. When a listing links to a site, the extension visits that page in the background and pulls the email, phone, and social profiles it finds there. That single step recovers contact data that the map alone never exposes.
If a field is still blank after enrichment, the business genuinely has no public contact for it. That is a data-quality reality, not a capture bug, and it is exactly why an enriched, context-rich database beats a bought list of stale rows.
A blank field is information. It tells you which businesses have a weak online presence, and those are often the easiest to sell a website or a profile cleanup to. What looks like a capture gap is frequently a qualified lead in disguise.
Issue three
The capture stalls or freezes mid-run
A capture that appears to hang is almost always a loading issue on the Google side. The results panel loads places as you scroll, so if the tab is in the background or the list has not finished rendering, there is simply nothing new for the extension to read yet.
Keep the Google Maps tab active and in the foreground while a capture runs, let the results panel finish loading, and avoid switching windows mid-capture. Chrome throttles background tabs to save resources, which the official Chrome extensions documentation describes, and that throttling is what makes a background run look stuck.
Keep the tab in focus
Leave the Google Maps tab active while capturing. Background tabs get throttled by Chrome and the run will look frozen.
Let results load first
Give the results panel a moment to populate before starting. A half-loaded list gives the extension nothing to read.
Frame the map, then start
Set the exact area you want in view before you begin, so the viewport does not drift into the wrong neighborhood.
Resume, do not restart
If you have to step away, you can resume a capture later from history instead of starting over.
Fix these on your next search
Add the extension, open Google Maps, and let the dashboard handle history, enrichment, and dedupe. Free download. No trial, no credit card.
Most Google Maps scrapers are one-shot: you run a query, you get a CSV, and if something is off you run the whole thing again. That single-file workflow is what turns a small hiccup into a wasted afternoon. Vonsel is built the other way around, so the fixes above are baked into the product rather than bolted on.
results per search on Google Maps, a limit that lives on Google's side
0
re-scrapes needed to add businesses or reviews to a saved list
Free
to install the extension, with no trial period and no card on file
A stalled capture is rarely a bug. It is the map showing you its edges
Put it together
From clean capture to real pipeline
Once your captures run smoothly, the payoff is not the CSV. It is what the dashboard does next: it plots every business on a map, enriches the contacts, reads the reviews for pain points, and drafts an email tailored to each one. That is the end the extension serves. Walk the whole path in the search-to-CRM workflow.
Troubleshooting a capture is worth doing well, because a clean list feeds everything downstream. Get the data in right, and the dashboard does the rest.
Stop fighting your captures
Run searches, keep a full history, and enrich every list in one place. Free download. No trial, no credit card. Explore features or see plans.
Why does my Google Maps capture stop at 120 results?
Google Maps only returns about 120 results per search, so a capture that ends there is behaving normally. To pull more, split the search into tighter keywords and smaller areas (by neighborhood, by category, or by city), then merge everything inside your Vonsel dashboard.
Why are some emails or phone numbers missing after a capture?
Not every business publishes an email on its Google profile, so those fields can come back blank. Vonsel runs website enrichment that visits the linked site to recover emails, phones, and social profiles, which fills many of the gaps a raw scraper leaves empty.
Do I have to re-scrape a list to add more businesses or reviews?
No. With Vonsel you can reopen a past capture from your history, add more businesses to it, and attach reviews to businesses you already captured. You never have to start over from a blank list.