Skip to content
TatiCreative
All articles

· 6 min read · Mert Tati

How to Stop Fake User Registrations and Bot Traffic on WordPress

Thousands of fake users overnight, a maxed-out SMTP quota, a crawling server: how to stop WordPress and WooCommerce spam signups and bot floods.

Short answer: to stop fake user registrations you need an hourly signup limit per IP and per network, a site-wide cap, and an automatic circuit breaker for distributed floods. Disposable email addresses should be blocked, and existing fake accounts should be cleaned up after taking a backup. For bot traffic that slows your site down, give each IP a per-minute request budget, and run that check before your theme and plugins load.

Toy robots lined up in a row, fake user registrations

Symptoms: how to spot a fake registration flood

  • Your inbox is filling up with “New user registration” notifications.
  • Your email provider warns that your sending quota is used up, and order and password reset emails aren't going out.
  • Your Users list is full of gibberish names, emails made of random letters and hundreds of accounts from the same domain.
  • Your database keeps growing, backups take longer and the admin dashboard gets sluggish.

We know this one well: a site we manage received roughly 10,000 registration requests in a single hour. Because every signup triggered a welcome email, the real damage wasn't in the users table but on the email side. Gmail-based sending has a daily limit, and once that limit is burned on fake accounts, real customers stop getting their order emails. That's why a fake registration flood isn't just a security problem; it's a direct sales problem.

1. Registration limits: per IP and per network

Don't accept more than a few signups per hour from the same IP address. With IPv6, a single user can control a huge number of addresses, so the limit should apply to the /64 block rather than to a single address. Since bots can cycle through different addresses on the same network, you also need a second limit per network (IPv4 /24, IPv6 /48).

2. A site-wide cap and a circuit breaker

A serious flood comes from thousands of different IPs and never trips any per-IP limit. To counter this, set a site-wide hourly cap: once it's exceeded, a circuit breaker kicks in and new registrations either pause temporarily or switch to “soft mode.” In soft mode, accounts are still created but held for approval and no emails are sent to them, so you don't lose a genuine user and you protect your email quota at the same time.

3. Unique emails and disposable addresses

Bots frequently use disposable email services and Gmail's dot and +tag tricks: [email protected] and [email protected] are the same inbox. At registration, these variations should be treated as the same address, and known disposable email domains should be rejected. Adding invisible bot traps to the registration form also helps, but real buyers creating an account at WooCommerce checkout should be exempt from these checks.

4. Safely clean up existing fake users

Once the flood stops, you're left with thousands of fake accounts. Deleting them by hand from the Users screen is slow and risks removing a real customer. The right order is: filter accounts created after a certain date that have no orders, comments or posts, preview the list, take a backup before deleting, bulk delete, and keep the option to restore for a while.

5. Bot traffic and request floods: rate limiting

Controlled checkpoint split down the middle, rate limiting

The same bots behind fake signups often hammer the site in other ways too: thousands of search requests, 404 floods probing for nonexistent URLs, add-to-cart and form submission floods, and fake crawlers posing as Googlebot. Pages served from cache barely touch the server; the real load comes from requests that run PHP and database queries.

  • Give each IP a per-minute point budget: heavy requests (search, 404s, form submissions) cost more points, and pages served from cache cost nothing.
  • Return a 429 (Too Many Requests) with a Retry-After header to any IP that exceeds its budget, for a few minutes.
  • Run this check at the earliest possible point, before the theme and plugins load; otherwise even the requests you reject still strain the server.
  • Verify requests that claim to be Googlebot or Bingbot: real search crawlers should be exempt from the budget, and fake ones should be blocked.
  • Never block WooCommerce checkout or payment provider callbacks (iyzico, PayTR and similar Turkish payment gateways) under any circumstances.

The real-IP trap behind Cloudflare

If your site sits behind Cloudflare, the address your server sees is a Cloudflare edge server. If your rate limit counts that address, every visitor passing through the same edge server is counted as one person, and real users get blocked together. We ran into this on a client site and fixed it. The right fix is to read the visitor's IP from the Cloudflare header, but only trust that header when the request actually comes from Cloudflare's IP ranges. Otherwise an attacker can send a fake header and appear to be a different IP on every request.

Monitor first, then protect

Switching a new rate limit or registration rule straight into blocking mode risks locking real customers out. We recommend spending the first few days in a log-only test mode. When we turned on load protection in test mode on the West Riders Custom store, every early entry came from data center bots; real visitors weren't affected. Once you've seen that, it's safe to switch to protection.

Registration and load protection with Hushfort

Every step in this article is built into the Registration Protection and Load Protection modules of the Hushfort WordPress security plugin: IPv6 /64-aware signup limits per IP and per network, a site-wide cap and circuit breaker, soft mode, blocking of disposable emails and Gmail variations, and a Cleanup Wizard with preview, backup and 30-day restore. Load Protection offers a per-minute point budget, 429 and Retry-After, fake Googlebot/Bingbot blocking and a self-expiring emergency mode. It works with Cloudflare IP verification, and WooCommerce checkout is never blocked by any module.

More in this series: Changing the WordPress login URL and hiding wp-admin and Stopping WordPress spam without reCAPTCHA.

Frequently asked questions

Can I turn off user registration completely? If you don't need memberships, yes: go to Settings → General and uncheck “Anyone can register.” In WooCommerce, though, account creation at checkout usually stays on, so registration limits need to step in there.

Isn't my hosting provider's firewall enough? Server- and CDN-level protection stops brute-force attacks, but it doesn't understand WordPress-specific behavior (registrations, comments, cart, search). The two layers complement each other.

Do 429 errors hurt SEO? Not as long as real search crawlers are exempt from the budget. A 429 with Retry-After is the standard way for a server to say “I'm busy right now, come back later,” and search engines recognize it.

Bottom line: put per-IP, per-network and site-wide limits on registration; protect your email quota with a circuit breaker; block disposable emails and clean up fake users after taking a backup. Rate-limit bot traffic at the earliest possible point, read the correct IP behind Cloudflare, and run every new rule in test mode first.

More articles

Request a call

Describe your project in 60 seconds.

Fill in the short pre-form; we'll match you with the right person and reply within 24 hours.

A native English-speaking Project Lead from our team runs your project with you.

01 / 04

Which areas do you need help with?

  • UI/UX & Product Development
  • AI Solutions
  • Graphic & Brand Design
  • Software & Hosting
  • Studio & Production
  • Social Media
  • Digital Marketing
  • Digital Transformation
  • Industrial IoT (IIoT)
Average response time< 24 hours