“Our Systems Have Detected Unusual Traffic”: Why Google Shows It and How to Stop It
Google shows “Our systems have detected unusual traffic from your computer network” when the IP address your searches come from has sent requests that look automated. It is a judgement about the address, not about you: on a shared office network, a VPN or a mobile carrier, other people's traffic counts too. For a normal visitor, solving the CAPTCHA, leaving the VPN or getting a new IP usually clears it within minutes to hours. For automated searches it means the request rate or pattern is above what Google accepts from one address.
- Written by
- seamless Team
- Reading time
- 9 min
- Published

On this page5 sections
The message appears on a page under google.com/sorry/, usually with a reCAPTCHA and an IP address printed at the bottom. That address is the important part: it is the one Google has flagged, and it is often not the one you assume.
What triggers it
| Cause | How common | Who it affects |
|---|---|---|
| VPN or public proxy exit | Very common | Everyone sharing that exit |
| Office, school or hotel network | Common | Everyone behind the same public IP |
| Mobile carrier NAT (CGNAT) | Common | Thousands of subscribers per address |
| Browser extensions that prefetch or scrape | Occasional | Just you |
| Malware using your connection | Occasional | Your whole household |
| Rank trackers and scripts | Very common | Whoever runs them |
| Very fast manual searching with operators | Rare | Power users |
Google does not publish its thresholds, and they move with context. Advanced operators like site:, inurl: and intitle: in quick succession are treated as more suspicious than ordinary queries, because that is exactly what scrapers send.
Fixing it as a normal visitor
- Solve the CAPTCHA once. Google sets a cookie that exempts your browser for a while. If you keep cookies blocked for Google, you will see the page again on every search.
- Turn off the VPN or proxy and search again. Consumer VPN exits are shared by thousands of people and are flagged constantly.
- Check the IP printed on the page against what your connection shows. If it is not your home IP, something is routing you elsewhere.
- Restart your router if your provider assigns dynamic addresses. A new IP usually clears it immediately.
- Disable extensions that preview links, check prices or ‘enhance’ search results, then try again.
- Run a malware scan if the message appears on every device in the house.
On a shared network there may be nothing you can do from your own machine. If the whole office sees the CAPTCHA, the fix is on the network: find the device or tool generating the searches.
When it happens in automation
If the traffic Google flagged is your own script or rank tracker, the page is a precise signal: the rate from one address is too high, or the requests look too uniform. Google's terms do not permit automated queries, so for anything business-critical an official or third-party SERP API is the durable route. If you collect results yourself, the mechanics are covered in how to scrape Google search results; the short version is below.
- Spread queries across many residential exits so no single address accumulates volume. Datacenter ranges are flagged almost instantly on Google.
- Keep one exit per short session, and do not carry Google cookies from one IP to another — a consent cookie that jumps between countries is a strong tell.
- Pace like a person. Seconds between queries, not milliseconds, with jitter.
- Match the locale to the exit.
hl,glandAccept-Languageshould agree with the country of the IP. - Treat the /sorry page as a stop signal. Retire that exit for the session instead of retrying through it.
def is_google_block(resp) -> bool:
return resp.status_code == 429 or "/sorry/" in resp.url
if is_google_block(r):
rotate_identity() # new session tag, fresh cookie jar
time.sleep(random.uniform(20, 60))How long does the block last?
For a lightly flagged address, solving the CAPTCHA is enough and the block lifts at once. For an address that keeps sending automated traffic, it can persist for hours or days, and every further request extends it. There is no form to request removal; the address has to stop generating the traffic, or you have to stop using that address.
Related: CAPTCHA on every page, not just Google
If sites beyond Google start challenging you at the same time, the address is on broader reputation lists. Check it with an IP fraud score lookup. Cloudflare's version of the same experience is covered in the verify-you-are-human loop.
FAQ
Frequently asked questions
Anything else? Our team answers on live chat, by email and on Discord.
Why does Google say it detected unusual traffic from my computer network?
Your public IP address has sent searches that look automated. On a shared network, VPN or mobile carrier, the traffic of other users behind the same address counts too, so you can be flagged without doing anything unusual yourself.
How do I get rid of Google's unusual traffic page?
Solve the CAPTCHA, disconnect any VPN or proxy, disable search-related browser extensions and, if your IP is dynamic, restart your router to get a new address. If it appears on every device in your home, scan for malware.
How long does the Google unusual traffic block last?
Often only until you solve the CAPTCHA. If the address keeps sending automated traffic, the block can last hours or days and is extended by every further request.
Does a VPN cause the unusual traffic error?
Frequently. VPN exits are shared by many users, some of whom run automated searches, so Google flags those addresses often. Disconnecting the VPN is one of the fastest fixes.
Can proxies avoid Google's unusual traffic detection?
Residential proxies spread requests across many consumer addresses, which keeps the volume per IP low. They do not help if the request pattern itself is robotic, and datacenter proxies are flagged by Google almost immediately.

