1.6 HTTPS / security / infrastructureHighInferred
Intermittent status codes
A server that returns inconsistent codes, a 200 sometimes and a 500 or 503 other times, confuses crawlers and erodes trust in the URL. Intermittent failures are the hardest to catch and the most damaging.
What it is
Server returns inconsistent codes under load.
Why it matters
Flaky 5xx during crawl can drop pages.
How to fix it
Stabilise infrastructure; load-test.
How to find it on your site
- Hit key URLs repeatedly with curl, including under some load, and watch for varying codes.
- Check server and CDN logs for sporadic 5xx responses.
- Check the Search Console Pages report for crawl anomalies over time.
- Fix the capacity or configuration issue causing the inconsistency.
Cross-reference to ranking and citation factors
Flaky status codes can cause Google to drop or distrust URLs intermittently, which is upstream of stable ranking.
Impact
Medium-high. Inferred.
Evidence
Stable correct status codes matter for crawl. Google Search Central, How HTTP status codes affect Google Search; Google Search Central, Large site owner’s guide to managing crawl budget
Sources