Google reCAPTCHA Blocking Genuine Enquiries: Scores and Fallbacks
Short answer: reCAPTCHA v3 gives every visitor a score from 0.0 (likely a bot) to 1.0 (likely human) and leaves it to your form code to decide what to do with that number. If the cut-off is set too high, or visitors arrive through privacy browsers, VPNs or strict tracker blocking, genuine people can score low and be silently rejected. Start logging the score with each attempt, lower the threshold to a level your real traffic passes, and replace the hard block with a fallback such as a manual review queue or an email link. If problems continue, consider a lighter alternative such as Cloudflare Turnstile.
The symptom
A customer rings to say they filled in your quote form three times and nothing happened. Or your enquiry count halves the week a plugin update turned on reCAPTCHA v3. In both cases the form looks fine to you, because your own browser and network score well.
The cause is usually one of three things: a strict threshold, a script that fails to load, or a token that expires before the visitor presses Send.
How v3 scoring actually works
Unlike the older checkbox, v3 runs invisibly. On page load or form submit, the browser asks Google for a token. Your server sends that token to Google's verification endpoint and gets back a response that includes success, score, action and a timestamp. Google's v3 documentation describes this flow and suggests starting with a threshold of 0.5, then adjusting based on what you observe in the admin console.
Key points that catch people out:
- The score is a signal, not a verdict. Google expects you to choose the response.
- Scores improve as reCAPTCHA sees more traffic on your site, so a new key on a quiet site can behave unpredictably at first.
- Tokens expire after about two minutes. A visitor who loads the page, writes a long message and then submits may send a stale token if your code fetched it on page load.
Step 1: Log every score
Before changing anything, find out what scores real visitors get. Ask your developer, or the form plugin settings, to record for each submission attempt:
- Date and time
- The score returned
- The action name
- Whether the attempt was accepted or rejected
- The hostname in the response
Keep this for a week or two. You will usually see genuine enquiries clustered between 0.3 and 0.9, and obvious spam (link-stuffed messages, nonsense names) at 0.1 or below. If several messages that are clearly from real customers sit at 0.3 and your threshold is 0.5, you have found the leak.
Many WordPress form plugins, for example, have a setting for the threshold but not a log. A small custom field or a hidden admin email that includes the score is enough.
Step 2: Adjust the threshold
Use the log to choose a number. A practical approach:
| Observed pattern | Suggested change |
|---|---|
| Real enquiries rarely below 0.5, spam at 0.1 | Keep 0.5 |
| Some real enquiries at 0.3 to 0.4 | Drop to 0.3 |
| Real enquiries spread down to 0.1 | Do not hard block; use a fallback |
Check the action name too. If your code verifies that action equals contact_submit but the front end sends submit, every attempt fails regardless of score.
Step 3: Check the browser side
Some failures are not about scores at all. Test the form in:
- Firefox with Enhanced Tracking Protection set to Strict
- Brave with Shields up
- Safari with a content blocker installed
- A phone on mobile data with a VPN app switched on
If the reCAPTCHA script is blocked, no token is created and your server rejects the submission as missing a token. A well-built form should detect this and show a friendly message rather than failing silently. Also open the browser console and look for errors mentioning grecaptcha or a refused script, which often point to a Content Security Policy that does not allow Google's domains.
For stale tokens, request a fresh token at the moment of submission instead of on page load.
Step 4: Add a fallback instead of a hard block
Rejecting a low score outright means a lost lead you will never hear about. Better options:
- Accept and flag. Store low-score submissions in a separate folder or label them "check" in the notification email. You glance at them once a day.
- Step-up challenge. Show a v2 checkbox challenge only when the v3 score is low. Real people tick a box; most bots stop.
- Visible alternative. If the token is missing or the score is very low, show a message with your email address or phone number so the visitor can still reach you.
Option 1 is the simplest and loses nothing. A minute of sorting is cheaper than a missed job.
Step 5: Consider alternatives
If reCAPTCHA continues to cause friction, there are other approaches:
- Cloudflare Turnstile. A free challenge that usually runs without asking the visitor to solve anything and does not depend on Google. The Turnstile documentation explains the widget and server-side check.
- Honeypot field. A hidden input that humans never fill in. Bots that complete every field reveal themselves.
- Time check. Reject forms submitted within two seconds of the page loading.
- Server-side filtering. Many hosting or form tools offer spam filtering on content.
A combination of a honeypot, a time check and a flagged folder stops most spam on a small business site without any third-party script.
Privacy note
reCAPTCHA sends visitor data to Google. For UK visitors, your privacy notice should mention it, and whether it needs consent under your cookie approach is something to confirm with the ICO's guidance or your adviser. This article is not legal advice.
FAQ
What reCAPTCHA v3 score should a contact form use?
Google suggests 0.5 as a starting point. Base your final choice on logged scores from your own visitors, and use a fallback rather than a hard block for borderline results.
Why does the form work for us but not for some customers?
Your network and browser history give you a high score. Customers on VPNs, privacy browsers or shared mobile connections may score lower or have the script blocked entirely.
Can we just remove reCAPTCHA?
You can, but replace it with something: a honeypot, a time check, or Turnstile. An unprotected form on a public site usually attracts spam quickly.
Does reCAPTCHA v2 have the same problem?
The checkbox version blocks fewer genuine people outright, because they can solve a challenge. It adds friction, though, and still depends on the script loading.
We can test your form end to end and trace exactly where enquiries are being dropped, so send us the page address whenever suits you.