Review any site with the Chrome extension
Pin feedback on a site you cannot add a script to — a client's production build, a competitor's page, a locked-down CMS — using the Pogpin browser extension.
The widget snippet is the best option for a site you control. The extension covers everything else: leave pinned visual feedback on any website, without touching its code.
When to reach for it
| Situation | Use |
|---|---|
| You can edit the site’s template | the widget snippet |
| Staging behind a login, or a URL you cannot modify | the extension, or proxy review mode |
| The page’s Content-Security-Policy blocks injected scripts | the extension — it runs independently of the page CSP |
That last row is the one that saves the day. A strict CSP can refuse an injected snippet; the extension runs as browser chrome, so the page’s policy does not apply to it.
Install and connect
- Install Pogpin Review Overlay in Chrome.
- Open your project in Pogpin and copy its connection code.
- Click the extension icon, paste the code into Connection code and press Connect.
The popup then offers Open dashboard and Disconnect. One connection per project — reconnect with a different code to point the extension somewhere else.
Review
Open any page and click the extension icon. The Pogpin overlay loads on top of the page with the same toolbar you already know: comment mode, viewport switching, the issue list and the visual editor.
Pins land in the project you connected, carrying the same automatic context as a widget pin — browser, OS, screen size, URL and the exact element.
If a page will not load in proxy mode
Proxy review mode is the zero-install path for public and staging URLs, but some sites refuse to be framed or proxied. When that happens Pogpin says so — the proxy could not load a readable page — and offers the way out, in order:
- Use the extension, which is not subject to the page’s CSP.
- For a site you control, add the Pogpin snippet to its template.
- Allow the Pogpin API origin in
script-srcandconnect-src, and the dashboard inframe-ancestors.
You can also save a screenshot review from that state, so the round of feedback is not lost while the access question is sorted out.