Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Gravity Forms reCAPTCHA Not Working: Causes and How to Fix It

Gravity Forms reCAPTCHA Not Working: Causes and How to Fix It

Short answer

Gravity Forms reCAPTCHA usually stops working because the site and secret keys do not match the reCAPTCHA version, your domain is missing from the Google key settings, or a caching or script optimization feature delays the reCAPTCHA script. Check the keys first, then exclude reCAPTCHA from optimization and look for another plugin loading its own copy.

Key takeaways

  • Keys only work with the reCAPTCHA type they were created for, so v2 and v3 keys are not interchangeable.
  • Every domain that shows the form must be listed in the key's settings in the Google admin console.
  • Delayed, combined or deferred JavaScript is a frequent cause of a missing or broken CAPTCHA.
  • Duplicate reCAPTCHA scripts from other plugins or themes can stop Gravity Forms validating submissions.
  • With v3, check the Spam entries view, because low-scoring visitors are flagged rather than shown an error.

Why is reCAPTCHA not working in Gravity Forms?

Gravity Forms reCAPTCHA usually fails because of wrong or mismatched keys, an unregistered domain, a script blocked by caching or optimization, or another plugin loading its own copy of reCAPTCHA.

The symptoms vary. Some sites show no CAPTCHA box at all. Others show the box, but every submission fails with an error such as The reCAPTCHA was invalid. With reCAPTCHA v3, real visitors may be marked as spam without any visible error.

Each symptom points to a different cause. This guide walks through them in the order they most often happen, from the quick key check to deeper script conflicts.

If you are new to the plugin, our guide on how to use Gravity Forms covers the basics of building and embedding a form first.

Which version of reCAPTCHA are you using?

Gravity Forms supports reCAPTCHA v2 through its built-in CAPTCHA field and reCAPTCHA v3 through the official reCAPTCHA Add-On, and each version needs its own matching keys.

The two setups work very differently:

SetupHow it appearsWhere you configure itKeys needed
CAPTCHA field (v2 checkbox)I'm not a robot checkboxForms > Settings > reCAPTCHA, then add the field to a formv2 checkbox keys
CAPTCHA field (v2 invisible)Badge, challenge only when suspiciousSame settings page, type set to invisiblev2 invisible keys
reCAPTCHA Add-On (v3)Badge only, score-basedAdd-on settings page plus per-form settingsv3 keys

Gravity Forms documents the field in its CAPTCHA field guide and the add-on in Setting up the reCAPTCHA Add-On.

Knowing which one your form uses matters. Many problems come from v3 keys pasted into v2 settings, or the other way round.

How do you check your reCAPTCHA keys?

Open the Google reCAPTCHA admin console, confirm the key type matches the Gravity Forms setup, then copy the site key and secret key again without extra spaces.

Keys are tied to one reCAPTCHA type. A v3 key pair will not work in the v2 checkbox field, and v2 keys will not work with the v3 add-on. Google does not show a helpful error for this; the form just fails.

Work through these checks:

  1. Sign in to the Google reCAPTCHA admin console and open the key used on your site
  2. Check the type shown in its settings (v2 checkbox, v2 invisible or v3)
  3. Copy the site key into the Site Key box in Gravity Forms
  4. Copy the secret key into the Secret Key box
  5. Save and reload the form in a private browser window

Watch for leading or trailing spaces when you paste. A single stray space in the secret key is enough to make every verification fail.

If you swapped keys between fields, the CAPTCHA may still display but always reject submissions. The site key is public and goes in the page; the secret key stays on the server.

Is your domain registered with Google?

reCAPTCHA only works on the domains listed for that key, so a missing domain, a new staging site or a changed domain will stop it from loading or validating.

In the key's settings in the admin console, look at the Domains list. Add every domain where the form runs. Google treats subdomains of a listed domain as covered, but a completely different domain needs its own entry.

This often bites after a migration. A form that worked on a staging address breaks on the live domain, or the reverse, because the key only lists one of them.

When the domain is wrong, the CAPTCHA box usually shows a red error message about an invalid domain for the site key. That message is a clear sign to update the list rather than chase plugin conflicts.

Why does the CAPTCHA box not appear at all?

A missing CAPTCHA box is usually caused by the field not being on the form, JavaScript being delayed or blocked by an optimization plugin, or a fatal JavaScript error elsewhere on the page.

First, confirm the basics. For v2, open the form editor and check that a CAPTCHA field is actually added. For v3, there is no box by design; you should only see the small reCAPTCHA badge, unless you chose to hide it.

Next, open the browser's developer console on the form page. Red errors about grecaptcha, blocked scripts or failed requests to Google point straight to the cause. The MDN guide to browser developer tools explains how to open the console in each browser.

If you see a JavaScript error from another plugin, fix that first. One broken script can stop every script that loads after it, including reCAPTCHA.

Can caching or script optimization break reCAPTCHA?

Yes, caching and JavaScript optimization are among the most common causes, because delaying, combining or deferring the reCAPTCHA script stops it from running before the visitor submits.

Features that commonly cause trouble include:

  • Delay JavaScript execution in performance plugins, which waits for user interaction before loading scripts
  • Combining or minifying JavaScript files, which can change load order
  • Deferring all scripts, including inline ones that Gravity Forms needs
  • Cloudflare Rocket Loader, which rewrites how scripts load
  • Long page cache lifetimes, which can serve an old form with stale security tokens

