Visual review
The fastest way to gather feedback on a website without making someone install anything: share a review link. Reviewers open it in a browser, click on the page to drop pins, and submit. Their tasks land directly in your project board.
How it works
Every WebPinch project has a guest token (a short nanoid). Wrap the token in one of WebPinch’s review URLs and you’ve got a self-contained feedback page.
| URL | What it does |
|---|---|
/guest/{token} | Lander page. Shows three ways for the reviewer (or you) to activate the widget — bookmarklet, embed snippet, manual iframe. |
/review/{token} | Full visual review tool. Loads the project’s website inside an iframe with a sidebar for pins. |
/review/{token} is what you usually share. /guest/{token} is more useful for installing the widget into the reviewer’s own workflow.
Sharing the link
Get the project guest token
Project Settings → Integration → Extension Token. Copy.
Construct the review URL
https://www.webpinch.com/review/<paste-token-here>Send it
Email, Slack, anywhere. Anyone with the URL can review. No sign-up.
The guest token is the access key. Don’t post the URL publicly if you don’t want anonymous strangers submitting tasks. Treat it like a “by invitation” link — easy to revoke (rotate the token in project settings), but harder to lock down.
What the reviewer sees
On /review/{token}:
- Left: the project’s website inside an iframe, navigable like any other browser tab.
- Top: a toolbar with the project name, pin count, and back/reload buttons.
- Right: the review sidebar listing every pin on this page.
Click anywhere on the iframe to drop a pin. A pin form appears asking for:
- Title (required) — short summary
- Description (optional) — details, repro steps
- Email (optional) — so they get notified when the issue is resolved
Submit, and the task appears immediately in your project’s kanban — typically in the Backlog column.
What’s captured
Same automatic metadata as the browser extension: screenshot, pin coordinates, CSS selector, page URL, browser, OS, screen size, plus the reviewer’s email if they entered one.
Existing pins are visible
Reviewers see pins that have already been placed on the same URL. This avoids duplicate reports — if someone else has already pinned the broken login button, the next reviewer sees that pin and can comment instead.
Pins on /review/{token} are read-only for guests. Only authenticated dashboard users can edit, comment on, or close a task.
Behind a login? Use authenticated proxy
If your site requires authentication (Google, GitHub, Azure AD, Auth0, Okta), reviewers normally can’t access it from inside the iframe. Configure Authenticated Proxy in Project Settings → Authenticated Proxy — WebPinch will proxy the requests through your authenticated session so reviewers see what you see, without needing their own credentials to your site.
Embedding the widget on your site
If you’d rather have your visitors give feedback through a button on your own site (instead of through /review/{token}), copy the embed snippet from Project Settings → Integration:
<script src="https://www.webpinch.com/api/widget/YOUR_GUEST_TOKEN"></script>Paste it before the closing </body> tag. A floating WebPinch button appears for visitors, submitting through the same flow as the extension and the review URL.
That one URL is a bootstrap: it loads the widget and configures it for your project, so you don’t pass any data- attributes yourself. It also carries whether the “Powered by WebPinch” badge applies, which is resolved from the project owner’s plan — see Billing.
When to pick which workflow
| Workflow | Best for |
|---|---|
/review/{token} | Sending a one-off review link to a client or QA tester |
| Embed snippet | Always-on feedback button on a staging or beta site |
| Bookmarklet (from the lander page) | Reviewers who want WebPinch on every page they visit, without installing anything |
| Browser extension | Internal team members using WebPinch frequently across many projects |