How to share a website for feedback
To share a website for feedback, paste the URL into a proxy annotation tool and send the generated review link — your client clicks any element and leaves a note pinned to it, no account. For a site that isn't live yet, a staging URL or a password-protected preview does the same job. Screenshot mark-ups work in a pinch but fall apart the moment the layout shifts.
Share a proxy review link (live site, no account needed)
Paste your live URL into an annotation tool — Drafty, Pastel, or Ruttl. You get a review link that anyone can open and comment on directly. They click the nav, the hero copy, the footer CTA, and pin a note to the exact spot. Nothing to install, no account to create. This is the fastest path when the site is already public, because the review link reflects the current live version — if you push an update, the link shows it.
Share a staging or preview link (site not live yet)
If the site isn't public, deploy it to a staging environment — most hosts (Vercel, Netlify, Kinsta) generate a preview URL on every deploy. Send that URL to the client directly. The downside: staging links are raw — no commenting layer, so feedback arrives as a voice note, a Loom, or a bullet-pointed email that forces you to cross-reference every line against the layout. Adding a proxy tool on top of the staging URL (step 1 with the staging URL, not the live domain) solves this.
Screenshot with annotations (quick, one-off)
Take a full-page screenshot — browser extensions like GoFullPage, or Command + Shift + 4 on Mac — open it in Figma, Preview, or Canva, and add red circles, arrows, and text labels. Export as PNG, attach to an email. This works for a single self-contained comment on a frozen moment. The problems start immediately after: the site changes, the screenshot no longer matches, and the client's "that button near the logo" now maps to the wrong version. Reserve this for one-off notes or when the reviewer can't open a link.
Share a Figma or v0 prototype link (design not built yet)
If you're still in the design stage — wireframes in Figma, a prototype in v0 or Framer — share the prototype link directly. Figma's built-in commenting lets reviewers click a frame and pin a note without a paid account; v0 generates a shareable preview URL. The catch is that both require the reviewer to understand they're looking at a prototype, not a finished page — client expectations often need a word of framing upfront.
Collect and centralise the feedback
Whatever method you use, the failure mode is the same: feedback arrives across email, a voice note, a Loom, and three follow-up texts — and you're spending real time reconciling four channels before you can start one revision. Centralise from the start. A shared review link means every comment is in one thread, anchored to the element it refers to, with no transcription step. The rule most designers learn the hard way: if feedback isn't on the artifact, it will drift.
Sending a client a website to review? Paste the URL into Drafty and share the link. They click the exact element — the headline, the pricing table, the mobile nav — and leave a note pinned right there. No account, no install, no screenshot. Every comment lands in one thread anchored to the spot they meant, and you can reply, resolve, and share a revised version on the same link.
Open a live demoQuestions
- How do I share a website for client feedback without them needing an account?
- Paste the URL into a proxy annotation tool and send the review link. The client opens it in any browser, clicks the element they mean, and leaves a note — no signup, no install. Tools like Drafty, Pastel, and Ruttl all support guest commenting.
- How do I share a website that isn't live yet for feedback?
- Deploy it to a staging environment — Vercel, Netlify, and most WordPress hosts generate a preview URL on every deploy. Send that URL. To add element-pinned commenting on top, paste the staging URL into a proxy annotation tool the same way you would a live URL.
- What is the best way to collect feedback on a website design?
- Send one link the client can open on any device and click directly. Element-anchored comments beat email summaries because the note is pinned to the exact spot — no "which header?" back-and-forth. The harder you make it to comment, the more likely the feedback arrives as a voice note you have to transcribe.
- Can I share a Squarespace or Wix website for feedback before it goes live?
- Yes. Squarespace has a password-protected preview mode — share the URL and the password. Wix lets you copy a share link directly from the editor. For element-pinned comments, paste the preview URL into a proxy annotation tool so reviewers can click specific spots.
- How do I share a website for feedback on mobile?
- Proxy annotation links open in any mobile browser — the reviewer taps the element they mean and types a note. Screenshots work on mobile too but suffer the same version-drift problem: the comment is attached to an image, not the live element.
- Why does email feedback on websites lead to revision cycles?
- Because descriptions of visual things are almost always ambiguous without a reference point. "The button near the top" could be three different buttons. A comment pinned to the exact element removes the ambiguity before the revision starts — designers who switch report noticeably shorter review cycles.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.