Console Error Scanner
Load a page in a real browser and capture its console errors.
How it works
Enter a URL and a real headless Chromium browser loads the page exactly as a visitor's browser would — scripts execute, requests fire, and everything the console would show gets captured.
The scan reports console errors and warnings, uncaught JavaScript exceptions, requests that failed or returned 4xx/5xx, and mixed content — insecure http:// requests made from an https:// page.
The whole capture, grouped by kind with per-request sources, downloads as CSV or JSON, free and instant. Scans take up to about 20 seconds because a real browser is doing real work.
Frequently asked questions
Why do console errors matter if the page looks fine?
Errors that don't visibly break the layout still break things you can't see at a glance: form handlers, analytics, personalization, lazy-loaded content. They're also the first place a rendering crawler's experience diverges from yours.
How is this different from the fetch-based checkers?
The other checkers read the HTML your server returns. This one executes it in real Chromium — so it catches problems that only exist after JavaScript runs, which is where most modern front-end breakage lives.
What is mixed content?
An https:// page loading a subresource over plain http://. Browsers block or strip these requests, so the image, script, or stylesheet silently fails for visitors even though the tag looks correct in your source.
Errors surfaced. Experience fixed.
BuildSEO AI sends real referral traffic through verified backlinks — make sure the page it lands on works.
Try BuildSEO AI