ShipGuardeRELEASE CLEARANCE BUREAU
How it worksUse casesDocsPricing
FREE CHECK · CONSOLE & NETWORK

What the console says when nobody is looking.

Paste a public page. It loads it in a real browser and records every uncaught error, console error and failed request, then separates the ones that are the page's fault from the ones that are not.

All six checks
RUN IT ON YOUR SITEFREE · NO ACCOUNT

Six read-only checks on one page: accessibility, performance, SEO, console and network errors, broken links, cookie handling. About a minute. Nothing is submitted, signed into, or changed.

WHAT IT LOOKS AT

The questions it asks of the page.

01Uncaught exceptions and console.error calls during load and settle
02Requests that fail: 4xx, 5xx, blocked, or a host that does not resolve
03Third-party scripts that error on every page view: analytics, chat widgets, pixels
04Requests to localhost or a staging host that leaked into production
05Content Security Policy violations that block the page's own assets
06Errors caused by the checker's own network, which are filtered out rather than reported
WHAT IT FINDS MOST OFTEN

From real public pages. No company named.

FOUND
THE HOMEPAGE REQUESTS HTTP://LOCALHOST:3000/COOKIEPOPUP.CSS

A developer's local path shipped in the build. Every visitor's browser tried to reach their own machine and failed. Use a relative or production URL for the asset, and grep the build output for localhost before deploying.

FOUND
AN INTENT-TRACKING PIXEL RETURNS 400 ON EVERY LOAD

The only failing request out of 95. The vendor changed the expected fields, so none of the visitor data was being written. Update the snippet from the vendor, then confirm the dashboard starts moving again.

FOUND
THE CSP BLOCKS THE SITE'S OWN WEB WORKER

No worker-src in the policy, so a blob: worker the page created was refused by the browser. Add worker-src 'self' blob: to the Content Security Policy.

WHAT IT CANNOT SEE

The honest limit.

One load, no interaction. Errors that only happen when a visitor clicks, types or scrolls are not seen here. That is what a journey run in the pilot is for.

Run the journey too: the pilotCheck a page now
INQUIRIES

Questions about the console & network errors check.

Are errors from your own checker filtered out?
Yes. A request blocked because our runner sits behind a bot wall, or an extension-style transport error, is the checker's problem and is never attributed to your site. That took us a few embarrassing false positives to get right.
Does a console warning count?
No. Warnings are noise on most sites. The check reports errors and failed requests.
Can I see the exact request?
Yes. Each finding carries the URL, the status, and where it was requested from.
THE OTHER FIVE

Every run does all six.

01Accessibility
02Broken links
03SEO basics
04Performance
05Cookies & consent

Code review checks the diff. ShipGuarde also checks the running product, so a release does not ship on the hope that nothing broke.

Join the free 30-day pilotStart a 7-day trial

NO CREDIT CARD · CONNECT GITHUB IN UNDER FIVE MINUTES · CANCEL ANY TIME

ShipGuarde

RELEASE CLEARANCE BUREAU
ISSUING AUTHORITY FOR SOFTWARE RELEASES
[email protected]

PRODUCT

  • Features
  • PR Reviews
  • Visual QA
  • Compare
  • Integrations
  • Pricing

RESOURCES

  • Free website check
  • Docs
  • How it works
  • Use cases
  • Sample report
  • Founding pilot
  • Blog
  • Changelog
  • FAQ
  • Support

COMPANY

  • About
  • Security
  • Status
  • Contact us
  • Privacy
  • Terms
  • Refunds
  • Sub-processors
FILED · SG-482 · ACME-COMMERCEEST. 2026