The WordPress block editor ships with a collaboration feature that most content teams overlook: block-level notes. You can attach threaded comments to any block, reply to those comments, and resolve them when discussions conclude. Email notifications alert you when colleagues respond. None of this requires a plugin.
This matters for editorial workflows where content moves between writers, editors and approvers. Instead of tracking feedback through scattered emails or external tools, the discussion lives alongside the content it references.
How the feature works
Select a block in the editor, open the Options menu (the three-dot icon), and choose "Add a comment." A dialog appears on the right side where you type your note and save. Other users see a person icon on blocks that have comments, alerting them to pending discussions without interrupting reading flow.
When someone replies, WordPress sends an email notification using the existing comment system. Recipients click through to the specific block, see the full thread, and can reply or resolve the conversation. Resolving a comment marks it complete using a checkmark in the dialog's upper left corner. The comment persists unless an editor manually deletes it, leaving a visible record of decisions made.
Our analysis
Most editorial teams handle feedback through one of three methods: in-person meetings, email chains, or external tools like Google Docs or project management software. Each has drawbacks. Meetings create scheduling overhead and lose context when attendees forget details. Email chains scatter discussion across inboxes and bury decisions in threads. External tools require switching context away from the actual content.
Block-level notes address these problems by anchoring discussion directly to the relevant section. When a writer receives feedback about a specific paragraph, they see that paragraph and the feedback together. Editors reviewing changes can read the comment history to understand why a particular phrasing was chosen. Approvers can resolve comments as they sign off, leaving a trail of what was discussed and decided.
The email notification integration makes this practical for async teams. Content moves through stages without requiring everyone to monitor the editor constantly. When feedback arrives, it arrives in the inbox with a direct link to the relevant block.
For teams managing client sites, the feature offers a lightweight way to capture requirements without installing project management plugins. A client can comment on a block asking for clarification; the developer responds; both see the exchange without leaving WordPress.
The trade-off**: The feature is asynchronous only. Real-time collaboration requires different tools. Teams used to live editing in Google Docs may find the back-and-forth slower. But for workflows that already operate asynchronously—which describes most agency and in-house content teams—this is a strength, not a limitation.
Who should care
| Team type | Primary benefit |
|---|---|
| Content agencies managing client sites | Capture client feedback without switching tools |
| In-house teams with async approvers | Centralize review decisions in one place |
| Solo developers building client themes | Leave implementation notes for future reference |
| Writers editing their own drafts | Self-reminders for sections needing revision |
What to watch next
Evaluate whether your content workflow involves scattered feedback that would benefit from being centralized. If editors, writers and approvers currently exchange comments via email or external tools, test whether block notes reduce context-switching and improve traceability.
The feature continues developing as Gutenberg's collaboration phase matures. Teams should check release notes with each WordPress update for new capabilities—particularly around real-time collaboration, which the current implementation enables only through asynchronous comments.
Key takeaways
- WordPress Notes adds threaded comments directly to any block—no plugin installation required
- Email notifications make async collaboration practical without constant editor monitoring
- Resolved comments persist unless manually deleted, creating a visible audit trail
- The feature works across all block types including custom third-party blocks
- Real-time collaboration remains unavailable; evaluate whether async fits your workflow before adopting
Frequently asked questions
Can I use WordPress Notes on any block type?
Yes. The feature applies to any block in the editor, including core blocks, third-party blocks and custom blocks you've developed.
Does the comment system support real-time collaboration?
Not yet. Currently, comments are asynchronous—users see notifications via email when others reply, but don't collaborate in real time within the editor.
Are resolved comments visible to site visitors?
No. Comments exist only in the editor interface. Resolved comments remain visible to logged-in users with editor access but don't appear on the published site.
Can I export comment history?
The current implementation doesn't include export functionality. For teams needing an audit trail, consider screenshots or external documentation of significant editorial decisions.
Does the feature work with WordPress multisite?
Yes, assuming users have appropriate permissions on the specific site where content is being edited. Comments don't automatically sync across a multisite network.