Skip to main content

Error Detection

Open in QuickMonitoring→ Sites → [Your Site] → Scans → Errors

The error detection module captures JavaScript console errors, uncaught exceptions, failed HTTP requests (4xx/5xx), and broken resource loads — images, fonts, scripts that 404 — during the crawl. Real errors, caught automatically on every scan. No manual testing required.

What you'll see​

Go to Sites → your site → Errors (sidebar).

Errors are grouped by type:

  • JS Error — console.error() calls and uncaught exceptions
  • HTTP Error — pages or resources that returned 4xx or 5xx status codes
  • Broken Resource — images, stylesheets, scripts, fonts that failed to load

Each error shows:

  • The URL where it was caught
  • The error message or status code
  • Severity level (critical / warning)

How to use it​

  1. Run a scan on your site
  2. Open the scan result
  3. Go to Sites → your site → Errors (sidebar)
  4. Review errors — click any error to see full context: the page URL where it occurred, the full error message, and a stack trace if available

Sort by severity to tackle the most critical issues first. A JS error crashing a form submission is more urgent than a missing favicon.

Pass condition​

✅ You've earned this achievement when the Errors section loads and shows either 0 errors (clean site) or a list of detected errors with type labels.

Common issues​

  • JS errors from third-party scripts (analytics, chat widgets, ad networks) — These are real errors, but they may not be yours to fix. Filter by domain to separate your own scripts from external ones. Focus on errors in your own codebase first.

  • HTTP errors showing 401 or 403 — These are authentication walls. If the crawler hits a protected route, it gets a 401 back — that's expected behavior, not a bug. Unless those routes should be public, safe to ignore.

  • Same error appearing on dozens of pages — It's almost always a shared component or layout file. Fix the root cause once rather than investigating each page individually.

  • No errors found but you know there are bugs — The crawler only captures errors during initial page load. Errors that only occur after user interaction (button clicks, form submissions) won't be caught here. Use Phase 4 (AI agent tests) for interaction-driven error detection.