Getting feedback

Website feedback examples: good, bad and vague, with the fix for each

Thirty real-shaped examples of website feedback, sorted into useful, vague and off-target, with what each one means and how to turn it into a change you can make

The HopBack teamOctober 20269 minutes read

Key takeaways

  1. Good website feedback names a specific thing on a specific page and says what is wrong with it for whom: "The headline on the home page says 'solutions' and our customers never use that word." Vague feedback names a feeling without a location: "It doesn't pop." Off-target feedback is about something other than the design: the brief, the business, or the reviewer's browser.
  2. Below are thirty examples across those three kinds, drawn from the reviews we run as an agency, with what each one usually means and the reply that gets a usable answer.
  3. None of the bad ones are the client's fault.

What makes feedback usable

Feedback you can act on has three parts, and the best clients give them without being asked.

  • A location. Which page, which element. "The second heading" is a location. "The top bit" is nearly one. "The site" is not.
  • An observation. What is there now, in the client's words. "The photo is of an office, not a warehouse."
  • A reason or a wish. Why it matters or what they would prefer. "Our customers are warehouse managers and they will not see themselves in it."

Most feedback arrives with one of the three. The job of the reply is to get the other two, without making the client feel they did it wrong.

Good website feedback examples

These are the ones you want more of. Say thank you for them, specifically, and the client learns to send more.

  1. "On the home page, the headline says 'end-to-end solutions.' We never say that. We say 'we pick, pack and ship.'" Location, observation, the fix in their own words. This is the gold standard.
  2. "The photo at the top of the About page is a stock office. Our team is in high-vis in a warehouse. Can we use one of ours?" A wish with a reason, and an offer of the asset.
  3. "On my phone the menu button is behind the chat widget, so I can't open it." A bug, with the device and the exact collision. Reproducible in one try.
  4. "The pricing page lists the Studio plan first. Most people buy Starter; can Starter go first?" A business reason attached to a layout request.
  5. "The contact form asks for a phone number before an email. Our customers hate giving phone numbers." Observation plus a reason you could not have known.
  6. "The green on the buttons is lighter than the green in our logo. Logo is #1f7a4c." Specific, with the value. Takes two minutes to fix.
  7. "Service page, third paragraph: this describes what we used to do. We stopped offering installs in 2024." A content correction with the fact.
  8. "The testimonials are all from 2019. We have newer ones; I'll send three by Friday." A gap, a promise, a date.
  9. "The footer says 'Auckland and Wellington.' We closed Wellington." Small, exact, done.
  10. "I like it. The only thing I'd change is the hero image; it reads as a bank, not a bakery." Praise and one change, with the reason.

What they share: a noun. The photo, the headline, the menu button, the green. Feedback with a noun in it can be built.

Vague feedback, and what it usually means

Vague feedback is real feedback without a location. The client has a reaction and no word for it yet. The reply is a question that gives them one.

  1. "Make it pop." Usually means contrast: the page reads flat to them. Reply: "Which part feels flat, the top of the home page or further down? And is it the colors or the size of things?" Nine times in ten the answer is the hero.
  2. "It doesn't feel like us." Usually about photography or tone of voice, not layout. Reply: "Is it the pictures, the words, or the colors that feel off? Point me at one spot and I'll fix the pattern."
  3. "Can it be more modern?" Usually means more white space, bigger type, fewer boxes. Reply: "Send me two sites you think of as modern and I'll show you what they have in common."
  4. "It looks busy." Usually one section with too much in it. Reply: "Which section would you cut first if you had to?"
  5. "Something's off on the About page." A real signal with no handle. Reply: "Read it out loud and tell me where you stumble." It works surprisingly often.
  6. "The colors are wrong." Usually one color, not all of them. Reply: "Which one, and where do you see it most?"
  7. "It needs to be more professional." Usually a font or a photo. Reply: "Is there a competitor's site that feels professional to you? I'll compare them side by side."
  8. "I'm not sure about the layout." Usually the order of sections. Reply: "What do you want people to see first, second and third?"
  9. "Can we make the logo bigger?" The famous one. Usually means the brand feels buried, not that the logo is small. Reply: "Let me try two things: the logo bigger, and the logo the same size with more space around it. You pick."
  10. "Looks good, just a few tweaks." Followed by nothing. Reply: "Great. Pin the tweaks on the link so I don't guess, and I'll have them done by Thursday."

