How to Ask Clients for Feedback on Their Website Without Losing Your Mind

The way you ask for feedback matters more than almost anything else in a web project. Ask well and you get useful notes you can act on in an hour. Ask badly and you get three weeks of back-and-forth where nobody is sure what's been decided. Here's what actually works.

I've asked clients for feedback thousands of times over nine years of running a web agency. I've tried every version of the ask I can think of. Long Google Docs. Short emails. Loom walkthroughs. Zoom calls where the client clicks around and narrates what they don't like. Pinned comments on the live site. Formal revision request forms with ten fields. I've seen what works and what doesn't, and I can tell you the difference is almost entirely about two things: specificity and structure.

This isn't going to be a post about active listening or "creating space for honest feedback." Those posts exist. This post is about the practical mechanics. What do you actually say in the email? What questions do you ask? When do you ask them? How do you prevent the client from sending you a 40-item list two weeks after you thought the project was done?

The one mistake that wrecks every review cycle

Before we get into what to do, let's talk about what not to do, because there's one mistake I see every agency make at least once and most agencies make every single project. It's this: asking an open-ended question like "what do you think?"

I know. It sounds friendly. It sounds collaborative. But "what do you think?" is the worst question you can ask a client, and here's why. The client hasn't had time to process what they're looking at. The client doesn't know what kind of feedback you're looking for. The client is going to panic a little bit, because they don't want to give the wrong answer. So they'll either give you something safe and useless ("looks great!") or they'll dump every half-formed opinion they have at once ("I'm not sure about the colors, my wife didn't love the hero image, someone on my team said the navigation is confusing, and can we get rid of the footer?").

Neither response helps you ship the project. The first leaves you guessing what they actually think. The second leaves you with a mess of unprioritized, half-baked ideas that you now have to interpret, challenge, and possibly ignore, all while keeping the client feeling heard.

The fix is simple in theory and hard in practice: stop asking open questions, start asking specific ones. Don't say "what do you think?" Say "does this headline say what you want it to say?" The first is a conversation starter. The second is an actionable question with a clear answer.

The eight questions that actually work

Here's the list I've refined over the years. I walk clients through these in order, either in an email or in a Loom video, and I make it clear that I want them to answer each one specifically. Not all of them apply to every project, but most do.

1. Does the homepage headline say what you want it to say?

This is the most important question for almost every client site because the headline is the one thing every visitor will read. I want a direct yes or no. If the client says no, I want them to suggest an alternative or at least describe what's missing. "It doesn't feel warm enough" is okay. "It sounds corporate when we want to sound like a neighborhood shop" is better. The more direction the client can give me on the intent, the easier it is to fix.

2. If a stranger landed on this page, would they know what you do in five seconds?

This is a gut check. It flushes out structural problems that the client might not articulate on their own. If the answer is no, the fix usually isn't cosmetic, it's architectural. Something above the fold isn't doing its job.

3. Are there any pages that feel like they shouldn't exist?

Agency sites almost always have too many pages. Clients will include their grandmother's blog post from 2019 because they don't want to hurt anyone's feelings. Ask this question early and you'll save yourself from doing good work on pages that shouldn't be on the site at all.

4. Are there any pages that are missing?

The inverse of the last one. Clients often realize they need a page they hadn't thought to ask for. An FAQ. A service detail page. A case study. Ask now, before you push v2, so you don't end up in scope creep territory in week six.

5. On mobile, is there anything that feels cramped or off?

You need to ask about mobile specifically because most clients will review the site on desktop by default. If you just say "take a look at the site," they'll open it on their 27 inch monitor, skim it, and never check how it looks on their phone. Then three days after launch they'll text you "why does this look weird on my iPhone?" Ask the question upfront.

6. Is there anything your competitors do that you want us to consider?

This is a strategic question disguised as a feedback question. It tells you what the client is comparing your work to, which helps you contextualize their other feedback. If they mention a competitor with a slick animated hero, and they've been giving you vague notes about the hero feeling "flat," now you know what they actually want. They don't have the vocabulary to ask for animation, but they feel it when they see it.

7. Is there anything that feels like it's missing trust?

