How to Share a Website with a Client for Feedback (The Right Way)
How to Share a Website with a Client for Feedback
The most effective way to share a website with a client for feedback is with a visual feedback tool — a link that opens the site in review mode, where clients can click directly on elements and leave pinned comments. No email, no screenshots, no description of where they mean. dotts is the simplest tool for this: you paste your staging URL, get a shareable link, and clients comment without creating an account. But the tool is only half the answer — how you frame the request matters just as much as where you collect the feedback.
The Problem with Just Sending the Link
Every freelancer has done it: built something, felt good about it, dropped the staging URL into an email with "let me know what you think", and waited.
What came back was either silence, or a wall of unstructured thoughts that took longer to decode than the original build took to finish.
Sending a website link without context is like handing someone a book and asking for notes without telling them what kind of book it is, what it's trying to accomplish, or what you want feedback on. The response you get reflects the question you asked — which, in this case, was no question at all.
The fix isn't complicated. It's a few deliberate choices around how you share, what context you provide, and what tool you use to collect the feedback.
Choose a Visual Feedback Tool Over Email
Email is the wrong medium for website feedback. It forces clients to describe visual problems in words, which introduces ambiguity at every point. "The header looks off" could mean 15 different things. There's no way to know which header, what "off" means, or whether they were looking at mobile or desktop.
A visual feedback tool — like dotts — removes this problem structurally. You share a link. The client opens the website in a special review interface. They click on whatever they want to address. A comment box appears, anchored to that exact element. They type. You see a pin on the element with their note attached.
When you open your feedback dashboard, you're not decoding descriptions. You're looking at a map of everything the client flagged, each pin exactly where they meant it.
dotts also captures browser and screen resolution automatically with every comment — so when a client reports a layout issue, you already know whether they were on Chrome on a 13" laptop or Safari on an iPhone.
Write a Two-Paragraph Context Message
Whenever you share a website for review, include a brief message alongside the link. This takes two minutes and significantly improves the quality of what comes back.
A good context message covers:
- What's included: Which pages are in this review
- What to focus on: What stage this is (structure? copy? final polish?)
- What to ignore: Placeholder images, draft copy, anything unfinished
- How to leave feedback: A one-sentence explanation of how the tool works
- When you need it by: A clear deadline
Example:
"Here's the review link for the homepage and About page: [dotts link]. We're at round 1, so please focus on layout and content — whether the structure makes sense and the copy is accurate. Placeholder images are marked with [IMAGE], ignore those for now. Just click on anything you want to flag and leave a note — no account needed. I'd love your feedback by Wednesday."
Five sentences. Completely changes what comes back.
Set a Clear Deadline
Open-ended review requests get open-ended responses. When there's no deadline, clients review when convenient — which could be immediately, or three weeks from now, after they've shown it to several other people who each have opinions.
Set a 3–5 day window for each feedback round. State it explicitly in your message. When the deadline passes, follow up once and then proceed.
This creates urgency, encourages clients to gather all their thoughts before responding (instead of trickling feedback in over days), and keeps your project timeline on track.
Share with the Right People from the Start
One of the most reliable ways to derail a project is sharing the website for review with the wrong person — your day-to-day contact who then shows it to the actual decision-maker, who has "some thoughts."
When you share a website for the first time, ask yourself: who needs to see this before it goes live? If the answer includes someone who isn't in this review, invite them now. A dotts link is easy to forward, and getting all stakeholders into round 1 beats getting a surprise fourth opinion in round 3.
If you can't control who's in the review, at minimum name the single point of contact: "Please consolidate all internal feedback into one set of notes before sending it to me."
Use Different Links for Different Rounds
If you're sharing multiple rounds of feedback on the same project, use a fresh link (or a new dotts project) for each round. This keeps the feedback cleanly separated — round 1 comments don't bleed into round 2 reviews.
When you share round 2, a brief recap helps: "I've addressed all 8 items from round 1. Here's the updated site for round 2 review: [link]. This round, please focus on the visual styling — anything that needs adjustment in color, typography, or imagery."
The recap documents what was done. The round focus keeps the feedback scoped. The new link makes clear this is a fresh review, not a continuation of the last one.
Protect Sensitive Work with a Passcode
For clients who are working on a confidential rebrand, a product launch, or anything they don't want indexed or accidentally discovered, dotts lets you password-protect shared links. You set the passcode, share it with the client alongside the link, and the site is only accessible to people who have both.
A small detail, but one that matters for clients in regulated industries or for work that's genuinely time-sensitive.
What to Do After the Feedback Comes In
Once the client has left their feedback:
- Acknowledge each comment — reply directly in the feedback thread with "on it" or a clarifying question. Don't move feedback to a separate to-do list without acknowledging it.
- Flag scope additions — if a comment adds something new outside the agreed scope, note it clearly: "This is a new item outside our revision rounds — I'll add it to the change log."
- Mark resolved as you go — as you implement changes, mark each comment resolved in dotts. This gives you and the client a clear picture of progress.
- Close the round with a summary — when all comments are addressed, send a brief note: "I've implemented all 7 items from round 1. Here's the link for round 2."
The summary creates a paper trail. The explicit close signals that round 1 is done and something new begins now.
Real Example: Before and After
Before:
Daniel shares a staging URL in an email: "Here's the first version! Let me know what you think 🙂"
Three days pass. He follows up. The client replies with a long email, some of which refers to the homepage, some to the About page, one thing mentions "the button" without specifying which, and one item is about the logo which was approved two weeks ago.
Daniel spends an hour sorting the feedback. He fixes what he can, guesses on the rest. Three revision rounds follow.
After:
Daniel shares a dotts link with a two-paragraph context message and a Wednesday deadline.
The client opens it and leaves 9 pinned comments in 20 minutes — each one anchored to the exact element. One of the "button" comments now has a pin on the specific CTA in the hero, with a note: "This color doesn't match our updated brand guidelines."
Daniel addresses all 9 items in a single working session. Round 2 needs 3 more comments. Done.
Same client. Same project. Different process.
Bottom Line
Sharing a website for client feedback is a process, not just a link. A visual feedback tool, a brief context message, a clear deadline, and the right people in the review — those four elements consistently produce better feedback, fewer rounds, and faster sign-off. None of it is complex. It just has to be done intentionally.
FAQ
What is the best way to share a website with a client for review?
Use a visual feedback tool like dotts. You paste your staging URL, get a shareable link, and clients can click directly on elements to leave comments — no account required. Pair it with a brief context message explaining what to focus on and a clear deadline.
Do clients need to sign up to leave feedback on a website?
With dotts, no. You share a link, they open it and click to comment. No signup, no email verification, no tutorial required. This is the single most important factor for getting complete feedback from non-technical clients.
How do I stop clients from sending website feedback via WhatsApp or email?
Set the expectation upfront: "I'll be sending you a feedback link — please use that for all review comments so nothing gets lost." Redirect every off-channel message: "Thanks — could you add that to the review link so I have it in writing?" Most clients adapt quickly when they understand the reason.
How long should I give clients to review a website?
3–5 business days is the standard for a single feedback round. Longer windows tend to produce lower-quality feedback (reviewed at the last minute, often after consulting more people). Shorter windows feel rushed. State the deadline clearly in your message.
What should I do if a client doesn't respond to the review link?
Follow up once at the deadline: "Just checking in — the feedback window closes today. If I don't hear back by end of day, I'll assume we're ready to move to the next stage." This creates a clear default action and prevents projects from stalling indefinitely.
Can I share a website for review if it's still in progress?
Yes. Use context to set expectations: "This is a work-in-progress — placeholder images are marked [IMAGE] and some copy is still draft. Please focus on structure and layout at this stage." Clients who understand what they're looking at give more appropriate feedback.
How do I handle multiple stakeholders reviewing the same website?
Share the dotts link with all relevant stakeholders at once, and ask the main contact to consolidate internal feedback before sending it to you. If multiple people comment independently, acknowledge all comments but look for conflicts and flag them: "I see two different preferences on this — can you confirm which direction to go?"
Share your next website the right way. [Try dotts free →](https://dotts.se)
Further reading
Start Collecting Feedback in Seconds with dotts
Forget messy email threads and unclear revision requests. dotts makes feedback fast, clear, and organized so you can focus on what matters—getting work done.