WordPress Comment Notifications: Configuring Them Well

WordPress sends emails when comments are posted. The default configuration is often inappropriate: too many notifications for active sites, too few for low-traffic sites. The right configuration produces awareness without overwhelming the recipient.

The choices to make are simple but worth making deliberately rather than accepting defaults.

The default behavior

WordPress emails the post author when comments are posted on their posts. It emails the admin address when comments are held in moderation.

For low-traffic sites with disciplined moderation, the defaults work. For higher-traffic sites or sites with multiple authors, the defaults produce email floods.

The "moderation required" notification

Set up moderation rules so most comments require moderation. The pattern that works:

Comments from first-time commenters require approval.

Comments with 2+ links require approval.

Specific words trigger moderation (the moderation queue).

With this configuration, only legitimate comments from known good commenters auto-publish. Everything else queues for review.

The notification when moderation is needed alerts the team that there's work to do. The notification volume depends on comment volume and how many comments require moderation.

The "comment posted" notification

For sites where you want to see every comment as it happens, enable the "anyone posts a comment" notification.

For sites where post-publication review is enough, disable the per-comment notification.

The choice depends on engagement strategy. Engaged authors who reply to comments quickly want immediate notification. Authors who batch-review want less frequent alerts.

The author vs site admin distinction

Multi-author sites need to think about who gets which notifications:

Post authors typically want notifications about comments on their own posts. The notification is targeted to their interest.

Site admins typically want notifications about moderation queue, security events, system issues. Not per-comment notifications on every author's posts.

The configuration in WordPress core supports the basic distinction. Plugins like PublishPress add more granular options.

The notification frequency

For high-volume sites, individual comment notifications produce too much email. The alternatives:

Batch notifications. A daily digest summarizes comment activity.

Threshold notifications. Notify only when comments accumulate beyond a threshold.

Channel routing. Comments go to Slack or another team channel rather than personal email.

WordPress core doesn't support these natively. Plugins can add them.

The Slack or team channel integration

For team-managed sites, routing comments to a Slack channel works well:

The team sees comments in shared visibility.

Individual inboxes aren't flooded.

The team can react and respond from where they already work.

Plugins or webhook integrations route WordPress comments to Slack.

The honest framing

Comment notification configuration is a small operational detail. Done well, the team stays aware without being overwhelmed. Done poorly, important comments get lost in noise or response is delayed.

The 15 minutes to configure well saves substantial frustration over time. For sites that haven't reviewed comment notifications, this is worth doing.