For teams that deploy front ends
Find the console errors and broken assets a deploy shipped
Load the page in a real browser and get back its console errors, uncaught exceptions and failed requests as JSON.
The problem
The page returns 200 and the HTML looks right, but a script threw on load, an image path changed and a font now answers 404. A server-side check cannot see any of it, because none of it happens until a browser runs the page.
How domscout handles it
diagnostics records what the browser saw while the page loaded: console messages, uncaught page errors, requests that failed outright, and every response with its status, so an asset that answered 404 or 500 is listed even though the page itself loaded. A summary counts each kind, so a CI step can fail when pageErrorCount or failedRequestCount is above zero without reading the lists. Cookies, authorization headers, form values and request bodies are never returned.
Where it shows up
- A post-deploy smoke test on the pages that carry revenue.
- A pre-merge check against the preview deployment.
- A scheduled sweep that turns new console errors into tickets.
The request
POST /scrape. diagnostics starts at Pro and adds 1 credit, so each page costs 2. The findings are under analysis.diagnostics. With maxEntries at 250 or less they come back in the same response; without it the capture runs as a job to poll. debugOverlay, on every plan, draws the same findings onto a screenshot instead.
Go further
More in Testing and QA: Responsive layout checks · Visual regression testing · Signup and checkout flow checks · Hover, focus and dark mode screenshots · Localization screenshots · Unlabelled control checks · A screenshot of every step · Embedded widget checks · Screenshots for support tickets · Ad landing page checks · Before and after hydration · Selectors for test automation · Print layout checks · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.