Repository navigation
docs(kb): use example.com in the locale routing URL list - #607
Closed
Kevin-Liu-01 wants to merge 1 commit into
Closed
Kevin-Liu-01 wants to merge 1 commit into
Kevin-Liu-01 wants to merge 1 commit into
Conversation
The URL list in "How do I set up SEO for a multilingual Next.js app?" used generaltranslation.com/en/about, /fr/about and /es/about. Those pages do not exist: /fr/about and /es/about return 404, and /en/about redirects to /en-US/about, which returns 404. The list now uses example.com, like the rest of the article. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
Author
|
Covered by #650 (merged): the locale routing article now uses example.com URLs. |
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.
Summary
The locale routing URL list in the KB article "How do I set up SEO for a multilingual Next.js app?" (
kb/multilingual-nextjs-seo.mdx:33-40) uses generaltranslation.com pages that do not exist as its examples of correct URLs. The rest of the article usesexample.com.Checked with
curlon 2026-10-10:https://generaltranslation.com/en/about/en-US/about, which returns 404https://generaltranslation.com/fr/abouthttps://generaltranslation.com/es/aboutThe research report flagged the three ✅ lines. The two ❌ lines in the same block use the same domain, so this branch changes them too.
Changes
kb/multilingual-nextjs-seo.mdx: all five URLs in the block useexample.com. The paths are unchanged.Size: 1 file, +5/-5.
Test plan
curlchecks above.Run on this branch (
k/docs-kb-seo-example-urlsat 3d65b1e, on origin/main f93de7c), inscripts/afternpm ci:validate-links: all links validvalidate:unsafe-htmlandvalidate:callouts: 546 MDX files each, cleanvalidate:reference-links: 500 MDX files against 301 reference symbol aliases, cleanvalidate:structure,validate:blog-orderandvalidate:kb(5 articles): cleantest: 7 scripts, 155 cases passedtypecheck: cleanjavascript:URLs in MDX finds nothing, and the changed article parses with the MDX parser the validators use.Open PRs #595 (publish dates) and #597 (the first canonical example, item 40 of the report) edit this article. Both merge cleanly with this branch (
git merge-tree).🤖 Generated with Claude Code