Contact form spam: how to stop it without blocking real customers

Almost every small business website with a contact form gets spam through it eventually. Offers of SEO services, links to dodgy sites, the same message in five languages. It's irritating, but the spam itself isn't the real danger. The danger is a fix that's too aggressive, so a genuine customer fills in your form, gets an error or a puzzle they can't solve, and rings someone else.

So the goal isn't "zero spam". It's "almost no spam, and no lost enquiries". Here's the layered approach I use on the sites I build and look after.

1. Start with checks the visitor never sees

The cheapest filters cost your customers nothing:

  • A honeypot field. This is an extra form field hidden from people but visible to simple bots, which tend to fill in every box they find. If it comes back filled in, the submission is dropped. Most WordPress form plugins have this as a setting.
  • A minimum time check. A person takes at least a few seconds to type a message. A submission that arrives a second after the page loaded almost certainly wasn't typed by a person.
  • Server-side validation. Check the email address looks like an email address and the required fields are actually filled in, on the server, not just in the browser.

These won't stop everything, but they quietly remove a lot of the lazy, automated junk.

2. Add a low-friction challenge if you still need one

If spam is still getting through, the next step is a bot check. The old image puzzles ("click every traffic light") are the option I'd avoid, because they're hard work on a phone and a real barrier for some people with disabilities.

Two options I'd look at instead:

  • Cloudflare Turnstile. It usually runs in the background with no puzzle at all. The free plan covers up to 20 widgets with unlimited verifications, and you don't need to host your site with Cloudflare to use it.
  • Google reCAPTCHA. Widely supported by form plugins. It's now managed through Google Cloud, and Google's billing page lists a free allowance of 10,000 assessments a month per organisation, which is plenty for a typical small business site.

Whichever you pick, the important part is that the response is verified on the server. A widget on the page that nothing checks behind the scenes only stops the very laziest bots.

3. Filter the content, but don't delete it

For spam that's written by people or by better bots, a content filter helps. On WordPress, that's often Akismet or a similar service, and many form plugins can block submissions containing links or certain words.

My rule here: send suspicious messages to a spam folder or log, never straight to the bin. Filters make mistakes. If a real customer's message gets flagged, you want to be able to find it, not discover months later that you've been missing enquiries.

4. Make sure the real messages actually arrive

This is the part that catches people out. A contact form can stop all the spam perfectly and still lose genuine enquiries because the notification email never reaches your inbox.

A few things worth checking:

  • How the site sends email. Many WordPress sites send through the web server's built-in mail function, which inbox providers often treat as suspicious. Sending through a proper email service (via an SMTP plugin, for example) is usually more reliable.
  • Your domain's email records. SPF, DKIM and DMARC tell inbox providers which services are allowed to send email for your domain. If your website isn't covered, its messages are more likely to land in junk.
  • A copy stored on the site. Saving each submission in the website's admin area as well as emailing it gives you a backup if an email goes missing.
  • A real test. Every so often, fill in your own form from your phone and check the message arrives where you expect it.

5. Keep it accessible and honest

A form that blocks spam but frustrates people isn't doing its job. Error messages should say what went wrong in plain language, the form should work with a keyboard and a screen reader, and if your bot check sends data to a third party like Google or Cloudflare, it's worth mentioning that in your privacy statement.

Where I fit in

I build and look after WordPress and WooCommerce sites for small businesses around New Zealand, and the same approach applies to forms in the custom sites and apps I build. If your contact form is drowning in spam, or you're not sure your enquiries are all getting through, send me a short note and I'll take a look.