"Our systems have detected unusual traffic from your computer network" means Google thinks searches from your IP address are automated. If you are running lead collection, the cause is almost always your own request rate or pattern: stop the run, let a person solve the reCAPTCHA only if they are genuinely browsing, wait for the block to clear, and resume much more slowly, or not at all. If nothing on your side is automated, look at your VPN, shared network or a possible malware infection.
This page is part of the scraping troubleshooting guide, which covers other block types such as 403 and 429.
What Google says
Google's help page, Unusual traffic from your computer network, explains that the message appears when a network "seems to be sending automated traffic to Google Search". It lists what counts as automated traffic:
- Searches sent from robots, computer programs, automated services or search scrapers.
- Use of software that sends searches to Google "to find how a website or web page ranks on Google".
And it lists other ways your network can be flagged when you are not the source:
- Malware: "You or another user on your network might have malware."
- Shared networks: others on the same network, "like at a school or business", sending automated searches.
- VPNs: others on the same VPN, and "some VPNs and tunnel services cause all traffic to be blocked". IPv6 tunnel services can cause it too.
- Your internet provider: other customers sharing the same addresses.
Google's suggested fixes are to solve the reCAPTCHA (with JavaScript enabled), check for malware, contact your network administrator, uninstall the VPN or contact the VPN provider, or contact your internet provider.
The block page itself usually adds that it appears when requests "appear to be in violation of the Terms of Service" and that the block will expire shortly after those requests stop. It also shows your IP address and the time, which is useful when checking whether the address is your own connection or a VPN exit.
Which cause is yours?
| What you see | Most likely cause | First thing to try |
|---|---|---|
| CAPTCHA appeared minutes into a collection run | Your run's rate or pattern | Stop the run |
| CAPTCHA on every search, even by hand, with a VPN on | Shared VPN exit address | Disconnect the VPN |
| CAPTCHA on the office network but not on mobile data | Someone else on the network, or an office tool | Ask your IT administrator |
| CAPTCHA on all devices at home with nothing running | Malware or a compromised device, or your provider's shared address | Scan devices, restart the router, contact the provider |
| Blank page or "sorry" URL with no CAPTCHA | A hard block, or an extension blocking scripts | Check JavaScript and extensions; wait |
The IP address on the block page tells you which connection Google is seeing. If it is not your normal home or office address, a VPN or proxy is in the path.
Why lead collection triggers it
Collecting search or Maps results with software looks automated because it is. The common triggers:
- Volume. Hundreds of searches in an hour from one address is not what a person does.
- Speed and regularity. Searches at exactly even intervals, or with no pause to read results.
- Parallel sessions. Several browser windows searching at once from the same IP.
- Repetition. The same query shape again and again ("plumber in" plus a town).
- Retries. A tool that immediately retries after a failure doubles the rate at exactly the moment Google is already suspicious.
Splitting a city into many searches to get past the result cap multiplies all of these, which is why the CAPTCHA often appears in the middle of a big Maps run. The coverage method itself is in Google Maps only shows 120 results; the point here is to run it at a pace the platform tolerates.
What to do when it appears during a run
- Stop the run immediately. Every further request extends the problem. Pause all jobs that use the same connection, not just the one that hit the CAPTCHA.
- Do not loop. A tool that keeps reloading the page or retrying the search is the worst possible response.
- Solve it once only if you are a person browsing. The CAPTCHA is there to let genuine users continue. Solving it to restart automated collection at the same speed just leads to another, longer block.
- Wait. Give it time; the block is designed to lift once automated requests stop. An hour is a reasonable minimum before trying again; if it is still there, leave it until the next day.
- Resume much slower. Fewer searches per hour, one job at a time, longer and less regular pauses, and no automatic retries on failure.
- Keep a record. Note the time, the job and how many searches had run. If it happens at the same point every time, that is your ceiling on this connection.
- Stop for good if it keeps happening. Repeated CAPTCHAs after you have slowed down mean Google does not want this traffic from you.
What not to do
- Do not use CAPTCHA solving services. Google's Terms of Service list "bypassing our systems or protective measures" as abuse, and prohibit "using automated means to access content from any of our services in violation of the machine-readable instructions on our web pages".
- Do not rotate through proxies or VPN addresses to dodge the check. It is the same evasion by other means, and it often makes things worse for other users of those addresses.
- Do not create extra Google accounts to spread the load. Account farming breaches the terms and puts every account at risk.
- Do not record the run as "no results". A blocked search is not evidence that no businesses exist; mark it as blocked and come back to it.
The polite alternatives
If you need more Google data than a slow pace allows:
- Collect less. Narrow categories and areas to your real sales territory. Fewer, better searches beat a national sweep.
- Spread it out. A run that takes three evenings at a gentle pace may finish; one that tries to finish in an hour will not.
- Use another platform for part of the work. Bing and Apple Maps have their own listings and their own limits.
- Use the official API. The Places API has documented limits (Text Search returns at most 60 results per query, per Google's documentation), usage charges and its own terms on storing data, but it is the licensed programmatic route.
Rate limits from other sites follow similar logic: a 429 Too Many Requests response, defined in RFC 6585 as "too many requests in a given amount of time", may come with a Retry-After header saying how long to wait. Google's CAPTCHA does not give you a number, so you have to choose a conservative one. More on 429 handling is in web scraping blocked: troubleshooting.
Long runs and the CAPTCHA
The longer a run, the more likely it meets a check partway through. Design runs so a pause costs nothing:
- Save progress per job, so a stopped run resumes from the next unprocessed search rather than starting again.
- Keep failed and blocked jobs in a queue to retry later, rather than retrying immediately.
- Run overnight or across days at low speed rather than in one burst.
How Map Extract helps
- CAPTCHA detection pauses work for manual handling. When a CAPTCHA page is detected during collection, work pauses so you can deal with it yourself. It is recorded, not counted as a result, and the blocked job is not saved as "no businesses found".
- Bounded retries. Failed jobs are retried a limited number of times, and the previous attempt's diagnosis is kept before a retry, so you can see why it failed.
- Run controls. The run centre lets you pause, resume and stop prepared runs, so one CAPTCHA does not mean losing the whole job list.
- Separate profiles. Browser profile management keeps a separate saved profile per platform and project, and security challenges stay manual.
- Website crawls are separate. The website data extractor records CAPTCHA and blocked outcomes on business websites too, and quarantines sites that keep blocking until you choose to retry them.
What it does not do: it cannot stop Google from showing a CAPTCHA, and its pauses and limits do not guarantee that your network will not be flagged. Google CAPTCHA stops should be expected on larger runs. Third-party platforms may restrict data collection or automated actions. Before running a workflow, check the platform's rules and make sure you have permission for the actions you configure.
Public business and social results the app collects are uploaded automatically to Map Extract's servers while it is licensed and running; the privacy notice explains this.
Key takeaways
- The message means Google sees automated-looking traffic from your IP address.
- During a collection run, the cause is almost always your own rate, parallelism or retries.
- Stop, wait, and resume far slower; never loop or keep retrying.
- Do not use solving services, proxy rotation or extra accounts to get past it.
- If nothing on your side is automated, check your VPN, shared network and devices for malware.
Frequently asked questions
What does 'Our systems have detected unusual traffic from your computer network' mean?
Google shows this page when requests from your network look automated. Its help page lists searches sent by robots, computer programs, automated services and search scrapers, and software that checks rankings. It can also appear when someone else on a shared network, VPN or internet provider is sending automated searches, or when malware is running. Solving the reCAPTCHA lets a person continue.
How long does Google's unusual traffic block last?
Google does not publish a fixed time. The block page itself says it expires shortly after the automated requests stop. In practice, if your own tool caused it, stopping the tool and waiting usually clears it. If it keeps appearing after you have stopped everything, the traffic is probably coming from someone else on your network, your VPN or malware on a device.
Why do I get a Google CAPTCHA on every search?
Every-search CAPTCHAs usually mean your IP address is shared with heavy automated traffic: a VPN exit, an office or school network, or a mobile carrier gateway. Turning off the VPN, trying another network and scanning for malware are Google's own suggestions. If you run collection software on the same connection, stop it; continuing to search keeps the network flagged.
Should I use a CAPTCHA solving service to keep my scraper running?
No. A CAPTCHA is Google asking whether a person is there. Google's terms list bypassing its systems or protective measures as abuse, and paying a service to answer on your behalf does exactly that. It also keeps the automated pattern going, so blocks get longer. Pause, let a person solve it if they are genuinely browsing, then resume far slower or stop.
Sources
Written by the Map Extract editorial team. Found an error? Email [email protected] and we will check and correct it. How we research guides: editorial policy.