Skip to content
Raptor home
Menu

JavaScript error

javascript.js_console_errors
Priority
Low
Severity
Warning

What we look for

While Raptor rendered these pages in a browser, their JavaScript failed with an error the page did not handle, up to 5 errors per page.

Why it matters

An unhandled error can stop menus, forms, buttons or tracking from working, for visitors and for search engines that run the page's scripts.

How to fix

Open the page in Chrome with the developer tools console showing (press F12) to see each error, then fix or remove the script that throws it, in your site's code or plugin settings.

What it cannot know

Raptor sees the errors from one load in its own browser. Errors that depend on what a visitor does, their device or their consent choices may not show.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: javascript.js_console_errors
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "javascript.js_console_errors"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=javascript.js_console_errors
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "javascript.js_console_errors"
}