Editorial illustration; the comment labels are representative examples, not a screenshot of a particular dashboard.
Comment moderation is often treated as a spam problem. It is really a publishing workflow. A genuine question needs a different decision from a link-filled advertisement, and both need a clear place in the queue.
This guide is for a small WordPress site that wants comments to remain useful without asking one person to inspect every setting every day. It focuses on the core Comments screen and Discussion settings. A plugin can add automation later, but it should not replace a decision process you cannot explain.
Summary
- Decide what “publishable” means before choosing moderation rules.
- Use pending, approved, spam and trash as different outcomes, not interchangeable bins.
- Start with a small test set and review false positives before tightening rules.
Decide what comments are for
First decide whether comments are part of the site’s purpose. A tutorial may benefit from questions and corrections. An announcement archive may close comments after a period. A brochure site may not need comments at all.
There is no prize for leaving a comment form open everywhere. If nobody can review the queue, an open form becomes a poor visitor experience. WordPress lets you disable comments globally through Discussion settings or for individual posts and pages.
Write two sentences for your policy: what readers can contribute and what will be removed. “Questions, corrections and relevant examples are welcome; unrelated promotion, abuse and copied advertising are not” is more useful than “comments are monitored.”
1. Review Settings > Discussion
Open Settings > Discussion and inspect the defaults before changing them. Decide whether authors must fill in a name and email, whether users must be registered, whether comments on older articles should close, and whether threaded replies fit the site.
Do not enable every restriction automatically. Requiring registration may reduce spam but also removes low-friction questions from first-time readers. Closing old comments may help a high-traffic archive, but it can also prevent a useful correction.
Enable email notification for comments held for moderation only when someone will act on it. An alert that nobody reads is not a workflow.
2. Choose a conservative default
For a small site, holding comments with multiple links or unfamiliar patterns is often a reasonable starting point. WordPress’s moderation screen describes rules for the number of links and moderation keys, while disallowed keys can delete matching comments immediately.
That last setting deserves care. A false positive in the moderation queue can be restored; a comment deleted by a disallowed key may disappear without notification. Begin by holding suspicious comments rather than blocking broad words such as “free”, “help” or a product name.
Use How to Evaluate a WordPress Plugin Before Installing It before adding a spam plugin. A plugin has its own update and compatibility cost, and the site should not install one merely because the queue looks inconvenient.
3. Read the whole comment before deciding
Open the comment and read its text, author name, website, time and the post it references. A comment containing one external link may be a useful citation; a short generic compliment followed by a link may be promotion.
Look for relevance rather than keyword matches. “Your cache example helped; here is the official reference” is materially different from “Great post, visit my site for offers.” If a comment is unclear but not harmful, reply with a question or leave it pending while you verify the context.
4. Use the right outcome
Use Approve when the comment is relevant and safe to display. Use Reply when answering it improves the page for future readers. Use Edit sparingly and preserve the commenter’s meaning; do not rewrite criticism into praise.
Use Spam for unwanted promotional or deceptive content, and Trash for content you do not want retained in the normal workflow. If a genuine comment was marked spam, use Not Spam so it returns to review.
These labels create useful history. If every unwanted comment is deleted immediately, you lose the pattern that could help you tune moderation later.
5. Test rules against real examples
Before adding a new moderation key, inspect recent comments. WordPress documentation recommends checking past comments against a new rule so you can see what it would catch.
Create a small test set: a genuine question, a genuine comment with one link, a short promotional message, a comment with several links, and a comment containing a word that may appear in normal writing. The aim is not to achieve perfect automatic classification. It is to learn which mistakes the rule creates.
If the rule catches too much, raise the threshold or move the term from disallowed to moderation. If it catches too little, add a narrow pattern that reflects your site’s actual queue.
6. Review the queue on a schedule
Set a review rhythm that matches the site. A small blog may check once daily; a busy community may need several reviews. During each pass, process the oldest pending items first, then scan newly approved comments for follow-up questions.
Do not approve everything in a batch merely to reach zero. A queue that is empty because real questions were discarded is worse than a queue with a few unresolved items.
Record recurring patterns in a short note: repeated domains, copied phrases, or false positives from a keyword. This gives you evidence when deciding whether a new rule is justified.
7. Separate moderation from moderation rights
Give comment-management access to people who need it, not to everyone who writes posts. WordPress roles and capabilities determine which users can edit or manage comments. Review those accounts as part of normal maintenance; WordPress Roles and Capabilities: Give Each User Only the Access They Need covers the least-access decision in more detail.
If two people moderate, agree on a handoff rule. For example, one person can approve relevant comments while a second person handles reports involving harassment or personal data. The important part is that nobody assumes someone else has reviewed the queue.
8. Handle older posts deliberately
Old posts attract both useful corrections and automated spam. Closing comments after a defined period can reduce the queue, but apply the choice to the type of content rather than using an arbitrary number for every page.
For a technical tutorial, keeping comments open may be valuable because readers can report changes. For a time-sensitive announcement, closing comments after the event may be sensible. If you close comments, add another contact path for corrections.
Common mistakes
- Blocking a broad word because one spam comment contained it.
- Treating “no record found” in a filter as proof that a commenter is trustworthy.
- Giving every author administrator-level comment access.
- Editing criticism so heavily that it no longer represents the commenter.
- Leaving a moderation queue unattended after enabling email alerts.
My Take
The best moderation system is intentionally modest. It catches obvious junk, gives a human a chance to review uncertainty, and leaves room for genuine disagreement. A small set of rules that the owner understands is safer than a complicated stack of filters no one remembers how to change.
Conclusion
Start with a clear comment policy, review Discussion settings, hold uncertain comments, and use the Comments screen consistently. Test each rule against real examples and keep moderation access narrow. The result should be a queue that helps you publish useful conversation, not a contest to delete the most messages.