Troubleshooting
Contact Form 7 reCAPTCHA V3 Not Working: Causes and How to Fix It

Short answer
Contact Form 7 reCAPTCHA v3 usually fails because the keys are v2 instead of score-based v3, your domain is missing from the key settings, or a caching plugin delays the reCAPTCHA script. Create fresh v3 keys, add them under Contact then Integration, and exclude reCAPTCHA scripts from optimisation.
Key takeaways
- Contact Form 7 supports only reCAPTCHA v3 natively.
- v2 keys will not work with the built-in integration.
- Every domain and staging site must be listed on the key.
- Script delay and combine options often break the token.
- Duplicate reCAPTCHA scripts from other plugins cause conflicts.
- The default spam threshold is 0.50 and can be adjusted by filter.
Why is Contact Form 7 reCAPTCHA v3 not working?
Contact Form 7 reCAPTCHA v3 usually fails because the keys are the wrong type, the domain is missing from the key settings, an optimisation plugin delays the reCAPTCHA script, or Google scores real visitors as spam.
The usual symptom is a form that refuses to send and shows a generic error, or a form that sends nothing while showing a spam-style message. Sometimes the reCAPTCHA badge never appears at all.
Contact Form 7 only supports reCAPTCHA v3 natively. The integration is described on the official Contact Form 7 reCAPTCHA page, and Google's reCAPTCHA v3 documentation explains how scoring works.
Work through the causes below in order. Most sites are fixed by the first three checks.
How does reCAPTCHA v3 work with Contact Form 7?
reCAPTCHA v3 runs invisibly on your pages, gives each visitor a score between 0.0 and 1.0, and Contact Form 7 treats submissions below its threshold as spam instead of sending them.
There is no checkbox or image puzzle. Visitors only see a small reCAPTCHA badge, usually in the bottom corner of the screen.
When a form is submitted, Contact Form 7 sends a token to your server. Your server then asks Google to verify the token and returns a score.
If the score is too low, or the token is missing or invalid, Contact Form 7 blocks the message. That is why a broken setup looks like a spam problem rather than a clear error.
Are you using the right type of reCAPTCHA keys?
You must create score-based reCAPTCHA v3 keys in Google's admin console; v2 checkbox or invisible keys will not work with Contact Form 7's built-in integration.
This is the most common mistake. Keys from another plugin or an older setup are often v2 keys.
- Open the Google reCAPTCHA admin console and create a new site.
- Choose the score-based v3 type.
- Add every domain the form runs on, without https or paths.
- Copy the site key and secret key.
- In WordPress, go to Contact > Integration.
- Click Setup Integration under reCAPTCHA and paste both keys.
- Save, then test the form in a private window.
If you need a visible v2 checkbox, you will need a separate add-on plugin. Contact Form 7 removed native v2 support some years ago.
Is your domain listed in the reCAPTCHA settings?
reCAPTCHA keys only work on domains listed in their settings, so a missing domain, a staging site or a changed domain will cause verification to fail.
Include both your main domain and any subdomains you use. The www and non-www versions count as the same domain for reCAPTCHA, but staging subdomains do not.
If you moved the site to a new domain, update the key settings or create new keys. Old keys on a new domain fail quietly.
Also check that the keys are still active in the Google console. Google has been moving reCAPTCHA key management into Google Cloud projects, so confirm the key still appears there and has not been deleted or limited.
Is an optimisation plugin delaying the reCAPTCHA script?
Script delay, defer and combine options in caching plugins often stop reCAPTCHA from producing a token in time, so the form submits without one and Contact Form 7 blocks it.
This is common with WP Rocket, LiteSpeed Cache, Autoptimize, Perfmatters and Cloudflare Rocket Loader. They hold scripts back until a visitor interacts, which can break the token request.
- Clear all caches.
- Turn off JavaScript delay and combine options.
- Test the form.
- If it works, add recaptcha, google.com/recaptcha and contact-form-7 to the plugin's exclusion lists.
- Turn the optimisation back on and retest.
Page caching can also cause problems if very old pages are served. Our guide on how to clear cache in WordPress covers each cache layer.
Is another plugin loading a different reCAPTCHA script?
If another plugin, theme or form builder loads its own reCAPTCHA script, especially a v2 script, the two can conflict and Contact Form 7 may not receive a valid v3 token.
Security plugins, login protection tools, comment plugins and other form builders often add reCAPTCHA to every page.
View the page source and search for recaptcha/api.js. If you see more than one version, or a version with a different site key, find which plugin adds it and turn that feature off on pages with your form.
Our guide to fixing plugin conflicts explains how to test plugins one at a time.
Are real visitors being scored as spam?
Yes, sometimes the setup is correct but Google gives low scores to some real people, such as those using VPNs, privacy browsers or ad blockers, and Contact Form 7 rejects them.
Contact Form 7 uses a default threshold of 0.50. Developers can change it with the wpcf7_recaptcha_threshold filter, which the plugin's documentation describes.
Lowering the threshold lets more people through but also more spam. Change it in small steps, such as from 0.50 to 0.40, and watch the results.
The Google admin console shows score distributions for your site. If many requests score low, check whether your traffic includes lots of VPN or bot visits.
Can the server fail to verify reCAPTCHA?
Yes, verification happens from your server to Google, so if your host blocks outgoing connections or has DNS or SSL problems, every submission fails even with correct keys.
Ask your host whether outbound HTTPS requests to Google are allowed. Some locked-down servers block them by default.
Turn on WordPress debug logging to catch errors during submission. Our guide to reading the WordPress debug log shows where to look. Google's reCAPTCHA troubleshooting page also lists common verification failures.
| Check | What to look for | Fix |
|---|---|---|
| Key type | Score-based v3 | Create new v3 keys |
| Domains | Current domain listed | Add domain in Google console |
| Script delay | Delay or combine enabled | Exclude reCAPTCHA and CF7 scripts |
| Duplicate scripts | Two api.js loads | Disable reCAPTCHA in other plugin |
| Scoring | Many low scores | Adjust threshold carefully |
| Server | Outbound requests blocked | Ask host to allow Google |
Why does the reCAPTCHA badge not appear?
A missing badge means the reCAPTCHA script is not loading, usually because the integration is not saved, the script is delayed or blocked, or CSS hides the badge.
Check Contact > Integration to confirm the keys show as saved. Then view the page source for the reCAPTCHA script.
Some themes or plugins hide the badge with CSS. Google allows hiding it if you show the required reCAPTCHA notice text near the form, as described in the reCAPTCHA FAQ.
Ad blockers and privacy extensions can also stop the script. Test in a clean browser profile.
What alternatives work if reCAPTCHA keeps failing?
If reCAPTCHA v3 causes more trouble than it solves, you can switch to Cloudflare Turnstile, a honeypot add-on, or Contact Form 7's own Akismet and disallowed-words filtering.
Turnstile is free and privacy-friendly, and add-on plugins connect it to Contact Form 7. See our guide to Cloudflare Turnstile on WordPress.
Remove the reCAPTCHA keys from the Integration screen before switching, so two systems do not run together. Our guide on how to stop contact form spam compares the options.
If messages pass reCAPTCHA but still never arrive, the issue is email delivery. Follow our guide to fix Contact Form 7 not sending.
Frequently asked questions
Does Contact Form 7 support reCAPTCHA v2?
Not natively. Contact Form 7's built-in integration only supports reCAPTCHA v3, which is invisible and score-based. If you want a visible checkbox, you need a separate add-on plugin, or you can use another anti-spam option such as Cloudflare Turnstile.
Why does my form say there was an error trying to send?
With reCAPTCHA enabled, this message often means Contact Form 7 treated the submission as spam because the token was missing, invalid or scored too low. Check your key type, domain list and script optimisation settings before looking at email delivery.
Can I hide the reCAPTCHA badge in Contact Form 7?
Google allows hiding the badge if you show the required reCAPTCHA notice text near the form, including links to Google's privacy policy and terms. Hiding it with CSS without that notice breaks Google's terms.
What score threshold does Contact Form 7 use?
Contact Form 7 uses a default threshold of 0.50. Submissions with a lower score are treated as spam. Developers can change the threshold with a filter, but lowering it too far will let more spam through.
Does caching break Contact Form 7 reCAPTCHA?
It can. Plugins that delay or combine JavaScript may stop reCAPTCHA from creating a token before the form submits. Exclude reCAPTCHA and Contact Form 7 scripts from those features, clear every cache, and test again in a private window.
Sources
- reCAPTCHA (v3) Contact Form 7
- reCAPTCHA v3 Google for Developers
- reCAPTCHA FAQ Google for Developers
- Troubleshoot reCAPTCHA issues Google Cloud
- Contact Form 7 WordPress.org Plugin Directory
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


