The best way to give website feedback is to mark it up directly on the live page — adding notes, highlights, and arrows where the issues are — instead of juggling loose screenshots and long email threads. Feedback that sits on the element it refers to doesn't get misread. Here's why the old way fails and how to do it better.
Why screenshots and email threads fall apart
Screenshots and email are the default because they're available, not because they're good. Both have failure modes that show up immediately on any real project.
- Screenshots go stale: the moment the layout changes, your annotated image points at a page that no longer exists.
- Email threads bury feedback: by reply five, nobody can tell which comments are still open.
- Context gets separated: the screenshot is in one place, the explanation in another, the page in a third.
- Numbered lists drift: "issue 3" means nothing once the page or the order changes.
The result is rework. Someone fixes the wrong thing, or misses a comment that was three replies up.
Put the feedback on the page
The single biggest improvement is to attach each comment to the exact element it's about. When the note lives on the misaligned button, there's no ambiguity about which button. You're replacing "describe the location in words" with "point at it."
You can do this with a free browser extension. Highlite lets you highlight, add sticky notes, draw, and arrow on any live page, then capture a screenshot of the result — no account, nothing uploaded. You still send an image, but now the image carries the full context: location plus comment, together.
Old way: "On the about page, the second section, the text on the right is too close to the image, and I think the heading should be bigger." New way: a screenshot with an arrow between the text and image ("add spacing") and a note on the heading ("+4px").
Rules for feedback that lands the first time
- One comment, one issue. Don't pack three problems into one note.
- Anchor every comment to its element with a note, highlight, or arrow.
- Say what you want, not just what's wrong: "make this green" beats "this color is off."
- Capture enough surrounding context in the screenshot so the location is obvious.
- If there are many issues, number them so the order to address them is clear.
When you need more than markup
If feedback has to be tracked, assigned, and revisited by a team over time, a hosted tool with a dashboard earns its keep — see the BugHerd alternative writeup. For everyday, one-pass feedback, marking up the page and sending an image is faster and clearer than the screenshot-and-thread routine it replaces.
Related: collecting client feedback on a live website and using the same approach to annotate websites for bug reports.
Feedback templates you can reuse
Good feedback follows a pattern. Keep these phrasings handy and most of your notes write themselves:
- Change request: "Make this [element] [specific change]" — e.g. "make this button the brand green."
- Bug: "This [element] does [wrong behavior]; expected [correct behavior]."
- Question: "Is this [element] intentional? It reads as [interpretation]."
- Approval: "This section is good as-is" — saying what works prevents accidental changes.
Frequently asked questions
How do I give website feedback without screenshots?
Annotate the live page directly with a browser extension — notes, highlights, and arrows on the actual elements — then share that. You still send an image, but it carries the location and the comment together, instead of a bare screenshot plus a separate written explanation.
What's the best way to give feedback to a developer?
Point at the exact element and state expected vs. actual. Developers lose the most time guessing which element you mean; an arrow or highlight removes that entirely. For bug-specific reports, the bug-report workflow adds repro steps to the same approach.
How do I give feedback on a website I don't own?
A client-side annotator works on any page you can open, including sites you don't control — you're marking up your own view of the page, not changing it for anyone else. Capture the screenshot and share it.
Try the better way on this page — mark up a heading and a paragraph, then capture it. That single image is clearer than the email you'd have written instead.