How to Moderate WordPress Comments on a Gaming Blog

The first week our guild blog opened comments, we got 412 of them. Thirty were from real players arguing about a raid tier list. The other 382 were spam links, copy pasted praise and one person who posted the same insult under every article. If you plan to moderate WordPress comments on a gaming blog, expect that ratio at the start and build the system before the traffic shows up, not after.

I have run comment sections for three fan communities on WordPress, and the setup that works is mostly built from settings already in the dashboard, plus one or two plugins. Here is what I configure on day one and what I stopped doing because it backfired.

Start With the Discussion Settings Most Admins Skip

Go to Settings, then Discussion. This screen controls more than most people realise, and the defaults are tuned for a quiet personal blog, not a community that gets linked from Discord servers and Reddit threads.

• Comment author must have a previously approved comment. Turn this on. First time commenters wait in the queue once, then post freely. It filters most drive by spam without annoying regulars.
• Hold a comment in the queue if it contains 2 or more links. Drop the default to 1. Real players rarely post links, and when they do, a short wait costs them nothing.
• Automatically close comments on articles older than X days. For patch notes and event coverage, 60 days is plenty. Old posts attract spam far more than real discussion.
• Enable threaded comments. Set depth to 3 or 4. Deeper threads become unreadable on phones, where most gaming readers browse.

Build a Word List That Fits Your Game

The Comment Moderation and Disallowed Comment Keys boxes on the same screen accept one word or phrase per line. Generic lists you download online are full of terms that make no sense for your audience and miss the ones that do.

For a gaming community, the useful entries are usually:

1. Names of gold selling and account boosting services that target your game.
2. Common spam domains you see repeatedly in your queue.
3. Slurs and harassment terms your community rules already ban.
4. Phrases like "cheap coins" or "level up fast" that appear only in sales pitches.

Put uncertain terms in the moderation box so they wait for review. Put only obvious spam in the disallowed box, because those comments go straight to the trash without anyone seeing them. I review the trash once a week for the first month to catch false positives.

A mistake to avoid

Do not add short words like "op" or "nerf" to any list. WordPress matches inside other words, so a filter for "rat" also catches "pirate" and "strategy", which on a game blog means half your build guides end up in moderation.

Choosing an Anti Spam Plugin

Settings alone stop maybe 70 percent of spam in my experience. The rest needs a plugin. The options fall into three groups.

For most fan sites, I pair a honeypot plugin with the discussion settings above and only add cloud filtering if spam still gets through. Run one plugin per type. Two honeypot plugins on the same form can conflict and block real users silently.

Why Requiring Accounts Usually Hurts Small Communities

A common suggestion is to force everyone to register before commenting. I disagree for most gaming blogs under a few thousand monthly readers.

Registration cuts spam, but it also cuts genuine comments sharply. A player who wants to correct a stat in your guide will not create an account to do it. They will leave and post the correction in a Discord channel you never see. On one site I ran, comments dropped by roughly two thirds the month we required login, and the spam reduction was smaller than what the previously approved setting already gave us.

Registration makes sense when you run a members area, a tournament sign up or a wiki like structure where people need persistent identities. If you go that route, set clear roles first, as covered in this guide to WordPress user roles for volunteer teams.

Sharing Moderation With Volunteers

Once comments grow past a few dozen a day, one admin cannot keep up. WordPress lets an Editor approve, edit and delete comments without touching plugins or themes, which is exactly the access a volunteer moderator needs.

• Write a short public comment policy, ten lines at most, and link it under the comment form.
• Agree on three actions: approve, edit out a link, or trash. Avoid editing someone's wording beyond that.
• Split the queue by time zone if your volunteers are spread out, so nothing waits more than a few hours.
• Keep a private note of repeat offenders by email and IP rather than relying on memory.

Keeping Comments From Slowing the Site

A popular patch notes post can collect 800 comments. Loading all of them on one page makes the article heavy on mobile. In Discussion settings, enable "Break comments into pages" with 50 top level comments per page, and show newest first for news posts where recent replies matter most.

If you use a page cache, check that approved comments actually appear for visitors. Some setups serve an old cached copy for hours, which makes readers think their comment vanished. The fix is usually a cache rule that clears the page when a comment is approved, explained in why caching plugins hide your own updates.

FAQ

Should I turn off comments entirely?

Only if nobody on your team can check the queue at least every other day. An unmoderated comment section full of spam damages trust more than a closed one, but a moderated one gives you corrections and ideas you would not get anywhere else.

Do comments help search rankings?

Indirectly at best. Useful comments can add fresh, relevant text and keep readers on the page longer, but thin or spammy comments do the opposite. Quality matters more than count.

How do I handle a comment that is rude but on topic?

Edit out the insult if your policy allows it and leave the point, or reply publicly asking them to rephrase. Deleting on topic disagreement quietly tends to make communities feel censored.

Your First Hour of Setup

Open Discussion settings today, require one previously approved comment, lower the link limit to 1 and close comments on posts older than 60 days. Add a single honeypot plugin, write a ten line policy, and review the queue daily for two weeks. That hour of work prevents most of the cleanup that would otherwise eat your weekends. More setup guides live in the WordPress section.