Glossary
What is Honeypot field?
How it works
The field is in the form’s code but hidden from view and from screen readers. A person never touches it; a simple bot reading the page’s fields fills it in like any other.
On submit, the server checks the field. If it has a value, the submission is dropped or marked as spam. Honeypots are usually combined with other checks, because smarter bots learn to skip them.
Example
A contact form starts receiving dozens of junk messages a day. Adding a honeypot field and a rate limit removes most of them, without adding a CAPTCHA that real visitors would have to solve.
Tips
- Hide the field properly from screen readers too, so assistive technology users aren’t caught out.
- Combine it with rate limits and a background check like Turnstile.
- Keep a spam folder rather than deleting outright, so you can rescue false positives.
Honeypot field in FormsAI
Every public FormsAI form has spam protection on every plan: Cloudflare Turnstile, which checks that a person is submitting, usually without them noticing, a hidden honeypot field, rate limits, and a check for answers given impossibly fast or stuffed with links. Suspicious responses go to a Spam tab, out of your results, exports, integrations and plan count.
FAQ
Honeypot field, answered
Is a honeypot better than a CAPTCHA?
It’s invisible to real people, so it doesn’t cost completions. It catches simpler bots; pair it with a background check like Turnstile for the rest.
Can a honeypot block real people?
Only if it’s badly hidden, for example visible to a screen reader or filled by a browser’s autofill. A properly hidden field is never touched by people.