Website error tracking: what broke and who it hit
See what broke, and who fixes it.
Start free. No card needed. Plans and limits are on the pricing page.

What Convertlyft catches
Error tracking catches what breaks in your visitors’ browsers. In Convertlyft, the line of code that records your visits also catches code that threw, files that didn’t load and requests that failed, on every page carrying it. Each one is grouped into an issue, with how many times it happened, how many people it hit and when it was last seen.
- JS error. Code on the page that threw.
- File didn’t load. A file the page asked for and never got.
- Request failed. A request the page made that failed. A failure on your own server is yours to fix.
Some errors are real but not your site’s problem: thrown by a visitor’s browser, an extension or an in-app browser, or a request cut off because the visitor left or lost signal. Those are set aside. They are never deleted, never counted as your site’s problems and never notify you, and you can bring any of them back.
From an error to the change to make
What to do lists to-dos, each with the measurement behind it and one change to make where there is one. An error your visitors hit can be one of them. When you have made the change, press I fixed it; the next check marks it Confirmed fixed or Came back.

Who fixes it
Every issue sits in one of three lanes, so you know whose job it is before you open it.
- Yours to fix. It came from your site’s own code.
- Tell the app maker. It came from an app or plugin you added, or from the platform your site runs on.
- Can’t see where it came from. The browser didn’t say which file it came from, or we don’t recognize that file. These are not counted and never notify you. Answer Is this mine? once, and the issue moves to its lane.
Each issue also says how sure we are: we can see the exact spot, we can see the file but not the exact line (no source map), we know which app, or we can’t see where it came from. Where your site publishes a source map, the stack points to the line in your own code.
What you see for one error
- How many. How many times it happened, how many people it hit, and when it was first and last seen.
- Where. The page, the browser and the line it came from.
- Its status. New, Getting worse, Came back, Ongoing or Quiet, with the reason beside it.
- The visits behind it. Watch the recorded visits behind this, and see what happened on the page.

Hand the fix to your developer, or to your AI
- Copy for your developer. One press copies a write-up of the error: for an AI, short or in full, a developer ticket, or a note for whoever built it. Email addresses, card numbers and anything that looked personal are removed first.
- Fix it with your AI. In the AI app you have connected to Convertlyft, ask it to fix the error. It reads the write-up itself, signed in, and tells you the change before it makes it.
- Open it in a developer’s tool. Claude Code, Cursor or Codex, with the write-up filled in. Nothing sends by itself.
Fix it with your AI and the developer’s tools are there for errors in your own code whose source we can place. For the rest, the write-up is ready to copy and send to whoever built it. Nothing on your site changes until someone on your side makes the change.

When it’s fixed
Mark an error fixed and it reads Fixed — checking while we watch the next visits to its pages. Once enough visits reach those pages that we would have seen it, and we didn’t, it moves to Confirmed fixed. If it happens again, it moves to Came back. An error that stops with no fix moves to Went quiet once its pages have had enough visits since.
Where you see errors
Errors have a place of their own in the dashboard, under Site health. Errors in your own code that are New, Getting worse or Came back are counted on the sidebar badge, and the Monday report lists the week’s new errors. On a heatmap, switch the map to clicks followed by an error to see where on the page it happened.
Your AI tools can read errors too
Convertlyft is an MCP server at https://mcp.convertlyft.com/mcp. A connected AI app can list the errors your visitors hit and read an error’s write-up before it proposes a change. Connect your AI →
How to track errors on your website, step by step
- Start free. No card needed.
- Add the line of code. We spot Shopify, WordPress, Wix, Squarespace, Webflow, Framer, Next.js or a tag manager and show the steps.
- Mark your own devices once: errors from devices you’ve marked as yours are left out of the count.
- Open Site health › Errors. Yours to fix comes first.
- Copy it for your developer or fix it with your AI, then mark it fixed.
What it costs
Convertlyft is free up to 5,000 visits a month, with recordings, heatmaps, funnels and errors on every plan. The full table of plans is on the pricing page. Your new account starts on Pro at 10,000 visits a month, free for 14 days. No card needed. Open the demo →
Check your site free first: an SEO audit of up to 25 pages, no account.
Questions
What is error tracking?
Error tracking catches what breaks in your visitors’ browsers, such as code that threw, a file that didn’t load or a request that failed, and groups each one into an issue: what broke, how often, and how many people it hit.
What errors does Convertlyft catch?
Code that threw, files that didn’t load and requests that failed, on every page carrying our tag. Errors thrown by a visitor’s browser or an extension, and requests cut off because the visitor left or lost signal, are set aside and never counted as your site’s problems.
Do I need to add anything to track errors?
No. The line of code that records your visits catches errors too.
Who fixes an error?
Each issue sits in one of three lanes: Yours to fix, for your site’s own code; Tell the app maker, for an app or plugin you added or the platform; and Can’t see where it came from, which asks you once whether it is yours.
Can my AI app fix an error?
For an error in your own code, ask the AI app you have connected to Convertlyft to fix it. It reads the write-up itself, signed in, and tells you the change before it makes it.
Is what visitors type recorded?
No. Typed values never leave the visitor’s browser. Email addresses, phone numbers and payment card numbers shown on the page are masked too.
How much does Convertlyft cost?
Free up to 5,000 visits a month, with every feature. The plans above that are on the pricing page.
Start on Pro, free for 14 days
Your new account gets 10,000 visits a month, no card needed. After 14 days it moves to Free, up to 5,000 visits a month with every feature, unless you choose Pro.