Trust elements are things like testimonials, reviews, certifications, guarantees, photos of real people, phone numbers, physical addresses. Clients know intuitively when their site doesn't feel trustworthy, but they rarely diagnose it correctly. Asking this question prompts them to think about it, and their answer usually points you at the right fixes.

8. Is there any page or section you're embarrassed to send to a customer?

This is the question I ask last, and it's the one that consistently surfaces the most useful feedback. "Embarrassed to send to a customer" is a much sharper threshold than "needs work." If a client says "I wouldn't be embarrassed to send any of this," you're done. If they hesitate on a page, now you know exactly where to focus your next round of work.

When to ask these questions

Timing matters almost as much as the questions themselves. Here's the sequence I use for a typical website project.

At the start of the project: ask about competitors, trust, and missing pages. These are strategic questions and the answers will shape the whole build. Don't wait until the site is done to find out the client wanted a testimonials section.

After the first design draft: ask about the homepage headline, the five second gut check, and any pages that feel wrong. These are the big-picture questions and you want to catch any structural issues before you invest time in polish.

After the first development pass: ask about mobile and the embarrassment question. Now you have real content in a real browser and the client can react to something close to the final product. This is also where I pull out a website feedback tool and have the client leave pinned comments on specific elements instead of emailing me a list.

Before launch: one final pass on the embarrassment question. If they still hesitate, fix that thing before you go live. If they don't hesitate, you're ready to ship.

Templates you can steal

Here are the exact templates I use. Copy them, change the names, use them today.

What to do when a client gives you bad feedback

Sometimes you do everything right and you still get bad feedback. The client gives you vague notes, or contradictory notes, or notes that would actively hurt the project if you followed them. Here's how to handle each.

Vague feedback

"The colors feel off" or "the hero doesn't pop." Don't argue, don't guess, don't just start randomly changing things. Respond with a specific follow-up question that forces the client to be concrete. "When you say the colors feel off, do you mean the accent blue is too bright, or the warm tones aren't warm enough, or something else? If you can pull up one or two websites where the colors feel right to you, that would help me a lot." You're not being difficult, you're saving both of you from three rounds of color experiments.

Contradictory feedback

"Make it more modern" and "our customers are older and want something familiar." These are the fun ones. Your job is to name the contradiction gently and let the client resolve it. "I want to make sure I understand. You want the design to feel modern, but you also want it to feel familiar to an older audience. Those can pull in different directions. Can you tell me which matters more if we have to pick one?" Nine times out of ten the client will pick. The tenth time they'll give you a brilliant third answer you hadn't thought of.

Feedback that would hurt the project

"Make the logo bigger." "Add more text to the hero." "Can you use Comic Sans?" (I wish I was kidding about that last one.) This is the hardest category because you need to push back without making the client feel overruled. The move here is to explain the tradeoff specifically. "I can make the logo bigger, but it'll push the headline down below the fold on most screens, which means new visitors won't see what you do until they scroll. Would you rather have the bigger logo or the visible headline?" Now the client owns the decision. If they still want the bigger logo, at least they understand the cost.

The single best change you can make to your review process

If you only do one thing from this post, do this: stop taking feedback over email, and start using a tool that lets clients leave pinned comments on specific elements on the live site.

Every problem in this post gets smaller when the feedback is pinned to a specific element. "The colors feel off" becomes "this button needs to be a different shade of blue," because the client has to click on something specific before they can leave a note. "The hero doesn't pop" becomes a pin on the actual hero element, where you can see exactly what they were looking at and on which device. Contradictory feedback becomes visible because you can see both comments in the same dashboard and point them out to the client.

This isn't a plug for our tool specifically. (Though yes, SiteRev does exactly this and the trial is free.) Any good website feedback tool will give you this. The specific tool matters less than the principle: pinned feedback on live elements is fundamentally better than written feedback in an email, and once you've worked that way for a week you'll never go back.

The takeaway

The agencies that ship projects on time aren't the ones with the best designers or the fastest developers. They're the ones who've figured out how to get useful feedback from clients on the first try. The questions in this post are the ones I've found that actually work. The templates are the ones I actually send. The tool recommendation is real advice from someone who got tired of chasing vague revisions.

Try one thing from this post on your next project. Even just the "what would you be embarrassed to send to a customer" question on its own will surface more useful feedback than any open-ended "what do you think" ever has. Report back.