How to collect website feedback from clients
Clients rarely give bad feedback on purpose. They give it in the wrong place, without the page, without a screenshot, all at once in a long email. Here is a review process that fixes that, with or without a tool.
Updated
Why client feedback goes wrong
Most review rounds fail the same way. The client writes "the button on the second page looks off" in a WhatsApp message. You don't know which button, which page, or what "off" means on their phone. You reply with a question, they reply two days later, and the launch slips.
The missing pieces are almost always the same four:
- The page and the exact element they mean.
- A screenshot of what they saw, because the page on their screen is not the page on yours.
- Their browser and screen size, so you can see the bug yourself.
- One list for every note, not split across email, chat and a call.
A review process that works
- Agree on rounds before you start. Put the number of review rounds in your proposal (two is common), and what counts as a change versus new work. Clients give better feedback when they know a round is a decision, not a chat.
- Share a staging site, not screenshots or a Figma link. Clients react to the real thing differently: real content, real speed, their own phone. Review on a staging or preview address so you can keep fixing while they look.
- Tell them what to look at. "Please check the copy on Home, About and Pricing, and try the contact form on your phone" gets you useful notes. "Any thoughts?" gets you a font debate.
- One note per issue, pinned to the page. Ask the client to point at the thing and say what should change. A note on the element answers "where" for them.
- Set a deadline for the round. Three to five working days. Collect everything, then fix in one pass instead of reacting to each message as it arrives.
- Reply on each note and close it. "Done, the button is now green on mobile too" next to the client's own note shows progress better than any status email, and makes the next round shorter.
What to ask clients
Good prompts for a review round:
- Is anything factually wrong: prices, names, phone numbers, opening hours?
- Does any page say something you wouldn't say to a customer?
- Try the main action (book, buy, contact) on your phone. Did anything get in the way?
- Is anything missing that customers often ask you about?
And what not to ask in the same round: whole new pages, a new logo, "can we try it in blue". Park those for later.
Where clients should leave feedback
| Method | Good for | Problem |
|---|---|---|
| Email or chat | Small sites, one-off questions | No page, no element, no screenshot; notes get lost in threads |
| A shared document or spreadsheet | Copy changes | Clients have to describe where things are; you copy screenshots in by hand |
| Annotated screenshots | Visual issues | Takes the client several steps; still arrives by email |
| A website feedback widget | Any review round | Needs one line of code on the site, and some tools ask clients to make an account |
A feedback widget puts a button on the site itself. The client clicks it, points at the element and types. The tool attaches the screenshot, page and browser for them, and the note lands in your list. That is the only method that captures all four missing pieces without asking the client to do anything extra.
How this looks with Pinnote
Pinnote is a feedback widget built for client sites and non-technical reviewers.
- Add one script tag to the staging site. At first only your reviewers see the Feedback button; if you'd rather anyone you send the address to could comment, open it to everyone in Pinnote. Install guides cover WordPress, Shopify, Webflow, Framer, Next.js and more.
- Invite the client by email. They click the link and can comment straight away, with no account and no extension.
- They click anything and type. Each note arrives in your inbox with a screenshot of what they saw, the page, the element, their browser and screen size.
- You reply in the dashboard, and the client sees your reply on the page next to their note. Resolve it when it's done. With Claude Code, Codex or Cursor, an agent can read the notes and make the fixes too.
Invite clients to the staging site only. When the site launches, remove the script, or leave it in with visitors set to No button so they see nothing.