"Our systems have detected unusual traffic from your computer network. This page checks to see if it's really you sending the requests, and not a robot." Then a reCAPTCHA, and sometimes a line about why this might have happened. The message shows up mid-search, on a computer that has done nothing more automated than look up a recipe, and the phrase "your computer network" is the clue to everything that follows. Google is not accusing you. It is accusing the address you share.
Google's own help page puts it plainly: the message appears when "a network you use, including VPN networks, seems to be sending automated traffic to Google Search". The list of things it names as causes is worth reading closely, because none of them is "you searched too much". They are malware on your computer or your shared network, other people on your network sending automated searches, a VPN whose other users are doing the same, IPv6 tunnel services, and other customers of your internet provider sending automated searches. In other words, the cause is almost always a neighbour on the same address.
Why one address takes the blame for everyone on it
Every request to Google arrives from a public IP address, and Google keeps a running estimate of whether the traffic from that address looks human. When the estimate tips, it asks for a captcha before answering further. The problem is how many people can sit behind one address:
- A VPN server. One exit address, thousands of customers. If a handful run rank trackers or scrapers through it, everyone on that server meets the captcha. This is the single most common cause for people who see the message every day.
- A mobile carrier. Carriers use carrier-grade NAT, which places hundreds or thousands of phones behind one public address. CGNAT has the mechanism; the practical effect is that a stranger's automated app can earn your phone a captcha.
- An office, school, or campus. Everyone exits through one gateway address. A single SEO tool on one desk can trip the message for the whole building.
- Your own ISP. Some providers share addresses among customers, which is the "others using your internet provider" line in Google's list.
- An IPv6 tunnel service. Google names these because the tunnel's address range is shared and often abused.
- Your own machine. Malware that runs searches in the background, or a browser extension that queries Google to check rankings or prices, generates exactly the traffic Google means, from your own address.
| What you notice | The likely cause | How to confirm it |
|---|---|---|
| Message appears only with the VPN on | Shared VPN exit | Disconnect the VPN, reload |
| Constant on mobile data, fine on Wi-Fi | Carrier-grade NAT | Compare the two networks |
| Whole office sees it | One gateway address, one automated tool inside | Ask who runs SEO or scraping software |
| Only your computer, on any network | Malware or an extension on the machine | Private window with extensions off, then a scan |
| Started after installing an SEO or price tool | The tool queries Google from your address | Pause the tool for an hour |
Fixes, in the order that works
1. Solve the captcha
It is not a trick. Solving it tells Google a person is present and clears the block for a while, sometimes for the rest of the day. If it returns within minutes, the automated traffic on your address is ongoing, and the steps below find it.
2. Turn off the VPN, or change its server
Disconnect the VPN and search again. If the message is gone, the VPN's exit was to blame. Pick a server in another city and it will usually stay gone until that server, too, accumulates neighbours who abuse it. Google's help page goes as far as suggesting you uninstall the VPN or contact its provider, which is the same diagnosis from the other side.
3. Switch networks to see whether it follows you
Search from your phone on mobile data with Wi-Fi off, then from Wi-Fi with data off. If the message appears on one network and not the other, the address of that network is the cause, and the device is innocent. If it appears on both, look at the device itself in step 5.
4. Get a new address, if your provider hands them out
Many home connections receive a dynamic address that changes when the router reconnects. Power the router off for a minute and back on, then check your address in our IP lookup to see whether it changed. A new address starts with a clean estimate. If the address never changes, your provider assigns static ones, and the next option is to ask them whether the address is shared.
5. Find automated traffic on the device
Open a private window with all extensions disabled and search. If the message does not appear there but does in your normal window, an extension is the source: rank checkers, price trackers, "research" toolbars, and some coupon extensions all query Google in the background. Remove it. If the message appears everywhere on this machine and on no other device, run a full malware scan; software that uses your connection to scrape is exactly what Google's first cause describes.
6. Find automated traffic on the network
At an office or school, the address belongs to everyone, and someone inside is running a tool. SEO rank trackers, scrapers, and automated browsers are the usual suspects, and they are not always on the machine of the person who sees the captcha. Google's advice here is to contact your network administrator, which is the polite version of "find out who is running the scraper". Once found, the fix in step 7 keeps the tool and clears the address.
7. Move automated traffic off your address
This is the part that applies to people who are the automated traffic, honestly and deliberately: SEO teams tracking rankings, price monitors, researchers pulling results. Google's threshold is per address, so the tool that runs from the office connection burns the office. The working pattern is to pace the queries and to send them through rotating residential proxies, so that each request arrives from a different household address and no single address crosses Google's tolerance. Why scrapers keep hitting reCAPTCHA has the full setup, including the rate that stays under the line and why datacenter addresses trip it first. The proxies for SEO page covers the tooling side.
A warning that belongs here: doing this through free public proxies makes the message worse, not better. A free proxy is an address that thousands of strangers already use for exactly this, and its reputation with Google is spent before you arrive. Check any address in our proxy checker and expect most public ones to draw the captcha on the first search.
What does not help
Clearing cookies, switching browsers, and incognito mode rarely change anything, because the judgement is on the address, not the browser. Repeatedly failing or refreshing the captcha makes the estimate worse. Changing DNS servers does nothing, since the address Google sees is unchanged. And logging into a Google account can help a little with the estimate but does not clear an address that is actively sending automated traffic.
What to do first
The message is about the address, and the address is shared. Solve the captcha, then take the VPN off, try another network, and look for a tool or infection sending searches from your side. When the automated searches are yours, move them onto addresses built for it and pace them, and your own connection goes back to being just yours.