Audit completed with errors

An audit can finish in one of three states: green (clean), orange (completed with errors) or red (failed). Orange means we got useful data but ran into trouble on some URLs. Almost every orange audit is still worth reviewing – you just need to know which errors to act on.

Where to find the error breakdown

On the audit report, click the orange banner at the top. A panel opens listing every error type with a count and the first five affected URLs. From there you can click any URL to see the raw response we received.

Common errors and what they mean

Connection timeout (ECONNABORTED)

A URL didn't respond within 30 seconds. Causes: slow origin server, cold-start serverless function, oversized page rendering. If the count is small (under 5% of URLs), it's usually intermittent – rerun the audit. If it's widespread, your origin is overloaded and needs investigation.

HTTP 403 Forbidden

The server actively refused our request. Most often this is your CDN flagging us as a bot. Allow-list our user agent or IP block (contact support for the current list).

HTTP 429 Too Many Requests

Your server or CDN is rate-limiting us. Lower the concurrency in Settings → Crawl from 3 to 1, raise the delay from 500ms to 1500ms, and rerun. We don't hammer sites by default, but some shared hosts have very tight limits.

HTTP 5xx (500, 502, 503, 504)

Your origin server returned an error. If the affected URLs all share a path prefix (e.g. /blog/), that section of the site is genuinely broken. If they're scattered, it's probably load-related – your origin was struggling during the audit.

TLS / SSL errors

Your HTTPS certificate is expired, mismatched (wrong domain) or uses an outdated cipher. Fix the cert – Google penalizes mixed-content and broken-cert sites in rankings.

Rendering timeout

The page loaded but our headless browser couldn't render it within 20 seconds. Usually means a JavaScript bundle is loading external scripts that hang. Open the page in DevTools with Network throttling set to Slow 3G to reproduce; check the Network tab for requests that never resolve.

Invalid HTML / parse error

We got a response but couldn't parse it as HTML. Causes: page returned JSON or plain text, response was truncated, or the response body is empty. Inspect the raw response from the error panel.

Errors you can safely ignore

• A handful of timeouts on a large audit (under 1% of URLs). Network blips happen.
• 403/410 errors on URLs you intentionally removed (return 410 to tell Google they're gone).
• Errors on /wp-admin, /api/* or other authenticated paths if you didn't add credentials.

When to rerun vs investigate

Rerun if the error rate is under 5% and the errors are spread across timeouts. Investigate if a single error type dominates, if errors cluster on one path, or if you see 5xx errors on pages that load fine in a browser.