What it is
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. Server returns inconsistent codes under load.
Why does intermittent status codes matter for AI search?
Flaky 5xx during crawl can drop pages.
How do you fix it?
Stabilise infrastructure; load-test.
How do you 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.
Which ranking and citation factors does it touch?
Flaky status codes can cause Google to drop or distrust URLs intermittently, which is upstream of stable ranking.
What is the impact?
Medium-high. Inferred.
What is the 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
Frequently asked questions about intermittent status codes
What does "Intermittent status codes" mean?
Server returns inconsistent codes under load.
How do you fix intermittent status codes?
Stabilise infrastructure; load-test.