Why email and screenshots do not scale
A small website project can easily produce fifty pieces of feedback. If they arrive as screenshots, forwarded emails, chat messages and calls, someone has to merge them, work out which page each refers to and guess the device. Most missed or misunderstood changes come from that translation step, not from the work itself.
Three ways to collect comments on a live site
| Approach | How it works | Trade-off |
|---|---|---|
| Script or widget | You add a snippet to the site; reviewers comment on the site itself. | Needs access to the site and a deployment; leaves a third-party script to remove later. |
| Browser extension | Reviewers install an extension and annotate any page. | Non-technical clients often will not install anything. |
| URL-based review | You paste the URL into a tool that loads the site through a proxy and adds the comment layer. | No change to the site, but the site must be reachable and some sites cannot be displayed. |
Symu 2 and Pastel use the URL-based approach. BugHerd, Marker.io and Feedbucket typically rely on a script or an extension. None is universally better, so pick by who controls the site and who is reviewing it.
A simple process for a review round
- Prepare a stable URL. Use a staging or preview URL that will not change during the round.
- Create the review. In Symu 2, paste the URL into a new project.
- Write a two-line brief. What you want checked and the deadline. Send it with the share link.
- Let the client comment. They enter a name and click elements. No account is needed.
- Triage. Each comment is a task with a status. Merge duplicates and ask questions in the comment thread.
- Fix in a batch. Do it yourself, or hand the open comments to an AI coding agent through MCP or a markdown export.
- Reply and resolve. Tell the client what changed, then send the same link for a verification round.
Limits to plan for
- Public reachability. A server-side tool cannot open
localhostor an office-only network. - Logins. Pages behind a login are not supported by Symu 2. Use a public staging copy or screenshots.
- Protected or embed-blocking sites. Strict bot protection or headers that forbid display inside another page can stop a site loading. Ask for a staging URL without those rules.
Do not forget mobile
Clients often review on a laptop and forget the phone. Use a tool with a device switcher and ask for at least one pass on the mobile view. In Symu 2 every comment stores its breakpoint, so you can filter mobile-only issues later.
Ready to try it? Read the client feedback overview or start a free 14-day trial. Comparing tools? See the 2026 roundup.