The most reliable way to stop WordPress comment spam is to layer controls instead of relying on one switch: set a deliberate approval policy in Settings → Discussion, hold comments with suspicious link counts, send recurring patterns to moderation, reserve the blocklist for high-confidence matches, close comments on posts that do not need them, and add an automated filter such as Akismet. This reduces what gets published and shrinks the review queue, but it cannot prevent bots from sending requests to your site.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Why spam keeps appearing after you turn comments off
WordPress has several separate comment controls, and they do not all affect the same content. The default setting in Settings → Discussion generally controls whether comments are enabled on new posts and pages. Existing content can retain its earlier comment status, so switching off the default does not necessarily close discussion on older articles.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Comment spam also includes more than visible comments. Pingbacks and trackbacks can create unwanted entries, and automated programs can continue submitting requests even when every submission is rejected or sent to moderation. Learn WordPress describes the limitation plainly: spam plugins can stop and delete a lot of spam, but they cannot stop spammers from accessing your website. Your goal is therefore publication control and manageable moderation, not a promise that no bot will ever connect.
For a video-game site, this distinction matters. A year-old review, walkthrough, or patch-note post may still accept comments even after you changed the site-wide default. A bot can target that URL repeatedly, while a legitimate reader may be discussing a strategy or a balance change in the same thread. The settings below let you close inactive discussions without sacrificing useful conversation everywhere.
Set the built-in Discussion controls first
Open Settings → Discussion in the WordPress administrator area. Work through the controls in order, then save the page before moving to the next layer.
Audit the defaults for new content
Check whether comments, pingbacks, and trackbacks are enabled by default. Decide separately whether your site actually needs each one. A gaming news site might want reader comments on analysis but have little use for pingbacks or trackbacks. Disabling a default is a forward-looking change; inspect older posts separately because their saved status may not change.
Choose who can publish without review
Under the comment-approval options, choose the level of control that matches your editorial workload:
| Policy | How it behaves | Best fit | Trade-off |
|---|---|---|---|
| An administrator must always approve the comment | Every comment waits in the moderation queue until an administrator approves it. | Sites where no reader contribution should appear before a human checks it, such as a small publication with a high abuse risk. | Maximum publication control, but every genuine comment creates work and replies are delayed. |
| Comment author must have a previously approved comment | A commenter with an already approved contribution can pass the repeat-author check; a new identity enters the queue. | Communities with regular readers where you want a lighter queue without opening the door to first-time spam. | Lower friction for returning contributors, but a spammer who earns one approval can receive less scrutiny later. |
Requiring approval, registration, or other identity checks can reduce participation as well as spam. If discussion is central to your guides or reviews, start with the repeat-author policy and tighten it when the queue shows a problem. If comments are occasional and highly visible, always-approve moderation is easier to audit.
Hold comments that contain too many links
Enable the rule that holds a comment when it contains more than a chosen number of links. WordPress documentation notes that many spam comments contain multiple hyperlinks, making this a useful signal. It is not proof of abuse: a reader posting a detailed hardware fix, mod list, or source-heavy technical explanation may legitimately include several links.
Choose a threshold that reflects your normal conversations rather than selecting the smallest possible number. Review held comments for a while, then adjust the threshold if legitimate guide feedback is routinely delayed or if link-heavy spam still reaches the queue. The action here is hold for review, not automatic deletion, so you can tune it safely.
Recommended Free Tools
Build the Comment Moderation list
Add recurring indicators to Comment Moderation. Matching comments are held for review instead of being published automatically. Useful entries can include:
- Repeated spam phrases seen in your own queue.
- Domains that repeatedly appear in promotional comments.
- Email addresses or name patterns associated with abuse.
- IP addresses that produce a persistent stream of unwanted submissions.
- Other distinctive terms that have no legitimate role in your community.
Use specific strings whenever possible. A broad word can occur in a perfectly valid discussion about a game, a character, or a genre. Keep a short record of false positives and remove or narrow entries that catch real readers. Moderation is a living list: recurring patterns should be added, while rules that no longer help should be edited.
Use the Comment Blocklist only for high-confidence matches
The blocklist is more aggressive than moderation. Content matching an entry is marked as spam and can be deleted without warning. WordPress documentation describes the older field name, “Disallowed Comment Keys,” as working like the moderation box except that matching comments are deleted immediately and without notification.
Reserve this field for patterns you are confident should never be retained. A narrow, unmistakable domain or phrase may be appropriate; a common word, a broad country name, or a generic sales term is not. If a genuine comment disappears, the blocklist is the first place to inspect. Move uncertain entries to Comment Moderation so a person can decide instead of losing the text.
Close comments on posts that do not need discussion
Some content has no useful reason to remain open. Announcements, expired event pages, old news, and static policy pages often attract bots long after readers have stopped adding value. Closing those threads removes a source of queue noise while leaving comments enabled on active guides or reviews.
Close one post
- Open Posts → All Posts and edit the post you want to protect.
- In the editor’s discussion settings, turn off Allow comments. If pingbacks or trackbacks are shown separately, turn those off as well when they are not needed.
- Update the post and, if comments still appear open, verify the saved discussion status by reopening the editor.
Close many posts at once
- Go to Posts → All Posts and select the posts that no longer need discussion.
- Choose Bulk actions → Edit, then apply the comment status that disables comments.
- Save the bulk edit and spot-check several posts from different dates to confirm that the change reached the intended group.
Bulk editing is especially useful after changing the default setting, because it updates existing content instead of waiting for each post to be edited individually. Use a narrow selection first; an overly broad bulk action can close a lively discussion by mistake.
Add automated filtering with Akismet
Built-in rules evaluate the content and metadata you specify. An automated service adds another layer by analyzing each submission against a broader spam-detection system. The Akismet plugin listing says it checks comments and contact-form submissions against a global database of spam, filters items that look malicious, and retains a status history for moderators to review.
Install and configure it
- In the dashboard, open Plugins → Add New Plugin.
- Search for Akismet, install the official plugin entry, and activate it.
- Follow the plugin’s setup screen to connect the service and choose its handling options.
- Return to the comments area after activation and confirm that filtered items have a visible status history.
- Keep the built-in approval, moderation, and blocklist rules in place; the plugin is an additional layer, not a replacement for your editorial policy.
Continue reviewing the spam queue after activation. Automated classification can make mistakes, and a service layer does not guarantee that every abusive submission will be identified. Approve legitimate comments, mark clear spam, and trash comments that are abusive or irrelevant. Feed repeated, unambiguous patterns back into Comment Moderation rather than immediately adding broad terms to the blocklist.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use a repeatable moderation workflow
A good configuration fails if no one processes its queues. Give comment review a consistent owner and a clear decision path:
- Inspect pending comments. Read the complete text, author name, email address, IP information, and links before deciding.
- Approve useful contributions. Publish genuine questions, corrections, and game discussion that meet your site’s standards.
- Reply where a response helps. A concise answer can resolve a gameplay question and signal that the community is actively moderated.
- Mark obvious spam. Use the spam action so future filtering has a useful signal.
- Trash abuse or irrelevant material. Do not leave harassment or meaningless promotions in the public thread.
- Review patterns periodically. If the same domain, phrase, name, or address recurs, add a precise entry to Comment Moderation and observe the result before escalating it to the blocklist.
Keep the queue review separate from list maintenance. First decide what should happen to the individual comment; then update a rule only when the pattern is clear. This prevents a rushed reaction to one unusual message from creating a site-wide false-positive problem.
How the layers compare
| Layer | Publication control | False-positive risk | Maintenance | User friction |
|---|---|---|---|---|
| Always approve | Highest: nothing appears before human approval. | Low publication risk, but legitimate comments wait. | Ongoing queue review. | High delay for every commenter. |
| Previously approved author | New identities are reviewed; repeat authors can pass. | Moderate; a previously approved identity may later abuse access. | Review new authors and monitor repeat contributors. | Lower for returning readers. |
| Link threshold | Holds link-heavy comments for inspection. | Legitimate research-heavy comments can be held. | Adjust the number as your community changes. | Usually invisible unless a comment is delayed. |
| Comment Moderation list | Matching comments wait for review. | Depends on how narrowly terms are written. | Requires tuning as patterns change. | Low when entries are precise. |
| Comment Blocklist | Matching content is treated as spam and may be deleted immediately. | Highest if entries are broad. | Audit entries and recover from mistaken matches where possible. | Legitimate writers may receive no visible explanation. |
| Akismet automated filter | Filters suspected spam while retaining a reviewable status history. | Classification can still require human checking. | Plugin/service upkeep plus queue review. | Usually low, unless your approval policy adds extra checks. |
| Closing comments per post | Removes the comment surface from selected content. | No comment false positive on a closed post; useful discussion is also unavailable. | Maintain statuses when content strategy changes. | Readers cannot comment on those posts. |
These controls cover different signals. Approval rules govern whether a person must intervene, lists inspect words and metadata, link thresholds catch a common spam pattern, and an automated filter analyzes submissions beyond the rules you write. Combining them gives better coverage than trying to make one list do everything.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot the problems you actually see
Spam appears on posts even though the default is disabled
Open one affected post and inspect its individual discussion setting. The post may have been published before you changed the default and retained comments as enabled. Close that post directly, then use a carefully selected bulk edit for the rest of the old content.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Pingbacks or trackbacks keep creating unwanted entries
Recheck both the site-wide defaults and the individual post status. Comment settings, pingbacks, and trackbacks are related but distinct controls. Disable the mechanisms your publication does not use, then close them on older posts where they remain active.
Legitimate readers are stuck in moderation
Inspect the specific trigger rather than disabling every safeguard. A comment may exceed the link threshold, contain a phrase on the moderation list, or come from a new author under the previously approved-author policy. Narrow the matching term, raise the link threshold to a level that fits your discussions, or approve the reader’s comment so future contributions are handled according to your chosen policy.
Valid comments disappear without notification
Check Comment Blocklist entries first. Unlike moderation, a blocklist match can be deleted immediately. Remove broad terms or move uncertain patterns to Comment Moderation. Also review the automated filter’s status history so you can distinguish a rule-based deletion from a service classification.
Spam is still published after installing a filter
Confirm that the plugin is active and that submissions are receiving a filter status. Then keep an approval policy enabled while you evaluate results. Automated filtering reduces the burden but does not promise perfect detection; review both the spam and pending queues and add precise recurring patterns to moderation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Bots keep sending requests after every comment surface is closed
This is expected. Closing comments prevents publication on those posts; it does not make the site’s endpoints unreachable. Continue monitoring server and WordPress activity through your normal operational tools, but measure success by fewer published spam comments and a smaller moderation workload rather than by the absence of connection attempts.
A practical policy for a gaming publication
Start by keeping comments open on active reviews, build guides, and discussion-led features. Require approval for every comment if your team can review promptly or if abuse is currently severe. Otherwise, allow a previously approved author to pass while sending first-time identities to moderation.
Close comments on expired event announcements, outdated news, and pages where a new reply cannot help readers. Set a link threshold that accommodates legitimate build references and source links, then add only distinctive spam phrases, domains, names, email addresses, or IP addresses to Comment Moderation. Promote a pattern to the blocklist only after you are confident it has no legitimate use in conversations about games.
Finally, add Akismet for automated analysis and retain human review. This combination balances publication control, false-positive risk, maintenance effort, coverage, and reader friction—the five trade-offs that determine whether a spam policy remains usable after the initial setup.
What success looks like
A successful setup does not claim that spammers have vanished. It means readers’ comments are not buried under promotions, moderators can identify why a message was held, old posts do not expose unnecessary comment forms, and the rules can be tightened without silently deleting real discussion. Check those outcomes after each change and adjust one layer at a time.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
