Comments & Site Interaction

WordPress Fundamentals

Chapter 9 · Comments & Site Interaction

WordPress Fundamentals 8's own Subscriber role — an account with no content-creation ability at all — finally has an obvious purpose here: letting a reader comment under a real account rather than anonymously. This chapter covers how WordPress's own built-in comment system works, how to keep it usable despite spam, and the real trade-offs behind common moderation choices.

How Comments Work

A comment form appears beneath Posts by default (Pages can allow comments too, but typically don't by default, matching WordPress Fundamentals 3's own pattern of Pages behaving differently from Posts). Whether comments are open at all — site-wide or per individual post — is controlled from Settings → Discussion.

Discussion Settings — The Real Trade-Offs

SettingThe real trade-off
Require name/emailA small amount of friction that filters out some low-effort spam and drive-by trolling, at the cost of a slightly higher bar for genuine casual commenters
Require an account to commentMeaningfully reduces spam and improves comment quality, but genuinely reduces total comment volume — the exact use case WordPress Fundamentals 8's own Subscriber role exists for
Hold a comment for moderation if it contains N+ linksCatches the most common spam pattern (link-stuffed comments) without blocking ordinary comments outright
Automatically close comments after N daysReduces spam on old posts (which accumulate the most spam attempts over time) at the cost of blocking genuine late discussion
There's no universally correct setting
A high-engagement community blog and a small business site with occasional posts have genuinely different needs here — more open settings favor engagement and volume; more restrictive settings favor quality and lower moderation effort. This is a real judgment call, not a checklist with one right answer.

Comment Statuses

Comments move through their own set of statuses, echoing the Post statuses from WordPress Fundamentals 3:

  • Pending — awaiting moderator approval, not yet publicly visible
  • Approved — live and publicly visible
  • Spam — flagged as spam, hidden from visitors, kept temporarily in case of a false positive
  • Trash — deleted, permanently removed after a set period

Spam — A Genuinely Large Practical Problem

Any public comment form on the internet attracts automated spam almost immediately — WordPress's own popularity, per WordPress Fundamentals 1's own market-share material, makes it a particularly common target for spam tooling built specifically around it.

Akismet — WordPress's own first-party answer
Akismet, built by Automattic (the same company behind WordPress.com, per WordPress Fundamentals 1's own distinction), checks every submitted comment against a constantly-updated, global database of known spam patterns before it's ever shown publicly. It comes bundled with WordPress core and is, for most sites, the single highest-value anti-spam step available — activating and configuring it is usually the very first real moderation task on a new site.

Engagement — Beyond Just Moderation

A comment section only builds genuine community if someone is actually responding — replying to real comments, not just filtering out spam, is what turns a comment form from a liability into an actual asset. Some sites deliberately choose a third-party comment system (Disqus is a common example) instead of, or alongside, WordPress's own native comments, trading some of WordPress's own direct control for that platform's own spam-filtering and social features — a real option worth knowing exists, even though this course focuses on the native, built-in system.

Hands-On Exercises

Exercise 1

A site owner requires visitors to have a registered account before commenting. Explain, using this chapter's own material, what this actually trades off, and which earlier chapter's own material this decision directly connects to.

📄 View solution
Exercise 2

Explain why comments flagged as "Spam" aren't deleted immediately, using this chapter's own reasoning.

📄 View solution
Exercise 3

Explain why this chapter says there's "no universally correct" discussion setting, using the specific example of a high-engagement community blog versus a small business site.

📄 View solution

Chapter 9 Quick Reference

  • Comments are controlled site-wide via Settings → Discussion; Pages typically disable them by default, matching Posts-vs-Pages behavior from WordPress Fundamentals 3
  • Every discussion setting is a genuine trade-off between spam reduction and comment volume/engagement — no universally correct answer
  • Comment statuses: Pending, Approved, Spam, Trash — echoing Post statuses
  • Akismet — WordPress's own bundled, first-party spam filter, usually the first real moderation step on a new site
  • Requiring an account to comment is the concrete real-world use case for WordPress Fundamentals 8's own Subscriber role
  • Third-party comment systems (e.g. Disqus) exist as an alternative to native WordPress comments, trading control for built-in spam handling
  • Next chapter: Maintenance, Updates & Backups