How do you collect client feedback on a website?

Use a tool that lets clients pin comments directly on the live page instead of describing changes in email. Share a link, ask them to mark exactly what they want changed, and set a clear deadline. Most vague feedback comes from asking clients to describe what they see in words instead of pointing at it.

What is the best way to get feedback on a website design?

The best method is to give clients a tool that loads the real site and lets them click on the specific element they want changed. This replaces email descriptions like 'the thing at the top' with a pin on the exact element. Set a deadline, send a reminder, and consolidate all feedback into one round before building anything.

How do I handle vague website feedback from clients?

Ask a follow-up question on the same pin: 'What would good look like here?' or 'Is this about the color, the spacing, or something else?' Keep the conversation in the tool so the context stays attached to the specific element. Never re-explain what the feedback was in a follow-up email.

How many rounds of client feedback is normal for a website?

Two to three rounds is the norm for a full website build. Round one covers the overall structure and flow. Round two covers copy and detail. Round three (if needed) covers final polish. Anything beyond three rounds usually means the scope of the project was not agreed on clearly at the start.

How to collect client feedback on a website (that's actually useful)

June 14, 20269 min readBy the Pin Feed team

Collecting client feedback on a website sounds simple. In practice it produces a 40-email thread, three conflicting versions of the same request, and a revision that fixes the wrong thing on the wrong page.

The problem is almost never that clients give bad feedback on purpose. It is that the process makes bad feedback the easiest option. When you ask someone to describe a visual change in words over email, vague is the natural result. When you give them a way to point at the thing and leave a note on it, the feedback sharpens immediately.

This guide covers the full process: choosing the right tool, framing the ask so clients know what useful feedback looks like, running the review rounds, and handling the cases where feedback is still vague anyway.

Step 1

Pick a tool that loads the live site

The first decision is what to collect feedback in. The tool determines the quality of feedback you receive, so this is worth getting right before your first client review round.

Email is the wrong tool for website feedback. When clients write “the header looks a bit off,” they are not being difficult. They are doing the best they can with the wrong medium. The tool you choose should make “off” impossible to write, because the client clicks on the header and drops a pin there instead.

What to look for

Loads the real site, not a screenshot. A screenshot of your page is frozen. Menus don't open, hover states don't fire, and responsive layouts are stuck at one width. Clients who notice something on a specific viewport or interactive state can't show you what they mean. Tools that proxy the live page don't have this problem.
No account required for clients. Every extra step between your client and their first comment costs you some feedback. A tool that requires them to sign up, verify an email, and navigate a dashboard before they can leave a note will produce less feedback than a tool that opens on a share link with just a name field.
Pins with threads, not just sticky notes. The feedback you receive will not always be complete on the first message. You need to be able to reply to a pin with a question, get a clarifying response from the client, and mark it resolved when you have built the change. A tool that only supports single comments forces that conversation back into email.
Viewport switching. If your client opens the site on mobile and notices something, they should be able to leave that pin on the mobile viewport so you see exactly what they saw. A tool that only shows one viewport loses the context.

Pin Feed loads your live site and covers all four. Clients join from a share link with just a name and email, pins thread into conversations, and desktop, tablet, and mobile viewports each keep their own set of pins. The free plan covers 3 projects with every feature.

Step 2

Frame the ask before you share the link

The second most common source of bad feedback is an unclear ask. If you send a client a review link with no instructions, you will receive whatever they thought you wanted: general impressions, copy corrections, a request to move the whole homepage around, and a note about the color of a button that was already approved three weeks ago.

Frame the review before you share the link. This takes three minutes to write and saves two rounds of revisions.

What the framing message should say

What you want feedback on specifically. “Please focus on the homepage, the Services page, and the Contact form. The blog section is not final yet, ignore it for now.” Clients will review every page if you do not tell them which ones matter.
What stage you are at. “This is the first round, so we are reviewing overall structure and flow. Copy and colors will follow in the next round.” Without this, you get copy edits in round one and structural feedback in round two, which means you rebuild the copy twice.
A deadline. “Please leave your feedback by Thursday, 5 PM.” No deadline means feedback arrives after you have already started building, spread across five messages over ten days.
How to use the tool. One sentence. “Click anything on the page to leave a note right on it.” Clients do not read onboarding docs. One sentence is enough.

The full message looks like this:

“Here is the first draft for review. For this round, please focus on the homepage and the Services page only — the blog is not ready yet. We are at the structure stage, so look at layout, navigation flow, and the sections that are there. Copy is placeholder for now. Click anything on the page to leave a note on it. Please share your feedback by Thursday at 5 PM so we can keep the project on schedule. Let me know if you have any trouble accessing the link.”

That is 85 words. It takes three minutes to write and turns a chaotic review into a scoped one.

Step 3

Run timed rounds, not open-ended reviews

The most corrosive pattern in client website feedback is the open-ended review: you share a link, the client comments whenever they get to it, you build the changes, they notice something new, they comment again, and this continues for six weeks while the project drifts past its deadline.

Timed rounds fix this. A round has a start date, an end date, a clear scope, and a decision point at the end.

A typical three-round structure

Round 1: Structure and flow

Navigation, page order, section layout, missing sections, anything that is in the wrong place. Copy is all placeholder at this stage, so changes to text do not happen here.

Timeline: 3-5 days for the client, then build.

Round 2: Copy and details

Real copy is in. Client reviews text, headings, CTAs, and content accuracy. Also covers colors, fonts, and the finer layout details now that structure is locked.

Timeline: 3-5 days for the client, then build.

Round 3: Final polish

Catches anything missed in rounds 1 and 2. Small corrections only. Structural changes at this stage are out of scope. If you need this round in writing, that is when scope creep becomes a change-order conversation.

Timeline: 2-3 days, then launch.

The key discipline is consolidation. Send one reminder the day before the deadline, collect all feedback in that round, then build. Do not build partial feedback as it arrives and do not open the next round before you have resolved the current one.

Step 4

What to do when feedback is still vague

Even with a good tool and a scoped ask, some feedback will arrive without enough information to act on. That is normal. The process for handling it is the same every time: ask a follow-up question on the pin, keep the conversation in the tool, and do not build anything against a request you do not understand.

The five most common vague feedback patterns and how to respond

"It just doesn't feel right."

Reply with: "Can you point at the specific thing that feels off? And what would right look like — warmer colors, a different layout, more white space? Even a rough direction helps."

"Make it more modern."

Reply with: "Good to know. Are you thinking about the typography, the color palette, the layout density, or something else? A reference site would also help — send me one you think has the right feel."

"The homepage needs work."

Reply with: "Noted — can you pin the specific section you are referring to and add a note there? The homepage has several sections, and knowing which part you mean will help me address the right thing."

"Can you make it pop?"

Reply with: "What do you mean by pop in this context — more contrast, a stronger CTA, a bolder heading? I want to make sure I build exactly what you are picturing."

"I'll know it when I see it."

Reply with: "Understood. I'll put together two variations on this section and you can choose the direction. That's faster than describing it back and forth."

All of these replies do the same thing: they ask for a specific, actionable direction without making the client feel like they gave bad feedback. The goal is not to correct them. It is to get the information you need to build the right thing.

Step 5

Close the round and confirm what you built

Closing a feedback round properly saves you from scope creep in the next one. When you finish building the changes from a round, send a short summary before you open the next review link.

The summary does three things. It shows the client you acted on their feedback, which builds trust. It creates a record of what was agreed on, which protects you from “I thought we changed that” later. And it sets up the next round with clear context, so you are not re-relitigating round one decisions in round two.

A round-close message template

“Round 1 is done. Here is what we addressed from your feedback:
Moved the Services section above the testimonials
Added a navigation link to the pricing page
Removed the secondary hero CTA
Round 2 is now open. This round covers real copy, colors, and fine details. The review link is [link]. Deadline is [date]. Let me know if you have questions.”

In Pin Feed, you mark each addressed pin as resolved before you send this message. The client can see exactly which pins were actioned and which (if any) you flagged as out of scope for this round.

FAQ

Common questions about client feedback

How do you collect client feedback on a website?: Use a tool that lets clients pin comments directly on the live page instead of describing changes in email. Share a link, ask them to mark exactly what they want changed, and set a clear deadline. Most vague feedback comes from asking clients to describe what they see in words instead of pointing at it.
What is the best way to get feedback on a website design?: Give clients a tool that loads the real site and lets them click the specific element they want changed. This replaces email descriptions like "the thing at the top" with a pin on the exact element. Set a deadline, send a reminder, and consolidate all feedback into one round before building anything.
How do I handle vague website feedback from clients?: Ask a follow-up question on the same pin: "What would good look like here?" or "Is this about the color, the spacing, or something else?" Keep the conversation in the tool so the context stays attached to the specific element. Never re-explain what the feedback was in a follow-up email.
How many rounds of client feedback is normal for a website?: Two to three rounds is the norm for a full website build. Round one covers structure and flow. Round two covers copy and detail. Round three (if needed) covers final polish. Anything beyond three rounds usually means the scope was not agreed on clearly at the start.

Keep reading

Stop explaining feedback over email. Pin it on the page.

Pin Feed is free for 3 projects. Clients join from a share link with just a name and email, no account, no install, no friction.

Start free

Free for 3 projects · No credit card · Clients never need accounts