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 Honeypot Not Working: Causes and How to Fix It

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

Short answer

The Gravity Forms honeypot usually fails because it is not enabled for that form, bots or humans skip the hidden field, or caching and delayed scripts break its checks. Turn it on in Form Settings, update Gravity Forms, exclude form scripts from optimization and add Turnstile or reCAPTCHA if spam continues.

Key takeaways

  • The honeypot is a per-form setting under Form Settings > Form Options.
  • It only stops simple bots, not smarter bots or human spammers.
  • Script delay and page caching can flag real visitors as spam.
  • Save flagged entries as spam while testing so nothing is lost.
  • Add Turnstile, reCAPTCHA or Akismet when the honeypot is not enough.

Why is the Gravity Forms honeypot not working?

The honeypot usually seems broken because it is switched off for that form, smarter bots and human spammers skip the hidden field, or caching and script problems flag real visitors as spam.

A honeypot is a hidden field that people never see. Simple bots fill in every field they find, so a value in the hidden field marks the submission as spam. It is quiet, free and invisible to visitors.

When people say the honeypot is not working, they usually mean one of two opposite problems:

ProblemWhat you seeUsual cause
Spam still gets throughJunk entries and emails keep arrivingHoneypot off, or bots that skip hidden fields
Real entries marked as spamGenuine leads land in the Spam listScript loading or caching problems
Entries vanishVisitors submit, but no entry appearsHoneypot set to discard flagged entries
No change after enablingSpam level stays the sameCached form, or spam comes from humans

The fix depends on which group you are in. The sections below cover each one.

Is the honeypot turned on for the form?

Open the form, go to Settings > Form Settings, scroll to Form Options and make sure Anti-spam honeypot is checked, then save.

The honeypot is a per-form setting. Turning it on for one form does not cover the others. Check every form that receives spam.

In the same area you can choose what happens when the honeypot catches a submission. One option discards the submission so no entry is created. The other creates the entry and marks it as spam.

While troubleshooting, choose the option that saves the entry as spam. That way you can see what is caught and spot real visitors who were flagged by mistake.

Gravity Forms explains the honeypot and other options in its spam prevention solutions guide.

Why does spam still get through with the honeypot on?

Spam still arrives because many modern bots ignore hidden fields, some spam is typed by real people, and a honeypot alone cannot catch either.

A honeypot only stops bots that blindly fill every field. Better bots read the page, skip hidden inputs and run JavaScript. Paid spammers who fill forms by hand will never touch a hidden field.

Look at the spam that arrives. If messages are well written, mention your business and come in small numbers, they are likely human. A honeypot will not stop them.

For those cases, add another layer:

  • CAPTCHA or Turnstile to challenge suspicious visitors
  • Akismet to score message content against known spam
  • Field rules such as blocking links in the message box
  • Rate limits at the firewall to slow repeat senders

Our guide on stopping contact form spam compares these methods across form plugins.

Why are real submissions marked as spam?

Genuine visitors get flagged when the form's JavaScript does not load properly, often because of caching, script optimization or old cached form markup.

Newer Gravity Forms versions strengthen the honeypot with a JavaScript based check, described in the honeypot enhancements documentation. The check relies on the form scripts running normally in the visitor's browser.

If a caching or optimization plugin delays, defers or strips those scripts, the check can fail for real people. Their entries then land in the Spam list. Users describe this pattern in a Gravity Forms community thread about the honeypot sending all entries to spam.

To fix it:

  1. Go to Entries, filter by Spam, and confirm real people are in there
  2. Turn off JavaScript delay, defer and combine in your caching plugin as a test
  3. Exclude Gravity Forms scripts and jQuery from those features
  4. Exclude the form page from page caching, or shorten its cache lifetime
  5. Clear every cache layer, then submit a test entry

Our guide on clearing cache in WordPress covers plugin, server and CDN caches.

Could an outdated Gravity Forms version be the cause?

Yes, older versions have a weaker honeypot and older bugs, so update Gravity Forms and its add-ons before changing other settings.

