Unexpected noindex directive found on a fetched HTML page
ShipReady found a noindex directive in a fetched HTML page or its X-Robots-Tag response header, on a route its classifier does not treat as an expected noindex surface.
Why it matters
Noindex is an explicit instruction for search engines. An unexpected directive on a public page is worth reviewing, while a technical observation of the directive does not itself show when or whether a search engine changed its index.
How ShipReady detects it
What it inspects
ShipReady inspects a successfully fetched, readable, content-serving HTML document and its response headers. HTML can be recognised by Content-Type or by document structure in the body.
It checks X-Robots-Tag and robots or googlebot meta tags, in either supported attribute order, for the text noindex.
What triggers a finding
The rule triggers when a supported noindex source is found and ShipReady's route classifier does not label the fetched URL as Sign-in, Sign-up, or App route.
What the evidence shows
The fetched document or response header contained a supported noindex signal on a route outside ShipReady's expected-noindex classifier.
Limits of this check
ShipReady does not query search engines, submit URLs, inspect every route, determine an intended business audience, or establish current indexing, ranking, traffic, or deindexing timing. Its route classifier is deliberately limited and does not replace a review of whether the page should appear in search.
How to fix it
Confirm whether the page should be searchable
Review the affected page's intended audience before changing any directive. Some sign-in, app, preview, and internal surfaces may correctly remain out of search.
Adjust the intended source of the directive
If the page should be indexable, update the relevant meta tag, X-Robots-Tag configuration, or deployment setting and verify related production routes.
How to verify the change
Inspect the deployed page and headers
Request the affected deployed URL and inspect its final HTML and X-Robots-Tag header after the intended change.
Expected: The page has the intentional indexing directive for its audience.