How to stop form spam without punishing real people
A hidden spam trap, a bot check only where you need it, and field rules against link spam, layered without adding friction.
3 min read
On this page
Spam is the tax every public form pays. Most teams answer it with a puzzle for every visitor, and real people pay the price: slower forms, abandoned signups, and still a few bots getting through. A better approach stacks cheap, invisible checks first and only asks humans to prove anything when traffic really calls for it. Here is how to layer them in Formpik, from the one you should always have to the one you add later.
Start with the spam trap
Every Formpik form has a Spam trap field, and it is on by default. It is a hidden input called _gotcha that people never see and never fill in. Bots fill in every field they find, so a value there means a bot. Those submissions are stored under Spam, and no flow runs for them, so nothing reaches Slack or your inbox.
<input type="text" name="_gotcha" tabindex="-1" autocomplete="off" style="display:none">Keep it hidden and empty. If real submissions start landing under Spam, the usual cause is a browser autofilling a trap that was left visible.
Refuse what the form never needs
A lot of spam gives itself away. A contact form rarely needs five links in the message, and a sales form rarely wants a throwaway mailbox. Field rules let you refuse those answers at the door:
- Most links on a message field. Set it to 0 and most link spam stops.
- Blocked words for the phrases you keep seeing.
- Fewest words on a message, so one word answers do not get through.
- No throwaway emails to refuse temporary mailboxes, or Work emails only to refuse free ones such as gmail.com on a business form.
With Refuse answers that break the field rules turned on, a submission that breaks a rule is refused and nothing is stored. The visitor sees one message per field explaining what to fix, so a real person can correct it in seconds. With it off, the submission is kept and flagged instead.
Limit how often one visitor can send
Bots that do get through tend to send in bursts. Limit per visitor in the form's settings caps how many submissions one address can send in an hour. Formpik also refuses more than 120 posts a minute from one address across every form, and drops an exact repeat sent within 10 seconds, which catches double clicks as well as scripts.
Only accept your own website
Spam scripts often post straight to a form's address from somewhere else. Add your domain under Allowed websites, and posts from any other site are refused. Your own server code can still post with an API key in the Authorization header.
Add a bot check when traffic grows
For a busy page, choose Cloudflare Turnstile or Google reCAPTCHA as the Bot check in the form's settings and add the widget to your form. A missing or failed check stores the submission as spam and runs no flows. Turnstile usually decides without asking the visitor to do anything, which keeps the form fast for real people.
Look at what got caught
Spam is held aside, never deleted on the spot. Filter the Submissions inbox by status to see it. If a real person was caught, open the submission and choose Not spam: it moves back to the inbox and its flows run for the first time. If something slipped through, Mark as spam moves it out of the way.
A sensible starting point
| Your form | Turn on |
|---|---|
| A small site | Spam trap, Most links set to 0, Allowed websites |
| A busy landing page | All of the above, plus Turnstile and a limit per visitor |
| A business signup | All of the above, plus No throwaway emails or Work emails only |
The security and spam guide lists every setting, and the forms guide covers each field rule.