Guides
Sharing a version for review
One private address, one version, and comments that arrive on the thing they are about.
A review link is a private address that shows one version of your site to whoever you send it to. They open it, look at the real pages on their own screen, and click anything that is wrong to say what it should be instead. There is no account to make, nothing to install, and your site's own address is not involved at all.
Everything here lives on the Review tab of a site in your dashboard.
Opening a link
Go to the site, open the Review tab and press Share for review. You are choosing four things:
- Which version. The live one, or a draft that has never been published. The link shows that version and goes on showing it whatever you publish afterwards, which is what makes an approval mean something: approving version twelve can never be read as approving version thirteen. A version you have already replaced is not offered.
- A password, optional. The address is long and unguessable, so this is for when the address itself will be forwarded to people you did not choose.
- A closing date, optional, up to the maximum your plan allows. When it passes, the link stops working on its own.
- Publish when approved, for a draft. The draft goes live the moment the link approves it, as long as you have not published something else in the meantime. This one requires a password, because the link can then change what your site serves.
You get an address like rv-g2a75ogjfq3nbsewts6csu4yuu.droply.id. Copy it with
Copy link and send it however you like. Search engines never list it, and it is
never cached anywhere, so closing it takes effect on the very next request.
What the other person sees
Your site, exactly as you built it, with a dark bar along the bottom of every page. The bar has:
- Pin a comment. They press it, then click the heading, paragraph, button or image that is wrong, and type what it should say. The bar stays in pointing mode for the next one, and Esc stops it. While pointing, clicking a link comments on the link instead of following it.
- Commit. A note that says the version needs changes before it is right.
- Approve. This version is good. On a draft shared with publish when approved, this is what puts it live.
- ? opens a short explanation of all of that. It opens once by itself the first time somebody arrives.
They can leave as many comments as they like up to the cap on your plan, come back later, and see what they have already said. If the link has a password they enter it once.
Reading what comes back
Comments land on the Review tab while you watch, without a reload. Each one is a card naming the element it was left on in its own words, so a note about the headline arrives attached to the headline rather than to a sentence trying to describe which heading was meant.
You also get one email about ten minutes after the first comment, listing everything left in that stretch. It is deliberately not one mail per comment: a reviewer working through a page leaves eight in four minutes, and eight emails is how a useful notification becomes a filter rule.
Answering a comment
Every comment card offers:
- Fix with AI opens the builder on a draft of that site with the comment in the box and the element already selected. Nothing is sent until you press send, and nothing is published until you publish it. This needs the AI builder on your plan.
- Other ways offers the same change by hand: open the editor on that file, or copy an instruction that names the site, the page and the element, to paste into whatever tool you already use.
- Mark done settles it. The comment stays, folded away, and the person who left it sees it as done immediately.
- Dismiss for a note you are not acting on.
Done and live are two different things, and the reviewer is told them separately. A comment reads as done the moment you settle it, and only reads as live on the page after you have published a version carrying the change. Publishing does not settle anything by itself, because the product cannot know whether what you published is what was asked for.
Closing a link
Press Close on the link. The next request to that address is told the link has closed, and the address is not reused. A closing date does the same thing on a timer. Closing a link that has builder drafts hanging off it says so first and discards them; the versions themselves stay in your Versions list either way.
Comments from a closed link stay on the Review tab. Closing the link ends the access, not the record.
What each plan allows
Review links, comments and approvals are on every plan. What changes higher up is how much room you get.
| Plan | Links open at once | Days a link may stay open | Comments per link |
|---|---|---|---|
| Free | 1 | 1 | 10 |
| Starter | 1 | 7 | 50 |
| Pro | 15 | 90 | 200 |
| Business | No limit | 90 | No limit |
| Enterprise | No limit | 90 | No limit |
Two more differences that are not numbers: sharing a draft needs a plan with drafts, and the bar carries a small Droply mark on free sites and not on paid ones. Marking a comment done never frees a slot against the comment cap, because the comment is still part of the record of that review.
What this is not
- There are no reviewer accounts. Everyone holding the address is the same person to us, so two people on one link are not told apart. Send two links if you need to know who said what.
- A comment is text. No attachments, no screenshots and no uploads from the review side.
- It reviews a site hosted here. It cannot put the bar on a page hosted somewhere else. If the site is elsewhere, importing it by address is usually a minute of work.
- It is not a tracker. There are no assignees, no due dates and no statuses beyond open, done and dismissed.
Privacy and what is stored
A review page is served with no caching, is never listed by a search engine, and sends no referrer to anywhere the reviewer clicks through to. What we keep is the comment text, the element it was left on, and the times it was left and settled. Visits to a review address count towards the site's own usage, the same as any other traffic to your account.
If you want the full picture of the feature before you use it, the client review feature page covers what it replaces and why it is shaped this way.
More documentation
- Publish from Claude: Connect Claude and let it publish pages and sites to your account, on every plan.
- Deploy from VS Code: Zip the current folder and publish it without leaving your editor.
- Capture a page from Chrome: The browser extension that snapshots the page you are on and hosts it.
- Automate with Zapier: Deploy from thousands of apps with no code.
- All documentation: the full index, including the custom-domain guides.