How to Fix a CAPTCHA on Every Page or Visit
Find whether your browser, your network or the site's settings keep asking, then fix that part.
Updated
TL;DR
A CAPTCHA on every page usually means the site's CAPTCHA service can't remember you between pages, because your browser deletes or blocks its cookie or you share a distrusted address. Let the browser keep that site's cookies first, then turn off any VPN.
What a repeating CAPTCHA looks like
Strings from Google's reCAPTCHA docs; the last two mean the site's own setup needs fixing.
| Where | What you see |
|---|---|
| reCAPTCHA v2 checkbox | I'm not a robot |
| reCAPTCHA v2 widget, site over its monthly quota | This site is exceeding reCAPTCHA quota. |
| reCAPTCHA widget, site key no longer valid | Invalid site key |
Why this happens
The check remembers you through a cookie, and your browser keeps throwing it away.
reCAPTCHA sets a _GRECAPTCHA cookie for its risk analysis, and a browser that wipes site data on close is less likely to remember you between visits.
Diagnose your CAPTCHA loop first
No tools needed; each check points at the browser, the network or the site.
Open a few other sites you use daily; if they also keep asking, your browser or network is the cause.
Sign in somewhere, close every browser window and reopen it; if you are signed out, the browser deletes cookies on exit.
Pause your ad or cookie blocker on the site and reload; if the prompts stop, the blocker was stopping the CAPTCHA's cookie or script.
Have someone open the site on their own device on your Wi-Fi; if they are asked too, the shared address is the likely cause.
Notice whether the box appears only when you submit a form; if so, the site may challenge everyone there.
Solutions ranked by effectiveness
Visitors start at the top; the last card is for people who run a site and hear complaints.
- Most common fix
Let the browser keep the site's cookies
Applies when sites forget you after each restart or ask on every page. reCAPTCHA's risk check uses a cookie, and Cloudflare's checks need cookies to pass.
In Chrome Settings, open Privacy and security > Site settings > Additional content settings.
Under On-device site data, choose Allow sites to save data on your device.
If the address bar shows Third-party cookies blocked, select it and turn cookies on.
Allowlist the site and its CAPTCHA provider, such as hcaptcha.com, in your blocker.
- Check next
Check the connection you share
Applies when other devices on your connection are asked too. Sites judge the public address, which a VPN exit shares with strangers and an infected computer can taint.
Switch off the VPN, Tor or proxy app; that shared exit's record is not yours.
Run a full scan with your security software on every computer on the network.
At work or school, tell IT which sites keep asking and since when.
- Site owners
Stop your own site asking on every page
If visitors complain, check your widget first: placed on every page or set to always challenge, it asks every time by design.
Show a visible challenge only on forms that attract abuse, such as sign-up.
In hCaptcha, every Publisher level, Auto included, always challenges; passive modes need Pro or Enterprise.
In reCAPTCHA, prefer score-based (v3) keys; Google says checkbox keys add user friction.
Stop the CAPTCHA loop from coming back
Habits that keep a passed check from being lost.
To clear one site's data, delete only its cookies under See all site data and permissions, not everything.
Leave the date and time on automatic; Cloudflare's Turnstile lists a wrong visitor clock among its failure reasons.
If you use assistive technology, sign up for hCaptcha's accessibility cookie and refresh it by logging in periodically.
Related errors
Learn more
FAQ
Help with your test setup
Geonode's support team is available around the clock for technical questions.
