Most visual feedback tools start with a snippet: paste a line of code into your site, and a feedback widget appears. It's the right default for staging sites and projects you control.
But a surprising amount of review happens on sites where you can't add code. A client's live production site behind a change-control process. A prospect's site you're auditing before a pitch. A third-party page you're using as a reference. A platform that doesn't let you inject scripts.
That's what a browser extension is for.
When a browser extension beats a snippet
Client production sites. Adding a script to production often means a ticket, an approval and a deploy. For a one-off review, that's more process than the review itself.
Pre-sales audits. You want to walk a prospect through twenty specific issues on their current site. You don't have access to it, and you shouldn't need it.
Reference and competitor research. "Make our pricing table work like this one" is clearer with pins on the page you mean.
Locked-down platforms. Some hosted builders and enterprise CMSs restrict custom scripts, or only allow them on paid tiers.
Quick internal QA. A developer wants to log five issues on a deploy preview without adding anything to the build.
In each case, the extension gives you the same point-and-click workflow without touching the site's code.
How it works in pinreview
- Install the pinreview extension in your browser and sign in.
- Open the site you want to review — any URL.
- Turn on feedback and click the element you want to comment on.
- Type your comment. Optionally annotate the screenshot with boxes, arrows, freehand or text.
- Submit. The feedback lands as a task on your project's board.
Each pin captures the same context as the snippet does: a full-page screenshot, the exact CSS selector of the element, the URL, viewport size, browser, OS and any console errors. Developers get a reproducible report whether it came from the widget or the extension.
The extension is included on pinreview's paid plans.
Inviting others to review with the extension
You can invite guests to review a site through a shareable link. When the target site doesn't have the pinreview snippet installed, reviewers need the extension to leave pins on it: the link checks whether it's installed, opens the site with feedback switched on if it is, and prompts them to add it if not.
That's a small but real ask for external reviewers, so match the method to the audience:
- Internal teammates and technical reviewers — the extension is a one-time install and works on any site.
- Clients reviewing a site you control — prefer the snippet. They click and comment with nothing to install.
- Clients reviewing a site you don't control — the extension is the way in; tell them in advance that there's a one-time install.
Either way, guests are unlimited and free on every plan.
Snippet vs extension at a glance
| Snippet (widget) | Browser extension | |
|---|---|---|
| Needs access to site code | Yes, once | No |
| Reviewers install anything | No | Yes, one time |
| Works on third-party sites | No | Yes |
| Best for | Staging, client review, your own sites | Production audits, locked platforms, research |
| Captured context | Screenshot, selector, URL, browser, OS, viewport, console errors | The same |
| Where feedback lands | Your project board | Your project board |
Most teams end up using both: the snippet on every staging site they build, and the extension for everything else. Our guide to adding a feedback widget to any website covers the snippet side.
Tips for reviewing a site you don't control
Say which environment you reviewed. Production and staging drift. The URL is captured automatically, but mention it in your summary to the client too.
Review at more than one screen size. Resize the window or use your browser's device mode; the viewport is recorded with each pin, so developers know which layout you saw.
Keep pins specific. One element, one issue. "The whole page feels off" is hard to act on; five pins on five specific problems are not.
Don't audit what you can't change. On third-party pages, pin the patterns you want to copy or avoid, and label them clearly so nobody tries to "fix" someone else's site.
Share the board, not a PDF. For a pre-sales audit, walking a prospect through a live board of pinned issues is more persuasive than a static report — and each issue is already a task if they sign.
The bottom line
A snippet is the best way to collect feedback on sites you control. A browser extension covers everything else: production sites behind process, platforms that block scripts, audits, research and quick internal QA.
pinreview gives you both, with the same captured context and the same board at the end, so where the feedback came from never changes how it gets fixed.