Google search block on Firefox since last Firefox update June 2026

Google might not like if you're clearing their session data too often — does it only happen once, on the first direct search after each restart? If you go to google.com homepage and search from there, are you able to avoid the turing test?

If they're currently blocking your session/location/behavior — and you're not signed in with them (or it has no effect), perhaps verify you're not clearing site data repeatedly: https://support.mozilla.org/questions/1586735 in case you have setting to clear all browsing history on exit — or what also worked is to set a different Google URL query as a custom search engine if that helps in your case: https://support.mozilla.org/questions/1587084

Thank you for your ideas.

I have cleared cache on occasion and yes it pops up.  But it also pops up after a few days of not clearing cache.  

I have gone to google.com and that page does not block me but as soon as I enter a search on that page, I get stopped again.

Google search works fine from Safari -- so it's hard to believe "Our systems have detected unusual traffic from your computer network. "

The link it wants to send me to wants me to login to Google. I did that once and later the message still popped up.

When I click on "Why did this happen?" I get the following message:

"This page appears when Google automatically detects requests coming from your computer network which appear to be in violation of the Terms of Service. The block will expire shortly after those requests stop. In the meantime, solving the above CAPTCHA will let you continue to use our services.

This traffic may have been sent by malicious software, a browser plug-in, or a script that sends automated requests. If you share your network connection, ask your administrator for help — a different computer using the same IP address may be responsible. Learn more

Sometimes you may be asked to solve the CAPTCHA if you are using advanced terms that robots are known to use, or sending requests very quickly. "

It makes no sense to me -- and wondering if this is a Firefox thing since this only started happening after the latest update?

I'm not sure if it was mentioned in the linked threads — have you tried restarting into Troubleshoot Mode to see what happens when the browser is loaded without any addons and using more default configuration? — Just to check it's not some "privacy" extension getting in the way of how Google refers between these states.