# 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. ## Plan availability 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 ## 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. ## How to use it 1. **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. 2. **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. 3. **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. ## 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. ## Doing this without us The two substitutes are a screenshot in a chat thread, and a general-purpose annotation tool bolted onto a site. - **What the comment is attached to.** Droply: The element itself, named in its own words. Screenshots and email: A picture of the page, or a description of where to look. - **Which version was approved.** Droply: One link shows one version, and that is what the approval is against. Screenshots and email: Whatever was live when the mail was sent, which has usually changed. - **What the client has to install.** Droply: Nothing. They open an address. Screenshots and email: Nothing, or an account and a browser extension. - **Turning a comment into a change.** Droply: Send it to the builder, element already selected. Screenshots and email: Find the element by hand and hope it is the right one. - **Knowing it was dealt with.** Droply: The comment closes, and the client is told once the change is live. Screenshots and email: 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. ## Frequently asked questions ### Does my client need an account? No. They open an address and use the bar at the bottom of the page. There is nothing to install, nothing to sign up for and no invitation to accept. ### Can I share something before it goes live? Yes, from Pro and above, by sharing a draft. Your public address goes on serving what it served before, and the draft can be published the moment it is approved. ### What happens to a comment when I publish a change? Nothing closes itself just because you published. A comment is settled by you, or by the generation that edited the text, and the reviewer sees it as done once a version has gone live carrying it. ### Can the link publish the site when my client approves it? Yes, for a draft, on a plan that has drafts, and only when the link carries a password. Their approval then puts that version live without you being at your desk. ### What if I send a new version halfway through? The address stays the same and follows it. Comments left on the earlier version stay open and say so: the client asked for something and it is still not done, which survives a republish. ### Can I close a link I have already sent? Yes. Revoking it takes effect on the next request, and setting a closing date does the same thing on a timer, the way an expiring link does for a published site. Anyone opening a closed link is told it has closed rather than shown the site. ## Related features - [Version rollback](https://droply.host/features/version-rollback) - [Password protection](https://droply.host/features/password-protection) - [Expiring links](https://droply.host/features/expiring-links)