WordPress Comments Are Stale. Here’s What Needs to Change.
WordPress has long been a go-to platform partly because it ships with a built-in commenting system. That’s a feature many site owners rely on, and it’s often a reason they stick with the platform. But the reality is that the system has aged poorly. It works, but it feels dated and limited compared to modern alternatives. There’s no direct account ownership of comments, the UI for leaving a reply feels like a chore, and there’s little in the way of social integration or modern convenience. It needs a significant refresh.
Comments Should Belong to Users
One of the most puzzling aspects of WordPress comments is that they aren’t truly owned by the people who leave them. A logged-in user can post a comment, but there’s no real link tying that comment to their account. Users can’t go back and fix typos or clarify a statement. It seems like an obvious feature: if someone has an account, they should be able to manage their own comments. Ideally, there would be an editing window even for non-logged-in users, offering a grace period to correct mistakes before a comment is final.
Other platforms in the WordPress ecosystem handle this better. In bbPress, users own their topics and replies and can edit them (often with a time limit). That same model doesn’t extend to standard post comment threads, which is a missed opportunity.
Social Authentication Would Lower the Friction
Typing in a name, email address, and website URL just to leave a comment feels like an unnecessary barrier in 2024. It likely deters a large number of potential commenters who are used to one-click responses on social media. Services like Disqus have shown that removing this friction increases engagement. WordPress needs a way for users to authenticate via social profiles, handling the identity legwork automatically. This could also serve as a path to comment editing later on.
Jetpack does offer social authentication for comments, but it comes with a downside: the comment UI is enclosed in an <iframe>, stripping the site owner of any design control. The default expanded textarea, which starts as a narrow box and expands on click, is also locked down. Even if the underlying functionality is powered by Jetpack, site owners should have the ability to control and style the interface.
A Whitelist for HTML Tags Would Improve Sanity
Commenters frequently type raw HTML like <div> and expect it to display as text, only to have it stripped out by the system. This happens constantly, even with experienced web developers. It's a UI/UX failure that leads to frustration and mangled formatting.
Jetpack’s Markdown support for comments is a major improvement because it makes it trivial to use backticks for code. However, not everyone knows Markdown, and even those who do can be uncertain about when and how it escapes HTML. A whitelist approach could be a practical solution: allow safe, formatting-oriented tags like <em> to render as markup, while non-whitelisted tags like <section> are automatically escaped and shown as plain text. This isn't a perfect solution, but it's a logical step forward for a common problem.
Preview Is a Must-Have Feature
Commenters should be able to see how their comment will look before it goes live. A preview allows them to catch formatting errors and gives them one last moment to reconsider their words before clicking submit. It’s a simple feature that improves both quality and thoughtfulness of discussion.
Email Notifications for Replies Are Overdue
Jetpack currently provides email subscriptions for new blog posts and for new comments on a specific post. Notifications for post updates come from WordPress.com and offer no control over design or what triggers them. While the comments subscription feature is useful, serious sites might want a more custom, controlled workflow.
The real gap is reply-specific notifications. When someone engages with your comment, you want to know about it. Commenters are invested in the conversation and want to follow up on replies to their own contributions. Sending out a flood of emails about every new comment on a post is less valuable than directly notifying someone when their specific comment gets a response. Given that WordPress already generates a lot of email, adding this feature doesn't seem outside its current scope.
Replies Need Context Everywhere
On the front end, nested comments show the parent clearly. But that context is lost in other places you encounter comments:
- Email notifications for replies don’t include the parent comment text.
- The comments admin screen, or the WordPress app, lacks the visual nesting of the site itself.
The admin panel does show an “In Reply To [Name]” link, but it merely links to the parent comment on the front end. It doesn’t expand inline or offer a quick preview of the original comment, which would be far more useful.
Comment Emails Need a Design Overhaul
Default WordPress-generated emails are functional but ugly. They rely on raw, long URLs instead of basic HTML links, which detracts from their readability and professionalism. There is a plugin that fixes this issue on a site like CSS-Tricks, but that shouldn’t be necessary; clean HTML links should come standard. Even basic HTML email formatting would allow for proper links and typography, making notifications much more pleasant and easier to skim.
Emails Should Perform Actions Directly
Moderation emails contain links to “Delete” and “Spam” a comment, but they require a round trip. The link sends the moderator to a page where they must click another button to execute the action. If a user is authenticated, the email link should perform the action immediately, eliminating an unnecessary extra step.
Bring Commenting Into the Ajax Era
Submitting a comment should not cause a full page refresh. That experience feels as outdated as lacking quick social authentication. Ajax submission, where the comment is posted and the DOM updates seamlessly, is a fundamental modern expectation.
WordPress themes already enqueue a script to handle the “Reply” link, positioning the form next to the comment being replied to. With that precedent, additional JavaScript could handle comment submission, refreshing the comment list, showing approval messages, or displaying errors without a page load. There are third-party plugins and tutorials that achieve this hand-rolled Ajax implementation, but baking it into the core would save a lot of maintenance headaches and make it universally available.
Richer Comment Actions and Voting
Comment moderation is currently an all-or-nothing proposition. One solution is to let users vote on comments. A like or upvote system, similar to what Jetpack offers for posts, could be applied here as well. If comment quality is measurable, the default sort order could reflect votes instead of chronological time. This would arguably surface better engagement, since readers often care more about high-quality comments than just the newest ones.
This leads to a broader set of potential actions beyond simple like/dislike:
- Upvote or downvote
- Flag as spam
- Flag as harmful or a Code of Conduct violation
- Save or pin comments
These data points could influence moderation. If comments are user-owned and carry a reputation, maybe moderation becomes more targeted. Instead of reviewing every comment, admins could choose to pre-screen only comments from unknown users or those with poor quality scores, trusting established contributors more.
Better Sorting and Front-End Control
Even without a full voting system, users should be able to sort comments by more than just date. Having an option for “Top” or “Best” comments requires a voting mechanism, but the ability to offer alternative sort orders is a clear improvement over a strict chronological list. Additionally, front-end users should have access to the same robust tools as the back end. It should be possible for authorized users to edit or delete their comment, flag it as spam, or adjust metadata from the site itself, providing a more fluid and empowered experience.A Dedicated Comment Moderator Role
Large comment sections, especially ones that get great after these improvements, require oversight. It’s often not feasible to grant full administrator or editor access to trusted community members just for that purpose. There should be a specific user role limited to comment moderation. This would let site owners delegate day-to-day comment management without giving away broader site permissions.
