DD DevDome Track. Protect. Grow.
Security

Stop Spam Registrations in WordPress Without Annoying Real Users

Hundreds of fake users with gibberish names and throwaway emails. They are not targeting you; they are targeting every WordPress site with an open signup form.

On this page
  1. Step 1: close the door if you do not use it
  2. Step 2: if you need signups, know what a bot looks like
  3. Step 3: the quiet tricks that cost real users nothing
  4. Step 4: what not to do
  5. Step 5: clean up what is already there
  6. Shops, forums and memberships: when you cannot close the door
  7. Reading the signup log
  8. Keep it working

To stop spam registrations on a WordPress site, first ask whether you need registrations at all. Most sites do not, and one checkbox ends the problem. If you do need them, the fix is to make the bots fail quietly: a honeypot, a timing check, bot detection by behaviour, and email confirmation. What you should not do is put a CAPTCHA in front of real people to stop bots that pay a service to solve it anyway.

Step 1: close the door if you do not use it

Go to Settings, General, and look at Membership. If “Anyone can register” is ticked and you do not run a shop, forum, membership or community, untick it. Bots find open registration forms by scanning; a closed form is simply not there. This fixes the problem for the majority of sites that ask the question.

While you are there, check New User Default Role. It must be Subscriber. A default of Contributor, Author or anything higher turns every spam signup into an account that can create content, which is how spam posts appear.

Step 2: if you need signups, know what a bot looks like

Registration bots behave differently from people, and every difference is a signal:

  • No history. A real person visited a page, maybe several, before signing up. A bot posts to the registration endpoint directly with no prior request.
  • Instant submission. The form arrives filled in within a second of being loaded, or without being loaded at all.
  • No browser profile. Headless clients and scripts lack the normal browser fingerprint.
  • Datacenter origin. Signups from cloud provider IP ranges are rarely humans.
  • Pattern names and emails. Random letters, throwaway domains, the same name with different numbers.

DevDome Bot Protection scores requests on these kinds of signals, with a Record Bots mode that logs what it would have blocked before you turn blocking on. Run it in record mode for a week, read the log, confirm no real signup appears, then switch to blocking. No CAPTCHAs, no challenge pages, no account needed for local protection. We make it, so weigh that; the record-then-block order is what to insist on from any tool.

Step 3: the quiet tricks that cost real users nothing

Honeypot field. A form field hidden from humans by CSS that bots fill in because they fill every field. Any submission with it filled is dropped. Silent, free, surprisingly effective against simple bots.

Minimum time to submit. A form submitted under two seconds after loading was not filled by a person. Reject it without a message.

Email confirmation. Require a click on a confirmation link before the account is active. Bots with throwaway addresses mostly never confirm, and the ones that do have spent real effort for a subscriber account that can do nothing.

Disposable email rejection. A list of known throwaway domains, checked at signup. Not perfect, but it removes a large share.

None of these show the user anything. That is the point.

Step 4: what not to do

CAPTCHA on every form. Solving services cost bot operators fractions of a cent per puzzle. Your real visitors pay in frustration, and a measurable share abandon the form. If you add one, measure signups before and after.

Blocking whole countries from the site. Block the registration page by country if you must, never the public site, and only when you genuinely have no users there.

Ignoring it. Thousands of spam users slow the Users screen, bloat backups and fill your inbox with “new user” emails. One day one of them has a role it should not.

Step 5: clean up what is already there

Back up. Then on the Users screen, filter by Subscriber and sort by registration date. Spam arrives in clusters, so select the obvious runs and delete, attributing any content to nobody. For thousands of accounts, a WP-CLI loop over users registered in a date range is faster.

Before bulk deleting, check two things: whether any of them have a role above subscriber, which means a different incident, and whether any have content or orders, which means they may be real. An activity log that records every user creation with the source makes this review fast and shows you when the spam started.

Shops, forums and memberships: when you cannot close the door

Sites that genuinely need registration face the problem for real. On WooCommerce, keep account creation at checkout rather than a standalone registration page, because a bot gains nothing from creating an account it will not buy with, and the checkout form has its own validation. On forums and membership sites, require email confirmation before any posting right is granted, and give new accounts a probation period with no links allowed in their first posts. In all cases, make sure the registration endpoint is covered by the same bot detection as the login page; the bots that fill signup forms are the same bots that try passwords, and a tool that recognises them on one form recognises them on the other.

Reading the signup log

Once bot protection and the activity log are running, the registration events tell a clear story. Look at the hour-by-hour pattern: humans sign up during the day in your readers’ timezones, bots in bursts at any hour. Look at the origin: residential networks versus datacenter ranges. Look at the names and emails: real people have ordinary names and ordinary providers, bots have patterns. After a week you will know what your real signups look like, and anything outside that shape is worth a second look before it gets a role above subscriber.

Keep it working

Leave the activity log on so new user creation is visible, keep bot protection in blocking mode, and look at the signup count monthly. If spam returns, the bots have changed tactics; go back to record mode for a few days and see what they look like now. The quiet methods adapt; the puzzle never did.

Related reading: Country Blocker Plugins for WordPress Compared: Which One Is Safe to Switch On?.

Disclosure: DevDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.

Key takeaways

  • Most sites do not need open registration. If yours does not, turn it off in Settings and the problem ends.
  • If you need signups, detect the bots by how they behave: no page views before the form, no browser profile, datacenter IPs, instant submission.
  • Honeypots and time checks stop the dumb bots silently. Email confirmation stops the rest from doing anything useful.
  • CAPTCHAs cost you real signups and are solved by services for cents. Treat them as a last resort.
  • Clean up existing fake users in bulk, but check roles first: a spam account with editor rights is a different incident.

Sources

  1. WordPress.org: Settings General screen : the Membership and New User Default Role options
  2. WordPress Developer Resources: registration_errors filter : where plugins reject a registration before it is created
  3. WooCommerce: account settings : registration options on checkout and account pages

Links last checked October 17, 2026.

Frequently asked questions

Why am I getting fake registrations if I have no membership?

Because Anyone can register is ticked in Settings, usually from a theme demo or an old plugin. Bots scan for open registration forms and submit to all of them. Untick it unless you run a shop, forum or membership that needs it.

Are spam registrations dangerous?

At subscriber level they are clutter: bloated user tables and spam in your email. They become dangerous if the default role is higher than subscriber, or if a plugin lets subscribers upload files or post content. Check the default role today.

Do I need a CAPTCHA on the registration form?

Usually not. A honeypot field, a minimum time-to-submit, bot detection and email confirmation stop the bulk without a puzzle. Add a CAPTCHA only if those fail, and measure how many real signups you lose.

How do I delete hundreds of spam users?

Filter the Users screen by role and registration date, select all, and delete with content attributed to nobody. A WP-CLI loop is faster for thousands. Back up first and check that none of them have content or elevated roles.

DevDome Team WordPress plugin builders

The DevDome team builds lightweight, performance-first WordPress plugins and free tools for site owners, founders and marketers. We write about the exact problems our plugins solve, in plain language for people who run real sites.