How to Get Feedback on a Website From Clients (The Right Way)
How to Get Feedback on a Website From Clients
The most reliable way to get useful feedback on a website from clients is to give them a visual feedback tool — a shared link they can open and click directly on whatever they want to address. When clients can point instead of describe, the quality of feedback improves immediately. Beyond the tool, the other half of the equation is setting up the process correctly: who reviews, when, how many rounds, and what counts as complete. This guide covers both.
Why Website Feedback Goes Wrong
Getting feedback on a website from a client sounds simple. It almost never is.
The problem isn't that clients have bad taste or unreasonable expectations. It's that they're being asked to do something genuinely difficult: translate a visual experience into written words, without a shared vocabulary, and send it back in whatever format feels natural to them — which is usually WhatsApp.
The result is feedback that's either too vague to act on ("can you make it more modern?"), too prescriptive without understanding the constraint ("move the logo 15 pixels to the left"), or scattered across so many channels that you're spending 45 minutes just aggregating it before you can do anything.
A well-designed feedback process removes all of this friction. Here's how to build one.
Step 1: Set Up a Visual Feedback Link
The single most impactful change you can make to your website feedback process is switching from email to a visual feedback tool.
Instead of asking the client to describe what they see, you share a link that opens your staging site in a special review mode. The client clicks anywhere on the page — a headline, a button, a section of the layout — and leaves a comment right there. The comment is pinned to that exact element. When you open your feedback dashboard, you see a pin map of everything they flagged, each one anchored to the pixel they meant.
dotts is the simplest tool for this. You paste your staging URL, get a shareable link, send it to the client. They don't need an account. They just open it, click, and type. Device and browser data is automatically captured with every comment, which is useful for debugging layout issues.
For PDFs, wireframe exports, or image assets, dotts handles those too — same click-to-comment experience, same no-account client flow.
Step 2: Tell the Client Exactly What to Do
Even with the best tool, clients give better feedback when you give them a simple instruction. Don't assume they'll intuitively know how to use a visual feedback link, even though it takes about 10 seconds to understand. A short message alongside the link goes a long way:
"Here's the review link: [link]. Just click on anything you want to change and leave a note — you don't need to sign up for anything. I've included your homepage, About page, and Contact page in this round. The deadline for feedback is Thursday."
Three things in that message: what to do, what's included, and the deadline. That's all they need.
Step 3: Define Who Gives Feedback and When
The most avoidable source of late-stage revisions is the late-appearing stakeholder. This is the managing director, business partner, or spouse who sees the website for the first time in round 3 and has "a few thoughts."
To prevent this:
- Ask at kickoff: "Who else will need to approve this before it goes live?" Get that person in the review from the beginning.
- Define a single point of contact for feedback. If multiple people review internally, they consolidate feedback before it comes to you — you receive one set of notes, not three sets that sometimes contradict each other.
- Put this in your contract. "Feedback will be collected from [name/role] as the designated reviewer. Additional stakeholders may be included in internal review rounds before submitting feedback."
Step 4: Set a Clear Deadline for Each Feedback Round
Open-ended feedback rounds are a trap. Without a deadline, clients respond when it's convenient for them — which could be three days from now, two weeks from now, or after they've shown it to four more people and collected a new list of opinions.
A simple rule: each feedback round has a 3–5 day window. After that, you proceed to the next stage. This creates urgency without being aggressive, and it keeps the project timeline from slipping indefinitely.
In practice, your message can simply include: "Please leave your feedback by [date]. After that, I'll begin implementing the changes and move us to the next round."
When the deadline arrives, follow up once. If there's no response, it's reasonable to proceed — especially if your contract supports this.
Step 5: Separate Rounds Clearly
One of the most common causes of revision confusion is mixing feedback from different rounds. The client gives feedback on the initial design, you make changes, they look at the updated version — and suddenly they're commenting on something from the first round that they thought was already fixed, or adding something new and calling it "a small thing from before."
Keep rounds cleanly separated:
- Use a fresh dotts link for each round (or a new project) so the feedback is clearly scoped to the current version
- When you send the round 2 link, briefly recap what was changed based on round 1
- Make it easy for the client to see that their previous feedback was addressed before they give more
This prevents the "I thought we fixed that" conversation, and it makes scope creep easier to identify when something genuinely new appears in a late round.
Step 6: Respond to Feedback in the Tool
Don't move feedback from the tool into a separate to-do list without acknowledging it. This creates ambiguity: the client doesn't know if you've seen their comments, and you end up with feedback in one place and status updates in another.
Instead, respond directly in the feedback thread:
- Reply to each comment with either "On it" or a brief question if clarification is needed
- Mark comments as resolved when you've addressed them
- If something is out of scope, note it clearly in the comment thread: "This falls outside our agreed scope — happy to include it in a change order if you'd like to proceed."
This keeps a complete, timestamped record of everything that was said and agreed. Useful when anyone asks "didn't we already fix that?" six weeks later.
Step 7: Define What "Done" Looks Like
Revisions don't officially end unless you formally close them. Without a clear signal, projects linger in an ambiguous state where the client might keep adding things and you're not sure whether to keep accepting them.
After your final revision round:
- Send a summary of everything that was changed
- Confirm that all feedback has been addressed
- State explicitly that the project is ready for launch and that additional changes will be scoped as new work
A short email does it: "I've implemented all feedback from round 2. Everything is ready for your review and approval before we go live. Please confirm, and I'll prepare the handover."
That sentence does three things: it documents the state of the project, it asks for explicit approval, and it sets the expectation that what comes after this is paid work.
Real Example: Before and After
Before process (typical scenario):
Sofia builds a portfolio site for a physiotherapy clinic. She sends the staging link via email. Three days later she receives a mix of notes in a reply chain, a voice note, and two photos of the screen taken on a phone. She makes what she thinks are the right changes. The client replies that the logo is still "too big" — but Sofia moved it, not resized it. Two more rounds follow, each with new items added. Total: 4 rounds, 6 hours unplanned.
After process (with dotts + defined rounds):
Sofia shares a dotts link with a 4-day feedback deadline. The client clicks on 9 elements and leaves specific comments. Sofia addresses all of them in one working session, replies in the tool, and marks each resolved. She sends round 2 with a brief summary of changes. The client approves. Total: 2 rounds, 2.5 hours.
Same client, same project complexity. Different process, different outcome.
Bottom Line
Getting good feedback on a website is mostly a process problem, not a client problem. When you give clients a structured way to give feedback, set clear deadlines, and keep rounds separated, the quality and speed of the feedback loop improves dramatically. A visual feedback tool like dotts is the single most impactful change you can make — and the setup takes under five minutes.
FAQ
What is the best way to collect website feedback from clients?
The most effective approach is a visual feedback tool — software that lets clients click directly on the element they're commenting on, rather than trying to describe it in an email. dotts is the most streamlined option for freelancers: no client account required, works on websites and PDFs, and captures browser data automatically.
How do I get feedback from clients who aren't tech-savvy?
Keep it as simple as possible. A visual tool with a shareable link — where the client just opens and clicks — is the right approach for non-technical clients. Pair it with a one-sentence instruction: "Click on anything you want to change and leave a note." That's all they need.
How many revision rounds should I include?
Two is the most common standard for web design projects. Include this in your contract, communicate it at kickoff, and treat any feedback beyond the included rounds as change order work. Defined rounds improve feedback quality — clients take each round more seriously when they know it's finite.
How do I stop clients from adding new things in later rounds?
By clearly separating rounds and stating upfront how many are included. When a new item appears in round 3, note it in the feedback thread: "This is a new request outside our included rounds — I'll add it to the change log and we can scope it separately." Having this documented in the original contract removes the awkwardness from that conversation.
What should I do if a client gives feedback by phone or WhatsApp?
Acknowledge it, and then ask them to add it to the feedback link: "Thanks — could you add that as a comment on the review link so I have it written down? It helps me make sure nothing gets missed." This gently redirects them to the proper channel without confrontation.
Do clients need to sign up to use dotts?
No. You share a link, they open it and click to leave comments. No account, no email verification, no setup. This is the single biggest reason it works well with non-technical clients.
How do I handle feedback from multiple stakeholders?
Ask clients to consolidate internal feedback before sending it to you. You should receive one round of notes, not separate rounds from different people that sometimes contradict each other. Define the single point of contact at project kickoff and include it in your contract.
Ready to fix your feedback process? [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.