CLIENT REVIEW
Send a client review link and get comments on the page
One private address showing one version of your site. Whoever opens it clicks the thing that is wrong and says what it should be, with no account and no screenshot.
Free plan, free SSL, no credit card.
Plan availability
Which plans include client review
Review links, comments and approvals are on every plan, free included. The paid tiers add room: more links at once, a longer window, and our name off the bar.
- Free Included
- Starter Included
- Pro Included
- Business Included
- Enterprise Included
Read from the plan records this account is billed against, not from a page someone wrote, so it cannot disagree with what happens when you click the button. See every plan and its limits.
What it does
The feedback arrives attached to the thing it is about
A review link is its own address showing one version of your site, with a bar at the bottom, and everything said there is recorded against the element it was said about.
Open a link on a version, set a password and a closing date if you want them, and send the address. Whoever opens it sees your site as you built it, with a bar along the bottom they did not have to install or sign up for. They can approve the version, ask for changes, or click any heading, paragraph, button or image and type what should be different about it. Each of those becomes a card in your dashboard naming the element in its own words, so "the headline should mention our new hours" arrives attached to the headline rather than to a sentence trying to describe which one.
The usual round trip is a screenshot with a circle drawn on it, or a numbered list in an email that says "third block down, the bold bit", and the work is reading it twice and guessing. Here the comment carries the element, so you can send it straight to the AI builder with the target already set, read the change, and publish. The person who left it is told it is done once the new version is live, never before. And a link belongs to one version on purpose: approving version twelve can never be read as approving version thirteen, which is the same reason rollback keeps every version rather than overwriting one.
Where to open one
It lives on the site you want looked at
Open that site in your dashboard. Review sits beside Overview, and one button on it starts a link.
- Dashboard
- Your site
- Review
- Share for review
How to use it
Three steps
-
Pick the version to share
The live one, or a draft nobody else can reach yet. The link shows that version and keeps showing it, whatever you publish afterwards.
-
Set a password and a closing date
Both optional, both one field. The address is unguessable already, and a password is what makes forwarding it harmless.
-
Send the address and read the comments
They arrive on your dashboard as they are left, on the element each one names, with an approval or a request for changes at the end.
Where it earns its keep
When people reach for this
A build going to a client before launch
The version they sign off is the version they are looking at, and their notes come back attached to the page. Pair it with a password when the address will be forwarded.
A copy pass on a page that is already live
Share the live version, collect the wording changes on the elements they are about, and publish. The address you sent follows the new version, so nobody needs a second link.
A round of changes you would rather not publish first
Share a draft instead of the live site. Your public address goes on serving what it served before, and the draft can go live the moment it is approved.
The alternative
Doing this without us
The two substitutes are a screenshot in a chat thread, and a general-purpose annotation tool bolted onto a site.
| Droply | Screenshots and email | |
|---|---|---|
| What the comment is attached to | The element itself, named in its own words. | A picture of the page, or a description of where to look. |
| Which version was approved | One link shows one version, and that is what the approval is against. | Whatever was live when the mail was sent, which has usually changed. |
| What the client has to install | Nothing. They open an address. | Nothing, or an account and a browser extension. |
| Turning a comment into a change | Send it to the builder, element already selected. | Find the element by hand and hope it is the right one. |
| Knowing it was dealt with | The comment closes, and the client is told once the change is live. | Another email saying it is done. |
Compared against the screenshot-and-email round trip and the general annotation tools commonly used for web feedback. Checked September 2026.
When this is not the right tool
It is a way to get comments on one version of one site from people who have no account. It is deliberately not a project tracker and not a permission system.
- Everyone holding the address is the same person to us. There are no reviewer accounts, so two clients on one link are not told apart.
- A comment is text. There are no attachments, no screenshots and no file uploads from the review side.
- It reviews a site hosted here. It cannot put a comment bar on a page hosted somewhere else, though importing one by URL is usually a minute of work.
- Answering a comment with the AI builder needs the builder on your plan. Marking one done by hand works on every tier.