fix(seo): stop Googlebot spending crawl budget on noindex query URLs - #28
Draft
stvlynn wants to merge 1 commit into
Draft
fix(seo): stop Googlebot spending crawl budget on noindex query URLs#28stvlynn wants to merge 1 commit into
stvlynn wants to merge 1 commit into
Conversation
The Pages coverage export showed Google fetching ~100k noindex query-string URLs and saturating the origin. Disallow those views and .md aliases for the generic crawler, tag markdown as noindex, cache social cards for a day, and return 503 on uncaught origin failures. Co-authored-by: Steven Lynn <stvlynn@users.noreply.github.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
dsh-fish | 84f38be | Aug 27 2026, 07:33 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What the coverage export showed
The 27 August Search Console Pages export is not code coverage. It is the index inventory for
dsh.fish.noindexThe sitemap offers ~36k URLs (5,985 artifacts × 6 locales +
pages.xml). GSC knew ~121k. Production/ja/a/…is stillindex, follow(SEO_LOCALE_GATING=false), so the 103knoindexrows are the query-string views (/browse?q=,?offset=,?profile=) that already emitnoindex, followin HTML.rel="nofollow"on keyword chips was not enough — Google still fetched them, confirmednoindex, and saturated D1/Worker (the 1,306 5xx). The leftover sitemap URLs sat in “discovered / crawled, not indexed”.Fix
Generic crawler (
User-agent: *, Googlebot):Disallow: /*?— query-string views. Plugin rows past listing page one stay in the artifact sitemap.Disallow: /*.md$— agent markdown aliases. Retrieval bots keepAllow: /in their own group.Also:
X-Robots-Tag: noindex, followon markdown responsesRetry-AfterDocs:
docs/seo/search-console.mdrecords this export;crawling.md/indexation.mddescribe the new robots rules.Operator follow-up (after deploy)
noindexset (should move toward “Blocked by robots.txt”)./,/browse,/docs, and/ko/a/dsh-better-edit.SEO_LOCALE_GATINGoff until the Korean CTR test from the first export has another crawl.