Spam is unwanted digital communication, especially irrelevant or repetitive messages sent through blog comments or forms. On a website, it can clutter discussions, introduce inappropriate material, waste moderation time, and make visitors less willing to read. Publishing junk messages can also hurt how search tools assess a site. section 9.6
Do not assume every incoming message should be published. Comments may also include vulgarity, inaccurate information, off-topic remarks, copyright violations, or low-quality writing. A site can choose not to allow audience posts at all when reviewing them is not worthwhile. section 9.6
Use a layered approach to reduce spam:
- Review incoming comments before they become public, particularly as a site attracts more visitors. section 9.6
- Set Comment Moderation rules in WordPress to route messages containing listed words or URLs into a queue. section 9.6.1
- Use Disallowed Comment Keys to automatically trash messages matching stronger blocking criteria, then save the settings. section 9.6.1
- Require commenters to provide a name and email address to cut down on spam and other inappropriate messages. section 5.6
- Protect forms as well as comments, since fake or unwanted submissions can arrive through contact forms. section 9.6.1
Choosing an automated filter
A blog with an active comment area can use Akismet to detect likely spam with AI and compare potential spam against a global database of known spam. For forms, WPForms can add anti-spam protection such as captcha, requiring a visitor to solve a puzzle or math problem before submitting. section 5.1 section 9.6.1
Spam controls should support, not replace, judgment. Automated filters reduce the number of messages requiring attention, while moderation rules let a site owner decide what is queued, published, or discarded. Start with simple rules, then add a plugin when manual review becomes too time-consuming. section 9.6 section 9.6.1
