Repository navigation
Stop the Search Console audit flagging intended noindex and slash redirects - #254
Conversation
…irects Running the live audit on the 2026-11-11 coverage exports reported 280 failures, but the site was healthy. The audit wrongly flagged three cases: - Pre-live docs, /search/ and other paths that static/_headers serves with X-Robots-Tag noindex were reported as "unexpected-noindex". The audit now reads those rules from _headers and accepts the noindex, failing only if such a page is still in the sitemap. - /docs/page -> /docs/page/ was reported as "redirect-source-in-sitemap" because the slash variant of the source is the redirect target itself. - http:// URLs in "Page with redirect" were reported as "expected-redirect"; the resolver already requests the https origin, so the edge upgrade never appears in the chain. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
@codex review |
|
Codex Review: Didn't find any major issues. 🎉 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Why
The Search Console coverage exports from 2026-11-11 list "Crawled - currently not indexed" (206), "Page with redirect" (307) and "Excluded by noindex" (75). The site is healthy: every URL either serves a 200 or is noindexed on purpose, all 435 redirects take one hop to a 200 page, and none of the redirecting URLs is in the sitemap. Even so,
audit-search-console-coverage.js --mode=livereported 280 failures, which hides any real regression in the next export.The audit wrongly flagged three cases:
unexpected-noindexredirect-source-in-sitemap/docs/page->/docs/page/, the slash variant of the source is the target, which is the canonical sitemap URL.expected-redirecthttp://root. The resolver already requests the https origin, so the edge upgrade never appears in the chain.Change
static/_headers. Any path served withX-Robots-Tag: noindexcounts as intentional, so_headersstays the single source of truth. Such a page still fails if it appears in the sitemap (noindex-url-in-sitemap), and noindex on any other page is stillunexpected-noindex.http://sources are accepted under "Page with redirect".tests/search-console-coverage-audit.test.cjs.Result
Re-running the live audit on the same three exports drops the failures from 280 to 3. The 3 that remain are real:
/docs/tutorials/sync/{getting-started,handling-conflicts,offline-first-patterns}/used to redirect and have served 200 since #244.No site, build or sitemap change.
🤖 Generated with Claude Code