Can I put the widget only on staging?

Yes. Add the tag in a template that only staging renders, or use a separate project whose allowlist contains just the staging hostname. The allowlist fails closed, so the key does nothing anywhere else.

Will search engines or real users see it?

Only on hosts you have added to the allowlist. On any other domain the script loads and does nothing, so a key that leaks into a production build does not put a button in front of customers.

How do I tell which deploy a report came from?

Include a build or commit identifier in the page and it appears in the report URL or in the description your reviewers write. The report also carries the exact time, which narrows it to a deploy window.

For staging sites

Reviewers are looking at staging right now. Give them somewhere to put it.

Staging is where the largest number of people who are not on your team look at your work: clients, stakeholders, QA, the marketing lead who spots a typo on Thursday. What they find travels back to you as a screenshot in a chat thread, if it travels at all.

Start freeNo credit card required.

The situation

What this usually looks like

Feedback arrives as photographs of screens
Someone takes a phone picture of their monitor, sends it to a group chat, and adds "this looks wrong on my laptop". You now know neither the browser, the width, nor the page.
Nobody knows which build they were on
Staging moves several times a day. A report from Tuesday afternoon may describe something that was already fixed by the time you read it, and nothing in the message says which deploy it came from.
Comments end up in three chat threads
One in the project channel, one in a DM, one in the email thread with the client. There is no single list, so items are missed and the same one is reported twice.
You will not give a client a tracker account
Inviting a stakeholder into your issue tracker means exposing your backlog and teaching them a tool for one comment. Most teams correctly refuse, and then have nowhere to send them.

Why this fits

What changes for staging sites

Anyone on the staging URL can report: No account, no invitation, no extension. The button is on the page they were sent to review, and pressing it takes about fifteen seconds.
One project per environment: Give staging its own key, inbox and domain allowlist so review feedback never mixes with real user reports from production. Projects are unlimited on the plan.
The report says which page and which browser: URL, referrer, browser and version, operating system, window and screen size, pixel density and time zone — so "it looks wrong on my laptop" becomes a width you can reproduce.
The allowlist keeps it off production by accident: The domain list fails closed. A staging key pasted into a production template does nothing at all rather than quietly collecting real users into your review inbox.

Who this is not for

Save yourself the trial

If what you want is visual annotation on top of the page — arrows, sticky notes, a comment pinned to an element — that is the entire premise of BugHerd and Marker.io, and this tool does not do it. This collects a described report with the technical context, not a mark-up layer. The comparison pages say which tool we would send you to instead.

FAQ

Questions

Can I put the widget only on staging?: Yes. Add the tag in a template that only staging renders, or use a separate project whose allowlist contains just the staging hostname. The allowlist fails closed, so the key does nothing anywhere else.
Will search engines or real users see it?: Only on hosts you have added to the allowlist. On any other domain the script loads and does nothing, so a key that leaks into a production build does not put a button in front of customers.
How do I tell which deploy a report came from?: Include a build or commit identifier in the page and it appears in the report URL or in the description your reviewers write. The report also carries the exact time, which narrows it to a deploy window.

Put it on your site today.

One script tag. Unlimited projects, widgets and reports on one plan, and your users never make an account.

Start free Read the docs