Crawler-facing error budgets
An error budget defines how much failure and latency a crawl surface can tolerate before measurements or discovery become unreliable.
How it works
Status errors, timeouts, stale imports, and high tail latency reduce effective coverage even when the average request succeeds.
How to validate it
Report valid sample counts, error rate, p50 and p95 latency, newest observation age, and missing-field completeness per source class.
Common failure
Displaying zero when no latency sample exists makes an unmeasured system look perfectly fast.
Machine-readable editions
The same article is available as Markdown and JSON. These alternates are linked here but are not submitted through the sitemap or IndexNow.