· 5 min read · Mert Tati
How to Stop WordPress Spam Without reCAPTCHA: Comments, Product Reviews and Elementor Forms
Stop WordPress comment spam, WooCommerce review spam and Elementor, CF7 and WPForms spam without reCAPTCHA: honeypots, time checks.
Short answer: most WordPress spam comes from bots, not people, and you don't need to make visitors pick out traffic lights to filter them. Combine an invisible trap field, a minimum time to fill out the form, a signed token that isn't affected by caching, and submission limits per IP and per email address, and the vast majority of spam stops without reCAPTCHA. Whatever suspicious submissions remain should be quarantined, not deleted.

Why reCAPTCHA isn't always the right answer
- It frustrates real visitors: image puzzles, especially on mobile, make people abandon forms, and that means lost leads and orders.
- It's third-party code: data goes to Google on every page view. Under KVKK (Turkey's personal data protection law) and cookie consent rules, that's a separate processing activity you have to account for, and it slows your pages down too.
- It creates accessibility problems: puzzles are a serious barrier for visually impaired visitors.
- Bots can get past it anyway: CAPTCHA-solving services are cheap, so for a determined spammer reCAPTCHA isn't a wall, just a cost.
Where does spam come from? Real examples
Spam often sneaks in through a forgotten corner of the site. On one client's site, we found that hundreds of bot comments had all been posted on the “Hello world!” sample post that comes with every WordPress install; it had simply never been taken down. On another site, the spam landing in the inbox wasn't coming from the contact form at all, but from a footer newsletter form that had been copied from another page and forgotten. These submissions shared a telltale signature: an empty referrer and an empty page URL, meaning the form was being posted directly without the page ever being opened.
When we tackled the nine WordPress sites on our server together, we cleaned out 2,478 spam entries. The common lesson: first shrink the attack surface (turn off comments you don't use, remove forgotten forms), then protect the forms that remain.
How to filter out bots without reCAPTCHA

- Invisible trap field (honeypot): a field humans can't see but bots fill in. Any submission with it filled in is a bot.
- Minimum fill time: a form submitted within 2-3 seconds of the page loading wasn't filled out by a human.
- Signed token: proves the form really came from your page. Bots that POST directly can't supply it. The token must be generated in a way that page caching doesn't affect; otherwise real visitors on cached pages get rejected too.
- Submission limits: no more than a set number of submissions per hour from the same IP or the same email address. Gmail dot and +tag tricks ([email protected]) should be treated as the same address.
- Content filters: messages with lots of links, banned words and disposable email domains.
- Blocklists: by IP, IP range (CIDR), email address and domain.
Quarantine instead of delete
No filter is perfect. So submissions that are definitely bots (trap field filled, no token) should be rejected, while suspicious submissions that might be human should be quarantined rather than deleted. That way no genuine customer inquiry gets lost, and you just glance at the quarantine every few days. When rolling out new protection, running a log-only test mode for the first few days is the safest way to see whether you're getting false positives.
Comments and WooCommerce reviews
If you don't use blog comments, turn them off completely: it's the quickest way to get spam down to zero. Don't forget to disable pingbacks and trackbacks while you're at it. WooCommerce product reviews, on the other hand, are valuable for sales and should stay on; here the best results come from combining the “only verified owners can leave reviews” setting with the bot filters above.
Elementor, Contact Form 7, WPForms and other form plugins
Every form plugin has its own spam settings, but they all work differently and log things in different places. If your site runs more than one form plugin (which is common: the contact form from one plugin, the newsletter form from Elementor), consolidating protection into a single layer makes both management and reporting easier. For forms that only ask for an email address, like newsletter signups, you can also use a stricter mode that only accepts addresses from major email providers.
How we do it with Hushfort
The Spam Shield module in the Hushfort plugin applies all of the methods above without reCAPTCHA: an invisible trap field, minimum fill time, a cache-proof signed token, hourly limits per unique IP and unique email, plus filters for disposable email, link count and banned words. It works with Elementor Pro, Contact Form 7, WPForms, Gravity Forms, Fluent Forms and Forminator forms, as well as WordPress comments and WooCommerce reviews. Form and comment data never leaves your server; the plugin sends no telemetry and loads no third-party code.
If you'd like to tackle login security alongside spam, check out our guide to changing the WordPress login URL.
Frequently asked questions
Is a honeypot enough on its own? Against simple bots, yes; against advanced bots, no. Advanced bots can skip hidden fields, so a honeypot should be used together with timing checks, a signed token and submission limits.
Should I use Akismet? Akismet does a good job with content analysis, but it sends comment and form data to an external service and is paid for commercial sites. If you want your data to stay on your server, local filters should come first.
How do I find where spam is coming from? Look at the page URL and referrer in the spam email you received. If those fields are empty, the form is being posted directly; if they're filled in, they show which form on which page was used. Forgotten duplicate forms are the most common culprit.
Bottom line: shrink your attack surface first, then apply invisible bot filters to the forms that remain. Reject definite bots, quarantine the suspicious ones, and start any new protection in test mode. Only consider reCAPTCHA if all of that isn't enough.