The fix is to exclude reCAPTCHA and Gravity Forms scripts from these features. Add exclusions for recaptcha, grecaptcha and gravityforms in your optimization plugin. Our guide to WP Rocket delay JavaScript exclusions shows how exclusions work in one popular plugin.

After changing settings, purge every cache layer. See how to clear cache in WordPress for plugin, server and CDN caches.

To confirm caching is the cause, test the form with optimization turned off. If it works, turn features back on one at a time until it breaks again.

Could another plugin be loading reCAPTCHA too?

Yes, if another plugin loads its own reCAPTCHA script, the two copies can clash, and the form may fail to render or validate.

Contact form plugins, login protection plugins, WooCommerce security add-ons and some themes all add reCAPTCHA. If one loads v3 across every page and Gravity Forms expects v2, the second script often fails.

Check by viewing the page source and searching for recaptcha/api.js. If it appears more than once, or with different parameters, you have duplicate loading.

Turn off reCAPTCHA in the other plugin, or limit it to the pages where that plugin's forms appear. If you are not sure which plugin is responsible, follow our plugin conflict troubleshooting steps on a staging copy.

Why are real submissions marked as spam with reCAPTCHA v3?

With v3, Google scores each visitor between 0.0 and 1.0, and if the score falls below your threshold, Gravity Forms treats the entry as spam instead of showing an error.

Google's reCAPTCHA v3 documentation suggests 0.5 as a starting threshold. Visitors on VPNs, privacy browsers or shared networks sometimes score lower and get caught.

Check Forms > Entries and switch to the Spam view for the form. If real enquiries are sitting there, lower the threshold slightly in the add-on settings and watch the results over a week.

You can also review scores in the Google admin console. A large share of low scores from real traffic suggests the threshold is too strict for your audience.

Do not drop the threshold too far. A very low value lets more bots through, which defeats the point of the check.

What other causes should you check?

Less common causes include server time drift, outdated Gravity Forms or add-on versions, firewall rules blocking Google, and AJAX form settings that reload a stale CAPTCHA token.

Work through this list if the main fixes did not help:

  • Update Gravity Forms and the reCAPTCHA Add-On to the latest versions
  • Ask your host whether outbound requests to Google's verification service are blocked
  • Check that the server clock is correct, since token checks are time-sensitive
  • Try the form with AJAX enabled and disabled to see if behaviour changes
  • Look for a security plugin or WAF rule that strips the reCAPTCHA response field

Gravity Forms has a built-in logging tool. Turn on logging under Forms > Settings, submit the form, then read the log for reCAPTCHA errors. The logging and debugging guide explains where logs are stored.

For PHP-level errors, WordPress debug mode can show what fails during submission. Turn it off again once you are done.

Are there alternatives if reCAPTCHA keeps failing?

Yes, you can rely on Gravity Forms' honeypot and anti-spam settings, or switch to a different CAPTCHA service such as Cloudflare Turnstile through a supported add-on.

Many sites block most spam with the built-in honeypot alone. It adds a hidden field that bots fill in and people never see, so it does not affect real visitors.

Turnstile is another option that many site owners prefer for privacy reasons. Our guide to Cloudflare Turnstile on WordPress explains how it works and how to add it.

For a broader spam plan, see how to stop contact form spam in WordPress. Combining two light methods often works better than one strict CAPTCHA.

Whatever you choose, test the form from a private window and a phone after every change. A form that silently fails costs more leads than a little spam.

Frequently asked questions

Why does Gravity Forms say the reCAPTCHA was invalid?

This error usually means the secret key does not match the site key, the keys belong to a different reCAPTCHA type, or the token expired before the form was submitted. Re-copy both keys from the Google admin console, check the key type, and make sure caching is not serving an old version of the page.

Can I use reCAPTCHA v2 and v3 on the same site?

You can, but each needs its own key pair, and running both on the same page can cause conflicts. Most sites pick one version for Gravity Forms. If another plugin uses a different version sitewide, limit it to the pages that need it so the scripts do not clash.

Do I need the reCAPTCHA Add-On for Gravity Forms?

Only for reCAPTCHA v3. The built-in CAPTCHA field covers reCAPTCHA v2 checkbox and invisible modes without an add-on. The reCAPTCHA Add-On adds score-based v3 checks, which run in the background without a checkbox, and it is available on Gravity Forms licenses that include official add-ons.

Why are my legitimate form entries going to spam?

With reCAPTCHA v3, entries from visitors who score below your threshold are marked as spam. People using VPNs, strict privacy settings or shared networks may score lower. Review the Spam view under Entries, and lower the threshold slightly if real messages are being caught.

Will a caching plugin always break reCAPTCHA?

No. Page caching on its own is usually fine. Problems tend to come from features that delay, combine or defer JavaScript, or from very long cache lifetimes. Excluding the reCAPTCHA and Gravity Forms scripts from those features, then purging the cache, fixes most cases.

Sources

  1. CAPTCHA field Gravity Forms
  2. Setting up the reCAPTCHA Add-On Gravity Forms
  3. reCAPTCHA v3 Google for Developers
  4. Logging and Debugging Gravity Forms
  5. Debugging in WordPress WordPress Developer Resources

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.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.