About this plugin
Somebody finds something broken on your site: a client, a colleague, a customer. They press Report issue, write one sentence and send it.
Your team gets a report with everything they never typed:
- a screenshot of the page, with password fields blurred before it is taken
- the page’s address, the browser, the operating system and the screen size
- the element on the page, if they pointed at one
- the JavaScript errors and console warnings from your site’s own code
- the requests that failed around the moment they reported
Nobody has to explain what they were doing, and nobody has to ask them what browser they use.
Nobody needs an account to report
The people reporting write a sentence and press Send. No sign-up, no email address required, nothing to install. That is the point: the person who finds the bug is rarely the person who can fix it.
Made for sites you build for someone else
Send your client the site, and their “the form doesn’t work” arrives with the error that stopped it. Before launch, show the button only to people logged in to the site, so your client can report and visitors see nothing. After launch, turn it on for everyone.
Where the reports go
com, as an email to your team if they want one, and into the tracker your team already uses once you connect it. A developer can hand a report to a coding agent, which opens a fix for your team to review.
Light on your pages
The button loads after your page and never delays it. The screenshot tool is only downloaded when somebody starts a report.
Getting started
- Install and activate the plugin.
- Create a free account on brokenhere.com and add your site.
- Paste your project key under Settings › Broken Here.
Broken Here is free for one site. com/pricing.
External services
com), a bug-reporting service. Nothing is loaded from it until you save a project key.
js, in the visitor’s browser. com for your project’s settings; that request says which site it came from, which is how your project’s Setup shows that the button is live.
When somebody sends a report, the widget sends Broken Here:
- what they wrote, and their name and email only if they give them;
- the page’s address, with the value of any parameter named like a secret (a token, a password, a session) replaced in the browser;
- the browser, operating system, window size and language;
- a screenshot of the page, with password fields and any area you choose blurred in the browser first, and any images they attach;
- the element they pointed at, if they did;
- recent JavaScript errors and console warnings and errors from your site’s own code;
- recent and failed network requests: the address without its query string, the method, the status and how long it took.
Request bodies are sent only if you turn that on in your project’s settings, only for failed requests to your own site, with anything under a secret-looking name replaced in the browser. log output, and it sets no cookies. It keeps an unsent report in the visitor’s own browser so it is not lost, and a sign-in token for your team members.
com.
com/terms
com/privacy