Repository navigation
fix(seo): align Ingress FAQ sitemap and Chinese listing redirects - #2135
Merged
Yilialinn merged 1 commit intoOct 12, 2026
Merged
Conversation
kayx23
approved these changes
Oct 12, 2026
bzp2010
approved these changes
Oct 12, 2026
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
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.
Task
Classify Remaining Indexing Residuals (P1).
Problem
index.htmlmatched the retired-article redirect and sent visitors to the English listing.Changes
index.htmlfrom the retired article redirect; article slugs still go to their English counterparts.Validation
npm run test:sitemap;npm run test:redirects;git diff --check./zh/learning-center/and/zh/learning-center/index.htmlreturn 200; a retired Chinese article route returns 301.Post-deploy check
Confirm both FAQ aliases are absent from sitemaps, the Chinese listing returns 200, and retired article URLs remain 301.
No canonical ownership change, including the existing API7 plugin documentation strategy.