- Class
- C1 Mechanism
- Weight
- 8
- Severity on fail
- critical
- Applies to
Test this rule on a live site with the XML sitemap checker, the noindex checker or the redirect checker. Free, no account needed.
Scope and evidence
Evaluated on each member of I. The book marks this requirement ELIGIBILITY REQUIREMENT, SEARCH-ENGINE-SPECIFIC, and the scanner treats it as a gate: indexing rule: a failure on an intended page removes that page from the eligible set instead of entering the achieved share.
Hops and loops follow §3.12. {via_clause} is empty for a direct response, or " (reached via {hops} redirects from {original})". {chain_problem} is "the redirect chain loops" or "the redirect chain exceeds 10 hops".
Fail conditions
Each condition has a stable code and a reason template. The evaluator fills the placeholders from observed values only; no sentence in a report is generated.
client_error{url}{via_clause} returned {status}. Google only indexes pages served with HTTP 200, does not index URLs that return a 4xx status code, and removes already indexed URLs that start returning one.
server_error{url}{via_clause} returned {status}. Google treats 5xx and 429 responses as server errors: its crawlers slow down, and already indexed URLs are preserved for a time but eventually dropped.
no_response{url} could not be fetched ({error}). Google only indexes pages served with HTTP 200.
unresolved_redirect{url} never reaches a final response ({chain_problem}). Google's crawlers follow up to 10 redirect hops, and Google only indexes pages served with HTTP 200.
The documented fix
Serve every URL you want indexed with a 200 at its final address. If the URL is gone on purpose, remove it from sitemaps and internal links; if it moved, redirect it permanently and list the destination instead.
Sources, quoted
These are the passages the rule rests on, stored once in the knowledge base and emitted exactly as written. A citation marked for specific conditions appears only on findings with those codes.
“Google only indexes pages that are served with an HTTP 200 (success) status code.”
[G-TECH] Google Search technical requirements · The page works · last updated 2025-12-18
https://developers.google.com/search/docs/essentials/technical“Google doesn't index URLs that return a 4xx status code, and URLs that are already indexed and return a 4xx status code are removed from the index.”
[G-HTTP] How HTTP status codes, and network and DNS errors affect Google Search · 4xx (client errors) · last updated 2026-02-04 · for client_error
https://developers.google.com/crawling/docs/troubleshooting/http-status-codes“5xx and 429 server errors prompt Google's crawlers to temporarily slow down with crawling. For Google Search, already indexed URLs are preserved in the index, but eventually dropped.”
[G-HTTP] How HTTP status codes, and network and DNS errors affect Google Search · 5xx (server errors) · last updated 2026-02-04 · for server_error
https://developers.google.com/crawling/docs/troubleshooting/http-status-codes“By default, Google's crawlers follow up to 10 redirect hops.”
[G-HTTP] How HTTP status codes, and network and DNS errors affect Google Search · 3xx (redirection) · last updated 2026-02-04 · for unresolved_redirect
https://developers.google.com/crawling/docs/troubleshooting/http-status-codes