Check your version under Forms > System Status. If it is behind, back up and update. Our guide on how to update Gravity Forms walks through the safe order.

After updating, clear caches. Old cached HTML can contain form markup from the previous version, which may not match the new checks.

Can caching break the honeypot?

Yes, full page caching can serve stale form markup and security tokens, which causes both missed spam and false positives.

A cached page is a snapshot. If the form changes, or the honeypot setting changes, visitors keep receiving the old snapshot until the cache expires.

Steps that help:

  • Clear the page cache after changing form settings
  • Exclude pages with important forms from caching if problems continue
  • Check CDN caching rules too, not just the WordPress plugin
  • Avoid HTML minify settings that rewrite form markup

If you use Cloudflare, page rules or cache rules can cache full HTML. Our guide on Cloudflare cache rules for WordPress explains how to exclude specific pages.

Should you add a CAPTCHA or Turnstile as well?

If spam continues after the honeypot is working, add a challenge such as reCAPTCHA or Cloudflare Turnstile to the forms that receive the most spam.

Gravity Forms has official add-ons for Google reCAPTCHA and for Cloudflare Turnstile, depending on your license. Turnstile is a low-friction option that usually runs without puzzles. Cloudflare's Turnstile documentation explains how it works.

A free alternative is the Gravity Forms Zero Spam plugin, which adds a JavaScript key check. Use one main anti-spam layer plus the honeypot. Stacking many plugins makes conflicts more likely.

Place challenges on the forms that need them. A simple newsletter form may only need the honeypot, while a quote form that triggers sales calls may need a stronger check.

How do you test the honeypot?

Submit a normal entry to confirm it saves, then check the Spam list after real traffic to see what is caught and what slips through.

You cannot easily fake a bot from your own browser, so testing is mostly about avoiding false positives:

  • Submit the form in a private window on desktop and on a phone
  • Confirm the entry appears under Entries, not under Spam
  • Confirm the notification email arrives
  • Review the Spam list every few days for a week

If notifications stop after enabling anti-spam features, check whether the entries were marked as spam. Spam entries do not send notifications. Our guide on Gravity Forms notifications not sending covers other email causes.

What else stops spam reaching your forms?

Block bad bots at the firewall, keep form pages lean, and avoid publishing raw form endpoints that attract automated posts.

Server level protection helps every form at once. Firewall rules, bot filtering and rate limiting stop many requests before WordPress loads. Our guide on blocking bad bots in WordPress covers practical options.

Watch for spam that targets one form only. That form may be listed on spam lists. Moving it to a new page or changing its ID sometimes cuts the volume quickly.

If you are new to the plugin's settings, our guide on how to use Gravity Forms explains form settings, notifications and entries.

Frequently asked questions

Where is the honeypot setting in Gravity Forms?

Open the form, go to Settings > Form Settings and scroll to Form Options. Tick Anti-spam honeypot and save. Repeat this for every form you want to protect.

Does the Gravity Forms honeypot affect real visitors?

Normally no, because the field is hidden and real people never fill it. Problems only appear when caching or script optimization stops the form scripts from running properly.

Why do spam entries not send notifications?

Gravity Forms does not send notifications for entries marked as spam. This is intended, so spam does not fill your inbox. Check the Spam list under Entries to review them.

Is the honeypot enough to stop spam?

For low-traffic sites it often stops most automated spam. Busy sites and forms targeted by smarter bots usually need a second layer, such as Turnstile, reCAPTCHA or Akismet.

Can I recover entries the honeypot discarded?

No. If the form is set to discard flagged submissions, no entry is saved. Switch the setting to create entries marked as spam so you can review and restore real ones.

Sources

  1. Enhancements to the Spam Honeypot Gravity Forms Documentation
  2. A Solutions Guide to Spam Prevention Gravity Forms Documentation
  3. GravityForms Honeypot sending all to spam? Gravity Forms Community
  4. Gravity Forms Zero Spam WordPress.org Plugins
  5. Turnstile Cloudflare Docs

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.