People keep saying forums and private communities are coming back. As feeds fill up with generated filler, a quiet place with real people and a searchable history starts to look valuable again. Plenty of others disagree and say forums never really come back. Either way, the people running small forums have run into the same practical problem: once a place is worth visiting, it's worth spamming.
Across the communities we follow, the same situations come up again and again. An independent forum operator says plainly that they don't have the resources of the big social networks to fight slop and bot sign-ups. A site owner asks why bots register accounts on a WordPress site that has no public posting at all. A moderator describes "sleeper" accounts that sign up, sit quietly for weeks, then edit an old harmless post into a link farm. Several people warn about a popular forum plugin with a database injection flaw under active attack, and remind everyone that the fix only helps if someone actually installs the update. A person running a tiny forum says what keeps it alive is a calm weekly digest email, not growth hacks.
Put together, the picture is consistent. Small forums don't lose to one big attack. They lose to a steady drip of junk that wears out the one or two volunteers who moderate.
So here is how we think about defence, ordered by how much each layer costs real members. Start at the top and only move down when you need to.
Layer 1: make your forum boring to automated sign-ups
Most bots are not clever. They hit every signup form they can find and see what sticks.
- Add a honeypot field at signup: a hidden field that people never see and bots fill in. It costs members nothing.
- Add a minimum time to submit. A form completed in under two seconds wasn't filled in by a person.
- Confirm email before the account can post. It doesn't stop determined spammers, but it removes the laziest ones.
- Turn off registration on sites that don't need it. If nobody needs an account to use your site, the signup page is just an open door.
Many owners stop here and see the bulk of junk accounts disappear.
Layer 2: limit what a brand-new account can do
This is the layer that does the most work for the least friction.
- Hold first posts for approval until someone has a few approved replies.
- Block links, images and signatures for new accounts. Spam needs a link to pay off; without one, most of it isn't worth the effort.
- Rate-limit new accounts: a small number of posts per hour, no private messages on day one.
- Treat profile fields as posts. Bio, website and signature fields are a favourite hiding place for spam links.
Real newcomers rarely notice these limits. A genuine first question doesn't need three links and a signature.
Layer 3: watch edits and dormant accounts
This is where sleeper accounts get caught.
- Re-moderate edits that add links to old posts, especially from accounts that have been quiet for a while.
- Flag accounts that go from zero to many posts in a short burst after weeks of silence.
- Review old, popular threads now and then. They rank well in search, so they're the most valuable place to hide a link.
- Prune accounts that never confirmed their email or never posted after a reasonable period.
Layer 4: let members help, carefully
Your regulars see spam before you do.
- One-click "report" for any logged-in member, with a clear note on what happens next.
- Auto-hide a post after a few reports from trusted members until a moderator looks at it.
- Give long-standing members a light trusted role: they can edit tags, move threads or approve first posts.
- Write down the rules for AI-generated posts. Whether you ban them, allow them with a label, or allow them in one area, members need to know where the line is.
Layer 5: when you need the heavy tools
Some forums attract targeted abuse. Then you might need visible challenges at signup, invite-only registration for a while, or paid membership as a filter. These work, but they cost you newcomers. Use them as a temporary gate during a wave, then step back down.
Don't forget the software itself
Many "spam" problems are really security problems. An outdated forum plugin, theme or extension with a known flaw lets attackers skip all five layers and write straight into the database.
- Keep the forum software and its plugins updated, and subscribe to its security notices.
- Remove extensions you no longer use, rather than just deactivating them.
- Keep off-site backups you have actually restored once, so a bad week doesn't become a lost archive.
If you're choosing software, look at the moderation tools as closely as the features: approval queues, new-account limits, edit review and member reporting. Discourse, Flarum, phpBB, bbPress and the newer WordPress forum plugins all handle these differently. (Disclosure: we build Jetonomy, a forum and Q&A plugin for WordPress, so weigh our view with that in mind.)
The first-week checklist after a spam wave
- Turn on approval for first posts and block links for new accounts.
- Add a honeypot and a minimum submit time to signup.
- Bulk-remove accounts created during the wave that never posted anything real.
- Search for links added in recent edits to old threads.
- Check that the forum software and every extension is on its latest version.
- Tell members what changed and how to report anything you missed.
- After a couple of weeks, loosen one rule at a time and watch what comes back.
The goal isn't zero spam. It's keeping spam cheap enough to handle that your moderators don't burn out, and keeping the forum open enough that a real person with a real question still gets in on the first try.
Your turn
- If you run a small forum, which single change cut the most junk for you?
- Have you dealt with sleeper accounts that edit old posts? How did you spot them?
- Where do you draw the line on AI-written posts: ban, label or allow?
- What's the lightest gate you've used that still worked during a spam wave?
Top comments (0)