How to get client feedback on a website that you can actually use.

Every web designer knows the message: "Can we change that bit at the top? And the blue feels off on mobile." Which bit? Which blue? On which phone? Vague feedback is not a sign of a difficult client. It is what happens when someone who does not build websites is asked to describe one in words, away from the thing itself.

The good news is that most of it can be fixed with process rather than patience. Here is a way to get feedback that is specific, complete and easy to act on.

1. Decide what kind of feedback you need right now

Feedback on a sitemap, on a design direction and on a nearly finished build are three different conversations. If you ask "what do you think?" at every stage, you will get comments on everything at every stage, including fonts during the structure phase and structure during the polish phase.

Before each review, tell the client what is open and what is settled. For example:

• Structure: are the pages and sections right? Is anything missing?
• Look and feel: does the design suit the brand? Do the photos work?
• Content: is every word correct, and is anything out of date?
• Final check: does everything work on their phone and their computer?

One sentence such as "This round is about content and wording; the layout is agreed" saves a lot of back-and-forth.

2. Ask on the real page, not about it

Screenshots, PDFs and emails all describe the website from outside. The client has to say where the problem is, and you have to work out what they meant. That translation is where most confusion starts.

Feedback works best when the client can point at the thing itself: this heading, this button, this photo, on the page as it really looks, at their screen size. Then "that bit at the top" turns into a note attached to the exact element, and nobody has to guess.

You can do this with a shared call where they point and you take notes, with annotated screenshots, or with a tool that lets clients pin comments directly on the site. Whichever you use, the principle is the same: the comment should live where the change is.

3. Keep all feedback in one place

The second biggest source of confusion is feedback spread across channels: one point by email, two in a messaging app, one said on a call and a document with "a few more thoughts". Things get missed, and the client remembers what you forgot.

Agree on one place for feedback at the start of the project and say it in your proposal. If something arrives somewhere else, move it into the agreed place yourself and reply there. Clients learn quickly where their comments get answered.

4. Ask better questions

Open questions get open answers. Specific questions get decisions. Instead of "Any feedback?", try:

• "Is there anything on this page that is factually wrong?"
• "Would you be comfortable sending this page to your best customer today? If not, what stops you?"
• "Which of these two headlines sounds more like you?"
• "Please check the contact details and opening hours carefully. These are the things visitors rely on."

And always say when you need the answers by. A review without a date tends to drift.

5. Make it easy for every person involved

Often the person you talk to is not the only person with an opinion. A partner, a manager or a colleague in marketing will look too. If each of them needs an account, a password and a tutorial, some will not bother, and their comments will arrive later, on WhatsApp, after you thought you had finished.

Ask at the start who needs to review, and give each of them the same simple way in. The fewer steps between opening the link and leaving a comment, the more complete the feedback.

6. Reply to every note, and close the loop

A note without an answer is an open question. When you make a change, say so under the note. When you decide not to make a change, explain why there too. This creates a written record that is easy to read back later, and it shows the client that nothing was ignored.

Then ask for a clear decision on each page: approved, or still needs work. A page that is "probably fine" is not approved. The guide on approval rounds goes into this in more depth.

7. Check on more than one screen

Many clients will look at the website on their phone first, often while doing something else. Ask them to look on both a phone and a computer, and say which matters most for their visitors. If your feedback method lets them switch between phone and computer views, even better.

A simple feedback brief you can copy

Send something like this with every review link:

• What this review is about (for example: "wording and photos on all pages").
• What is already agreed and should not change.
• Who should review, and the date you need comments by.
• Where to leave comments, and one example of a good comment ("The opening hours in the footer should say 9:00 to 18:00").
• What happens next: you reply to every comment, make the changes, and ask for each page's approval.

Where Tweakpin fits

Tweakpin was built for exactly this step. You add one line of code to your client's site (or the free WordPress plugin), and send your client a link. They click the thing they want changed on the real page and leave a note pinned right there, with no account or browser extension. You answer under the note, and they mark each page as approved when it is done. It works on WordPress, Elementor, Webflow, Shopify, Wix, Squarespace, Framer and any site where you can add a line of code.

It is not the only way to do this, and the habits above matter more than the tool. But if your feedback still arrives as screenshots and voice notes, letting the client point at the page itself is the quickest improvement you can make.