WordPress 7.1 Notes vs Client Review Tools: What Changes for Agencies
WordPress 7.1 Notes help logged-in collaborators review content in the block editor. Client review tools serve a different need: collecting feedback on the rendered website and recording approval. The right choice depends on who is reviewing and what they need to check.
WordPress 7.1 was released on 19 August 2026. This comparison now reflects the released Notes features, rather than the earlier roadmap.
What WordPress 7.1 adds to Notes
The official Notes documentation describes comments on selected text, multiple threads on a block, rich text and mentions. Notes can be resolved and reopened. They are visible to people with permission to edit the post, not to visitors on the public page.
The released documentation does not describe an accept-or-reject tracked-changes mode. Our earlier article presented that roadmap idea as a shipped feature; that claim has been removed.
The distinction that matters: who is giving the feedback
Notes live in the block editor. To leave one, a person needs a WordPress user account on your site with editing access, and they need to be comfortable working inside the editor. That is exactly right for writers, editors and developers on the same team.
It is usually the wrong shape for a client. Most agencies do not want to create editor-level accounts for a client’s marketing manager, and most clients do not want to learn the block editor to say “this headline should be shorter”. There is also the awkward fact that a client with editor access can change things you did not ask them to change.
And Notes are attached to blocks in the editor, not to the rendered page. A client reviewing a site is reacting to the thing the public will see: spacing, a sticky header, how a section behaves on their phone. Plenty of that feedback has no block to attach itself to.
Core Notes vs a client review tool
| WordPress 7.1 Notes | A client review tool like Reviso | |
|---|---|---|
| Who it is for | Logged-in collaborators with edit access | Clients and stakeholders with no account |
| Where feedback happens | Inside the block editor | On the live rendered page, at any screen size |
| Account needed | Yes, a WordPress user | No, a share link |
| Discuss wording changes | Comments attached to selected text | Comments on the rendered page |
| Works with Bricks and Elementor pages | Blocks only | Yes, native to Bricks, Elementor and Gutenberg |
| Formal client approval and sign-off record | No | Yes, timestamped, with a PDF certificate on Pro |
| Feedback across a whole site or many sites | Per post or page | Whole-site reviews |
| Price | Free with WordPress | Free core plugin, paid tiers |
So should you drop your review tool?
Use core Notes if your review loop is internal, your content lives in blocks, and everyone involved already logs in. Try the built-in workflow before adding another tool.
Keep a dedicated client review tool if the person you need feedback from is a client, if the sites you build use Bricks or Elementor rather than blocks, or if you need the round to end with a recorded approval you can point at later. That last one is the gap core has never tried to fill: Notes are a conversation, not a sign-off.
The honest read is that WordPress 7.1 does not replace client review, it raises the baseline for internal collaboration and makes the boundary clearer. For an agency, the remaining question is how clients review the finished page and confirm that the work is ready.
What we are doing about it
Reviso already works this way: your client opens a link with no account, pins comments on the live page, can propose replacement wording in place, and approves the page when it is right, leaving a timestamped record. Use Notes for internal editorial discussion and Reviso for client review where that division suits your project.
If you want the client side of this now, the free plugin covers unlimited sites, or see how it compares to other client feedback tools.