Lorixen.
EN

Stopping contact form spam without annoying real customers

Short answer: Layer cheap, invisible defences before reaching for a puzzle. A honeypot field, a minimum time-to-submit check and proper server-side validation stop most automated junk at no cost to real visitors; add an invisible or low-friction check such as Cloudflare Turnstile or reCAPTCHA v3 if bots still get through, and a content filter such as Akismet for human-typed spam. Picture puzzles and distorted text should be the last resort, because they block some genuine customers.

Spam on a contact form is more than an irritation. It buries real enquiries, trains you to skim the inbox, and can make your own email provider treat form notifications as junk. The good news is that most of it is cheap to stop, as long as you match the defence to the kind of spam you're getting.

Know which spam you have

Look at the last 20 junk messages before choosing a fix:

  • Automated bot spam: nonsense text, links, the same message repeated, submissions seconds apart. Usually caught by honeypots, time checks and bot-detection services.
  • Link spam typed by humans or semi-automated tools: SEO offers, "I noticed your website" pitches, crypto links. Bot checks struggle here because a person (or a tool imitating one) filled it in. Content filtering works better.
  • Targeted abuse: someone hammering one form, often to test stolen card details on a payment form or to flood your inbox. Rate limiting is the answer.

The defences compared

Defence Effort to add Friction for real visitors Accessibility Cost
Honeypot field Low (most form plugins have it) None Good if hidden properly from screen readers and keyboard focus Free
Time trap (reject forms submitted too fast) Low None, if the limit is a few seconds Good Free
Server-side validation (required fields, valid email and phone formats, length limits, blocking links in the name field) Low to medium None Good, with clear error messages Free
Rate limiting (per IP or per session) Medium (host, firewall or plugin) None for normal use Good Often included with hosting or a firewall service
Cloudflare Turnstile Medium (site key, widget, server check) Usually none; sometimes a checkbox Cloudflare states WCAG 2.2 AA conformance Check Cloudflare's current plans page
reCAPTCHA v3 Medium (keys, script, server check, score threshold) None visible; you decide what low scores trigger No puzzle shown by v3 itself Check Google's current pricing page
Akismet (content filtering) Low on supported WordPress form plugins None Good Needs an Akismet subscription
Image or text puzzle CAPTCHA Low High Poor for many users Varies

Honeypots and time traps

A honeypot is an extra form field hidden from humans. Real visitors never fill it in; simple bots fill in every field and get rejected. Hide it with CSS rather than type="hidden", label it clearly for anyone using a screen reader ("leave this empty"), and remove it from keyboard tab order.

A time trap records when the form loaded and rejects submissions made faster than a person could type, such as under three seconds. Keep the limit short so fast typists and autofill users aren't caught.

Both are invisible and free. Their weakness is that better bots learn to skip them, so treat them as the first layer, not the only one.

Cloudflare Turnstile

Turnstile runs small non-interactive JavaScript challenges in the browser and, according to Cloudflare's documentation, can be used without routing your site's traffic through Cloudflare. Its widget types are Managed (recommended by Cloudflare, showing a checkbox only when risk is higher), Non-interactive and Invisible.

The detail most DIY setups miss: Cloudflare says server-side validation through its Siteverify API is mandatory, because the widget alone does not protect your form. Tokens can be forged, each token is valid for 300 seconds, and each can be validated only once (as of November 2026). If your plugin only adds the widget and never checks the token on the server, it isn't protecting anything.

reCAPTCHA v3

reCAPTCHA v3 returns a score for each request without showing a challenge: per Google's developer guide, 1.0 is very likely a good interaction and 0.0 very likely a bot, and Google suggests starting with a threshold of 0.5 and adjusting it from your admin console. Tokens expire after two minutes, so the check should run when the visitor presses Send, not when the page loads. Rather than blocking low scores outright, route them to a "possible spam" folder you review weekly.

Note that Google's reCAPTCHA v3 developer page now carries a notice pointing to its Google Cloud Fraud Defense documentation. If you're setting it up fresh, read Google's current product pages first.

Akismet for human-typed spam

Akismet checks the content of a submission against its spam database. Its support page lists integrations with WordPress form plugins: Jetpack's contact form is checked automatically, Contact Form 7 needs specific options added to form fields (and the Flamingo plugin if you want to review and mark submissions), Gravity Forms needs a dedicated add-on configured per form, and Fluent Forms enables it in global settings. Akismet notes that once activated, it checks both blog comments and contact forms. It needs an active subscription.

Rate limiting

If one IP address submits ten forms in a minute, no customer is behind it. Rate limits usually live at your host, a web application firewall or a security plugin. They're especially useful on booking and payment forms.

What not to do

  • Don't hide your email address entirely. Some customers prefer email, and an obfuscated address or "contact form only" policy loses enquiries. A plain email address on the contact page attracts some spam, which your email provider's filters handle.
  • Don't add a picture puzzle as the first fix. W3C's guidance on accessible authentication notes that maths CAPTCHAs, visual puzzles and transcribing text are cognitive tests that exclude some people, and an audio version that must be transcribed doesn't remove the problem. That guidance is written for log-ins, but the lesson applies to any form a customer needs to get through.
  • Don't silently delete suspected spam. Quarantine it. A false positive might be a real customer.
  • Don't stack three services at once. Add one layer, watch for a week, then add the next if needed.
  • Brochure site with one contact form: honeypot + time trap + server-side validation. Add Akismet if you're on WordPress and still getting pitched by humans.
  • Busy service business (quote and booking forms): the above plus Turnstile (Managed mode) or reCAPTCHA v3 with low scores sent to review, plus rate limiting on the booking form.
  • Shop or member site with log-ins and payments: bot detection on sign-up, log-in and checkout, rate limits at the firewall, and server-side validation everywhere. Avoid puzzles on log-in.

FAQ

Does Turnstile or reCAPTCHA slow my page down?

Both load scripts from the provider. Load them only on pages with forms, not site-wide.

Why am I still getting spam with reCAPTCHA installed?

Common causes are a missing server-side check, a threshold set too low, or human-typed spam that bot detection isn't designed to stop. Check the server verification first, then add a content filter.

Is a honeypot enough on its own?

Sometimes, for low-traffic sites. Watch your inbox for a fortnight after adding it; if junk keeps arriving, add the next layer.

Will spam protection stop my own test submissions?

It can, especially time traps if you autofill. Test from a normal browser at a normal speed, and check your quarantine folder.

A contact form should be easy for customers and dull for bots, and we can tune yours so only real enquiries land.

Sources

WhatsAppLet’s talk