Guides

Website feedback examples: 14 comments, bad and good

Website feedback examples for design, copy, layout, mobile, bugs and approval: what a vague comment looks like, what a useful one says instead, and why.

Free forever, no card. Clients just open the link, nothing to install.

By LayerdockUpdated 6 min read
A pin comment with a mark on the part of the page it is about
On this page
  1. What makes website feedback useful
  2. Design and layout examples
  3. Copy and content examples
  4. Mobile examples
  5. Bug report examples
  6. Approval and sign-off examples
  7. Common questions

Good website feedback says where, what and why, so nobody has to ask a follow-up question. Below are fourteen website feedback examples, each as the vague comment people usually send and the useful one that gets fixed first time: design, copy, mobile, bugs and approval.

Try this on your own site

Paste your site, send one link, and your client or team pins comments on the live page. Nothing to install.

Free forever, no card. Clients just open the link, nothing to install.

What makes website feedback useful

Every useful comment in this list has the same four parts. Leave one out and the comment comes back as a question.

  • Where: the page and the element, not “the thing near the top”.
  • What: what you see, in plain words.
  • Expected: what you thought would happen or how it should look.
  • Priority: blocks launch, this round, or later.

For the rules behind these, and a template to paste, see how to give feedback on a website design.

Design and layout examples

  • Visual weight

    Bad: Make it pop more.

    Good: The “Book a call” button in the hero is the same grey as the secondary link next to it. Make it the brand purple so it reads as the main action.

    Names the element and says what change “pop” actually means.

  • Spacing

    Bad: The spacing feels off.

    Good: On the About page, the gap between the team photos and the heading above them is about twice the gap used on the Services page. Match Services.

    Gives a reference to copy instead of a feeling.

  • Typography

    Bad: Font looks weird.

    Good: The case study quotes are in italic serif, but every other quote on the site is upright sans. Use the same style as the testimonials on the homepage.

    Points at a consistency problem with an example of the right answer.

Copy and content examples

  • Wording

    Bad: Change the text here.

    Good: Hero subheading: replace “We craft digital experiences” with “We build Shopify stores for food brands”. That is what the client asked us to lead with.

    Gives the exact new text and the reason.

  • Missing content

    Bad: This page needs more.

    Good: The pricing page has no answer to “Is there a setup fee?”, which is the first question on most sales calls. Add it to the FAQ.

    Says what is missing and why it matters.

  • Accuracy

    Bad: Wrong info.

    Good: Footer phone number is the old office number. The current one is in the brand sheet, page 2.

    Says what is wrong and where the right value lives.

Mobile examples

  • Layout

    Bad: Mobile is broken.

    Good: iPhone 13, Safari: on the Services page the three cards overflow to the right and the page scrolls sideways. On desktop they sit in a row correctly.

    Device, browser, page, what happens and what is expected.

  • Tap targets

    Bad: Menu is hard to use.

    Good: On phones the menu links are so close together that I opened Blog twice when aiming for Contact. They need more space between them.

    Describes the actual failure a visitor will hit.

Bug report examples

  • Forms

    Bad: The form doesn’t work.

    Good: Contact page, Chrome on Windows: I filled every field and pressed Send. The button spins for a few seconds, then nothing happens and no email arrives. Tried twice at 3pm.

    Steps, browser, expected and actual result, and when it happened.

  • Links

    Bad: Some links are dead.

    Good: In the footer, “Careers” goes to a 404 page. Every other footer link works.

    One broken thing per comment, with exactly where it is.

  • Checkout

    Bad: Checkout is weird.

    Good: Adding a second item to the cart resets the quantity of the first one to 1. Happens every time on the product page for the blue mug.

    A reproducible bug a developer can see in one try.

Approval and sign-off examples

  • Approval

    Bad: Looks good!

    Good: Approved: Home, About and Services as they are now. Pricing still needs the setup-fee answer before I can sign it off.

    Says exactly what is approved and what is not, in writing.

  • Priority

    Bad: Lots of small things, see list.

    Good: Must fix before launch: the contact form and the footer phone number. Nice to have later: the case study quote style.

    Splits blockers from polish, so the last round has an end.

  • Scope

    Bad: Can we also add a blog?

    Good: Not for this launch, but we would like a blog next quarter. Can you quote it separately?

    Keeps a new request out of the current revision round.

Most of the “where” in these examples disappears when the comment is pinned to the element on the live page: the page, the element, a screenshot and the screen size travel with it. That is what a website commenting tool does, and why a list in an email is the hardest format to fix from.
FAQs

Frequently asked questions

Quick answers to the usual questions.

What is an example of good website feedback?

“On the pricing page, the Pro card’s button is grey on desktop and looks disabled. I expected the same purple as the hero button. This blocks launch.” It names the element, says what is wrong, says what was expected, and says how much it matters.

How do I give feedback on a website design?

Point at the element, describe what you see, say what you expected instead, and give a priority. Pinning the comment to the element on the live page does the pointing for you, with a screenshot and the screen size attached.

What is bad website feedback?

Feedback a developer cannot act on without asking a question first: “make it pop”, “something is off on mobile”, “the form is broken”. None of them says where, what or why.

How should a client give feedback on a website?

In one place, during an agreed review round, one comment per issue, pinned to the part of the page it is about. A long email with a list of numbered points loses the “where” every time.

Keep reading

More from the blog

Ready when you are

Make your next website
design review easier.

Give your team and clients one clear place to see the issue, capture the context, and share the fix.

Explore the tools