To collect client feedback on a live website, give the client a way to point at the page directly — marking up the real site with notes and arrows — instead of describing changes in an email. It removes the translation step where "move that thing up a bit" turns into three rounds of clarification. Here's how to set up a workflow that actually works.
Why written feedback breaks down
Clients usually aren't designers or developers, so they describe visual problems in approximate language. "It feels cramped." "Can the button be more obvious?" "Something's off with the spacing." You know there's a real issue in there, but you have to interview them to find it.
- The client writes a paragraph describing a layout problem.
- You read it three times and still aren't sure which element they mean.
- You ask for a screenshot. They send one with no markup.
- You guess, make a change, and find out next week it was the wrong element.
None of this is the client's fault. Words are just a bad medium for visual problems.
Let the client point at the page
The fix is to move feedback onto the page itself. If the client can circle the cramped section and write "too tight here" right on it, the ambiguity disappears. There are two broad ways to do this.
Option 1: a hosted review tool
Tools like BugHerd or Markup.io host a review project where the client leaves comments pinned to the page, and you manage everything from a dashboard. This is the right choice for ongoing engagements where feedback needs to be tracked and assigned. The cost is setup and an account for everyone involved. The BugHerd comparison goes deeper on when that's worth it.
Option 2: a free browser annotator
For lighter engagements, the client can mark up the page with a free browser extension and send you a screenshot. Highlite works for this: the client highlights, adds notes, draws arrows, and captures an image — no account, nothing uploaded to a third party. You get a marked-up screenshot back in the same email thread.
Instead of "the homepage hero needs work," the client sends you a screenshot with an arrow on the headline ("too generic"), a note on the image ("use the team photo"), and a highlight on the CTA ("make this green"). You implement it in one pass.
Make the workflow client-proof
- Tell the client exactly which page (or pages) to review, with the link.
- Ask them to mark up the live site and send back a screenshot — show them once how.
- Request one note per issue so nothing gets bundled and lost.
- Set a deadline; open-ended review invitations tend to stall.
The simpler the ask, the more likely a busy client actually does it. A free, no-account tool lowers the barrier — there's nothing for them to sign up for.
For the broader principles, see how to give website feedback without screenshots and email threads, and if you run an agency, website feedback for agencies covers scaling this across clients.
A repeatable client-feedback process
One-off feedback is fine, but if you collect client feedback regularly, a small repeatable process saves you from reinventing it each project:
- Stage the page at a stable URL and confirm the client can open it.
- Send a one-line instruction: review this page, mark each issue, send back the screenshot.
- Ask for one note per issue, with the desired outcome, not just the complaint.
- Set a review deadline so the project doesn't stall waiting on feedback.
- Consolidate the marked-up screenshots into your task list and implement in one pass.
This article is about the general process. If you're a designer specifically, the companion piece on client feedback for UI designers goes into the design-handoff angle, and if you run a studio, website feedback for agencies covers doing this across many clients at once.
Frequently asked questions
What's the easiest way to collect client feedback on a website?
Have the client mark up the live page and send you a screenshot. With a free, no-account browser extension there's nothing for them to sign up for, which is usually the difference between getting feedback and getting silence.
Do clients need to install anything?
It depends on the tool. Hosted platforms often let the client comment via a link without installing anything, but they need an account. A client-side extension asks the client to install it once, in exchange for no account and full privacy. Pick based on which friction your clients tolerate better.
Want to see what your client would experience? Mark up this page — circle a heading, leave a note — then capture it. That ten-second flow is exactly what you'd ask them to do.