The pattern in every reply: narrow the location, offer a choice of two, name a date.

Off-target feedback, and how to steer it

Off-target feedback is about something the design cannot fix, or something that was decided earlier. It is still useful; it just belongs somewhere else.

  1. "Our competitor has a chatbot. Can we have a chatbot?" A scope request dressed as feedback. Reply: "Happy to quote that as an add-on. For this round, is there anything on the pages as they are?"
  2. "I showed it to my husband and he thinks the whole thing should be blue." A new reviewer arriving late with a new direction. Reply: "Blue is a bigger change than this round; let's note it for the next project. Is there anything you'd change yourself?"
  3. "The site is slow." Often the staging server, or their office Wi-Fi. Reply: "Staging is on a slow box; the live site will be on a fast one. If a specific page feels slow, tell me which and I'll check it."
  4. "I can't see it properly." Often an old browser or a tiny laptop. Reply: "What device are you on? Send me a screenshot and I'll see what you're seeing."
  5. "Can we change the brief? I think we're targeting the wrong people." The most important thing they will say all project, and the design cannot answer it. Reply: "Yes, and that's a conversation, not a comment. Can we do twenty minutes tomorrow?"
  6. "My brother-in-law does websites and he says WordPress is better." Reply: "He might be right for some sites. For yours we chose X because Y. Happy to walk through it on a call."
  7. "I don't like the font." Sometimes about the brand font they approved in the logo. Reply: "That's your brand typeface from the guidelines. Is it the size, the weight, or the face itself?"
  8. "Can you add our Instagram feed, a newsletter pop-up, a video on the home page and a blog?" Four scope items. Reply: "All possible. Which one matters most for launch? The rest go on the list for phase two."
  9. "Just copy what [big brand] does." Reply: "Which part of it? Their hero, their menu, their checkout? I'll take the pattern, not the page."
  10. "This isn't what I expected." The hardest one, and usually a gap between the brief and the design that nobody saw. Reply: "Tell me what you pictured, and I'll show you where we went a different way and why. Then we decide together."

How to get more of the good kind

The difference between the first ten examples and the rest is not the client. It is the container they were given.

  • Review on the thing itself. When the client clicks the headline and types, the location comes for free. The email is where "make it pop" lives.
  • Ask for a number. "Pin anything you'd change. Five pins is a great round." Permission to be brief is permission to be honest.
  • Give a deadline, not an open window. "By Friday" gets the quick, specific pass. An open window gets the essay.
  • Send the reviewer guide with the first link. One page on how to give feedback does more than any amount of coaching on a call. Ours is at For clients.
  • Thank the specific ones. "That note about the warehouse photo was exactly right" is how clients learn what good looks like.

How HopBack handles this

In HopBack the client opens the real site, or the design or PDF, and clicks the thing they mean. The comment carries the element, the page and the screen size, so every piece of feedback arrives with a location, which is the part that was missing from examples eleven to twenty. Rounds and a deadline take care of "just a few tweaks." The reviewer guide is one click from the review.

Questions people ask

What is an example of good website feedback?

"On the home page, the headline says 'end-to-end solutions.' We never say that; we say 'we pick, pack and ship.'" It names the page, the element, what is there, and what the client wants instead.

How do I respond to vague website feedback?

Narrow the location with one question, offer a choice of two, and name a date. "Which part feels flat? I'll try two versions and have them to you by Thursday."

What should I ask clients when requesting website feedback?

Ask for the three things on the page that bother them most, in order, and give a deadline. Three located notes beat a page of impressions.

Is it rude to push back on client feedback?

No, as long as you push toward specifics rather than away from the client. Every reply above takes the feedback seriously and asks for the detail that makes it buildable.

How many rounds of feedback should a website have?

Three on design and two on the build is the common shape. Write it into the plan and the contract; see the website project plan template.

Get feedback with a location on it, every time

14 days of Studio. No card needed.

One email a month, no more

Short, practical, about client feedback and running an agency. Unsubscribe in one click.