Every web agency has been here. The staging site is ready. You send the client a link and ask for feedback. Three days later, a reply arrives: 'Looks good but something feels a bit off about the homepage. Also the colours seem slightly wrong on my phone.' You now have to request clarification, wait for another response, and make a change based on a guess. Meanwhile the launch date is slipping. Getting website feedback from clients does not have to work this way — but it requires a process, not just a link.
The core problem: email is structurally wrong for website feedback
Email was not designed for giving feedback on visual interfaces. When a client types their website feedback into an email, they have to describe visual and spatial information in words — and the result is almost always vague. 'The button is in the wrong place' could refer to any of twelve buttons, on any of twenty pages, and means something different depending on which device they were viewing it on. The fix is not to ask for better descriptions. It is to give clients a tool that lets them click on the exact element they mean, pin a comment there, and move on. The precision comes from the format, not from client effort.
Step one: share a review link, not a URL to the staging site
The instinct of most agencies is to send the client the staging URL and ask them to browse and note anything they want to change. This produces unstructured feedback — a long email listing items in the order the client noticed them, with no spatial reference and no record of which page or which element. Instead, share a structured review link through a website feedback tool. The client opens the same staging site inside a review interface where clicking an element creates an attached comment. The format does the work of structuring the feedback for you.
Step two: define who is reviewing before you share anything
One of the most common sources of conflicting website feedback is undefined reviewer roles. The project manager gives their feedback. The CEO reviews it on the weekend and contradicts it. The marketing director emails separately with a third opinion. Before sharing the staging link, confirm in writing who is reviewing for content, who is reviewing for design, and who has final sign-off authority. These are different roles and should be treated as such. Three people with opinions does not produce website feedback — it produces a revision round that satisfies none of them.
Step three: set a feedback deadline and collect it all before acting
A critical discipline for reducing revision rounds is collecting all website feedback from all reviewers before making a single change. Agencies that implement client feedback piecemeal — as each person responds — end up with stakeholder A's changes already applied when stakeholder B reviews, producing contradictions and another round. Set a clear deadline — 'please leave all feedback by Thursday' — and hold to it. The client team's internal coordination is their responsibility to manage before that deadline.
Step four: require formal sign-off, not just an email saying it looks good
The end of a website review should be an unambiguous action, not an email thread that trails off. A formal sign-off — clicking an Approve button in the review tool, which generates a timestamped record with the client's name and the specific version they approved — provides exactly this. When the client later requests changes to something they already approved, the record resolves the question immediately. Without it, 'I thought we signed off on that' becomes a recurring negotiation.
“The quality of website feedback you receive is almost entirely determined by the process you use to collect it. Give clients a better tool and they give you better feedback.”
How to get useful website feedback from clients: the checklist
- Use a website feedback tool — not email — so clients click on what they mean
- Define reviewer roles before sharing the staging link
- Share a structured review link, not just the staging URL
- Set a feedback deadline and collect everything before making changes
- Require a formal sign-off action — not just an email reply
- Keep a record of what was approved and at which version
Related resources
FileFeedback
Struggling with client feedback on your projects?
FileFeedback lets clients leave frame-accurate, timestamped comments directly on your videos and images — no more email chains, no more confusion about which version they mean.
Try FileFeedback free