Repository navigation
Docs: fix live SEO for the home URL, /next, and the 404 - #298
Open
LunatiqueCoder wants to merge 5 commits into
Open
LunatiqueCoder wants to merge 5 commits into
LunatiqueCoder wants to merge 5 commits into
Conversation
The docs home canonical, sitemap, and navbar logo no longer use the trailing slash that 308s. /next pages point at themselves, allow follow, and /next redirects to getting started. The 404 page is noindex with no canonical. The example home HTML includes an h1. Co-authored-by: Ovidiu Cristescu <LunatiqueCoder@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The live demo heading needs copy approval, so this branch is only the docs home, /next, and 404 SEO fixes. Co-authored-by: Ovidiu Cristescu <LunatiqueCoder@users.noreply.github.com>
Unknown URLs were only noindex in the static 404 file. The version menu opens /next/getting-started instead of the redirect stub. Co-authored-by: Ovidiu Cristescu <LunatiqueCoder@users.noreply.github.com>
Those URLs matched the version route, so the client rendered 2.x while the server sent the catch-all 404. Head tags now stay omitted. Co-authored-by: Ovidiu Cristescu <LunatiqueCoder@users.noreply.github.com>
createUrl leaves the unslashed home path in place and prefixes baseUrl again, so both alternates pointed at a doubled path that 404s. Co-authored-by: Ovidiu Cristescu <LunatiqueCoder@users.noreply.github.com>
This branch was successfully deployed
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.
Follow-up to the merged docs URL swap. Docs-site only. The live-demo heading is a separate PR so copy can be reviewed on its own.
og:url, hreflang, sitemap entry, and the navbar logo/title link arehttps://nuclearpasta.com/react-native-draxwith no trailing slash. After hydration, client-side logo navigation, and back/forward, those tags stay on that unslashed URL. A location without the trailing slash used to make both hreflang alternateshttps://nuclearpasta.com/react-native-drax//react-native-drax.baseUrlstays/react-native-drax/./nextpages usenoindex, followand a self-referencing canonical andog:url, including after hydration. They stay out of the sitemap, and the unreleased banner and label are unchanged./react-native-drax/nextstill resolves as the redirect stub for a direct visit and sends the browser to/next/getting-started.2.x (next)entry links straight to/react-native-drax/next/getting-started. On a real doc, the menu still links to that same page in the other version.noindexon bothrobotsandgooglebot, and has no canonical,og:url, or hreflang. The static/404document is the same. Missing paths under/next(for example/next/nopeand/next/api/nope) hydrate as that same 404 page instead of the version shell, so they never emit a canonical,og:url, or hreflang. Client navigation from those URLs onto a real page does not leave the missing URL's alternates behind.