Blog ·
How to leave useful visual comments on websites.
A clear page review gives the person fixing it a specific target, a reproducible problem, and a way to check the result.
A four-step review workflow
- Review the page. Open the same preview or live URL that your team needs to check. Reproduce the issue before you write.
- Pin the element or area. Select the affected control, text, image, or layout area. If the problem spans several elements, pin the relevant area and name the parts.
- Describe expected versus actual. State what you did, what happened, and what you expected. Include the exact page URL and viewport width when the issue depends on a route, state, or screen size.
- Share, then resolve after checking. Send the thread to the person responsible. After the change, revisit that URL and viewport, test the same action, and resolve only if the result matches the request.
Example comment
Page: https://example.com/pricing · Viewport: 390 px
“On the pricing page, tap the annual plan button. Actual: its label wraps over the price at 390 px. Expected: keep the label and monthly equivalent readable without overlap.”
This is an example report, not a claim about a real defect on that site.
Choose a pin, screenshot, or written note
Pin an element when the request concerns one visible control or text block and you can revisit the page. Pin a broader area when the problem spans nearby elements. Use a screenshot when it makes a temporary state or visual difference easier to see; describe the same state in words because an image alone does not say what action produced it. A written note can be enough for copy or a simple request, but name the page and target.
Record enough context to reproduce it
Include the exact route, the action or state that reveals the issue, and the browser and viewport when they affect the result. Say whether you used a preview or production page. Keep the report limited to what is needed: do not include passwords, tokens, private account data, or unrelated personal information. The hosting and data guide explains project access and stored feedback.
Hand the thread to the person fixing it
Share the pinned thread with the engineer or designer responsible. If a coding agent will help, make sure it has repository access separately, then follow the agent workflow guide to connect and work through comments. pinthread carries the page and element context; your team still decides what change to make.
To collect comments on your own review site, follow the installation guide.
Recheck the same route and viewport
After a responsive change, revisit the original route at the reported viewport and repeat the triggering action. Check the neighboring layout too if the change could affect it. If the issue remains, reopen the discussion with what still differs. Resolve only after the page matches the expected result.
Choose a tool for the review
Checked on 25 October 2026. This is a workflow comparison, not a ranking. Read each product’s own description:
| Tool | Could fit when… | First-party source |
|---|---|---|
| pinthread | You want hosted website threads shared with a team and agent access over MCP. | Pinthread install guide |
| Agentation | You use React 18+ and want local element notes, component context, or optional Agent Sync. | Agentation FAQ |
| BugHerd | You want website element comments, screenshots, and a task board. | BugHerd website feedback |
| Pastel | You want reviewers to comment on a live URL canvas. | Pastel |
| Vibe Annotations | You want a Chromium extension and local MCP workflow. | Vibe Annotations |
These products describe different workflows. Check their current requirements and access model against your site before choosing.
Limits to keep in mind
A visual comment does not prove the cause of a defect or identify the source file. A selector or screenshot can become stale after a page change. Reproduce the issue, add the URL and relevant viewport, and verify the fix in the actual page. This guide does not claim that any one tool works on every site or produces a particular search ranking.
For background on the term, read what visual website feedback means.
Questions
What should a useful visual website comment include?
Name what you expected, what happened instead, the page URL, and the viewport when size or layout matters.
Should I resolve a comment when the code change is complete?
No. Reopen the same page and check the result first. Resolve the thread only when it matches the request.
Last reviewed: 25 October 2026. Product sources: Agentation FAQ, BugHerd website feedback, Pastel, and Vibe Annotations.