fix(BUY-66226): drop deprecated sitemap-products-sg.xml from sitemap index + robots - #338
Open
BuyWhere wants to merge 1 commit into
Open
fix(BUY-66226): drop deprecated sitemap-products-sg.xml from sitemap index + robots#338BuyWhere wants to merge 1 commit into
BuyWhere wants to merge 1 commit into
Conversation
…index + robots SG product slug pages return 410 Gone (BUY-37747/BUY-37750) and the /sitemap-products-sg.xml route itself emits 410, but the sitemap index (sitemap.xml) and robots.txt still unconditionally listed it. That kept a permanent broken-sitemap reference alive in GSC coverage (an index pointing at a Gone sub-sitemap) — the route comment said "delete it from GSC" yet the index kept re-publishing the reference. Remove the SG entry from both the index route and robots.ts so no crawler is directed at a Gone sitemap. Part of BUY-66226 (sitemap deploy triage). The core BUY-66176 regression (100 SG URLs in sitemap-products.xml) is already fixed in prod; this clears the residual broken-index reference. Co-Authored-By: Claude <noreply@anthropic.com>
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
1 participant
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
Removes the deprecated
sitemap-products-sg.xmlentry from the sitemap index (sitemap.xml) and fromrobots.txt.Why
SG product slug pages return 410 Gone (BUY-37747/BUY-37750) and the
/sitemap-products-sg.xmlroute itself returns 410. Despite that, both the sitemap index androbots.tsstill unconditionally listed the SG sub-sitemap. The result was a permanent broken-sitemap reference in GSC coverage: the index kept pointing at a Gone sub-sitemap, so any GSC "delete" could never stick — the index re-published the reference on every regeneration.The route's own comment says "This sitemap is deprecated — delete it from GSC to avoid coverage errors." But as long as the index lists it, GSC cannot clear it. This PR removes the listing so no crawler is directed at a Gone sitemap.
Scope
src/app/sitemap.xml/route.ts— drop the SG entry from the index.src/app/robots.ts— drop the SG entry from thesitemap:array.No other behavior changes. No other code or test references the SG sitemap entry.
Context
sitemap-products.xml) is already fixed in production (verified:sitemap-products.xmlnow returns exactly 100 US URLs / 0 SG URLs, regenerated 2026-08-04T22:42Z). This PR clears the residual broken-index reference discovered while re-verifying.deploy-www/merge once the Railway deploy token (BUY-60107) is available.Verification
git diff origin/main— exactly two files, +7/-2.🤖 Generated with Claude Code