How Cloudflare Bot Fight Mode Blocked Google From All Our Websites

We run the PTS Content network from one server: 338 websites with 28,444 articles between them, and we use Cloudflare to manage their domains. Cloudflare has a setting called Bot Fight Mode. It sounds like exactly what a website owner wants: one click, and the automated software that scrapes and attacks your site gets stopped. At the time, we did not want AI companies scraping our articles to train their models, so when we moved on 11 November 2025 we switched it on for all our sites. It stopped Google as well.

Why we moved to Cloudflare

For years our DNS, the service that tells the internet where each website lives, was with DNS Made Easy. It offered failover: if our server went down, it could send visitors somewhere else. But we have no second web server to fail over to, and we do not need one. Our server has run at better than 99.99% uptime, and our websites are not mission critical. If one went down for an hour while I restored a backup, nobody would be seriously harmed. So we moved our DNS to Cloudflare, which saves us around $800 a year.

Cloudflare is a great service. It has an extensive API, so we can manage the DNS for hundreds of domains automatically instead of clicking through each one by hand. The problem was not Cloudflare: we flipped the wrong switch.

What happened

Over the winter of 2025, the traffic from Google search to our websites all but disappeared. Only nine of our sites have Search Console records going back that far, and their figures tell the story. In November 2025 those nine were getting between 136 and 200 visits a day from Google between them. By January 2026 it was about four a day, and February was no better. The number of times Google showed our pages in its results fell by about 97%.

Chart of daily visits from Google to nine of our sites, falling from around 150 a day in November 2025 to about 4 a day from mid December to March, then recovering from April to July 2026, with Bot Fight Mode switched on on 11 November 2025 and off on 23 March 2026
This is not a graph of our total traffic. It is Google Search Console's count of clicks from Google search results to nine of our longest running sites. The sites stayed up throughout, and other visitors kept arriving: it was visits from Google search that dried up.

Bot Fight Mode was treating Google's crawler, the software Google uses to read web pages, as one of the bots it was there to stop. If Google cannot read your pages, it stops showing them.

Why it took so long to spot

Nothing told us. Bot Fight Mode does not send an email when it challenges a visitor, and the sites worked perfectly whenever we looked at them, because we are people, not bots.

The timing also pointed the wrong way. Google ran one of its big ranking updates between 11 and 29 December 2025, just as our Google search traffic fell. A drop in the middle of a Google update looks like a Google problem, and the usual advice is to wait for things to settle. Waiting does nothing when the real cause is that Google cannot get in.

The figures tell a different story once you look closely. In Search Console, our clicks from Google started falling on 3 December, three weeks after we switched Bot Fight Mode on and more than a week before the update began, and had already dropped by three quarters by the time it started.

The proof came from one site. With Bot Fight Mode switched off, its Google traffic came back, but very slowly, over months. Google does not restore a site the moment you let it back in. We do not have Cloudflare's logs from that winter, so we cannot show each of Google's requests being turned away. What we have is the timing, and a site that recovered once the switch was off.

What we did

We switched Bot Fight Mode off everywhere on 23 March 2026. Then we went further: our sites now use Cloudflare only for their domain settings (DNS), so visitors and Google come straight to our own server instead of passing through Cloudflare. None of Cloudflare's blocking features can get between Google and our pages now, whatever is switched on in the account.

Recovery was slow. Those nine sites were back to 42 visits a day from Google in April 2026, 137 a day in June and 145 a day in July. Most returned to where they had been. A few never did, but that was down to later Google updates, not Cloudflare.

There is a price. Without Cloudflare in front, more junk reaches our server: about half the raw requests are scrapers and other bots. The server copes easily, and we filter the bots out of our visitor figures. That is a small cost next to vanishing from Google.

Your situation may be slightly different. ask a question below ↓ and our editorial team will reply with our advice.

We made a similar mistake again

In 2026 we used Cloudflare Turnstile, the "are you human?" check, on our comment forms. In April it quietly stopped working for real visitors: every genuine comment was rejected, and for nine days nobody could post. We took it off. Our forms now rely on checks visitors never see, which were already stopping around 1,500 spam attempts a day.

How to check your own site

  • In Cloudflare, look in the security settings under Bots and see whether Bot Fight Mode is on. If it is, ask yourself whether anyone has checked that Google can still get in.
  • In Google Search Console, use URL Inspection on your home page and run a live test. If Google cannot fetch the page, it will tell you.
  • Also in Search Console, open Settings, then Crawl stats. A sudden fall in crawl requests, or a jump in errors, after a change you made is a warning sign.
  • In Cloudflare, the security events list shows which visitors were challenged or blocked. Look for Googlebot in it.

The lesson

Any setting that blocks bots can block the one bot you depend on. Before you switch one on, ask how you would know if it stopped Google. After you switch it on, run the live test in Search Console the same day, and look at the crawl stats a week later. And if your traffic falls during a Google update, check your own settings before you blame Google.

For why AI companies training on our articles still rankles, see Why We Cannot Train Our Own AI on Claude or ChatGPT Answers. For how we run all these sites on one server, see Do Small Businesses Need Cloud Computing? For the other mistakes we see most often, see 10 Costly Technology Mistakes Small Businesses Make.