Make certain pages always redirect to new site #6
Conversation
This file contains 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
Should fix the issue where the old getting started page ranks higher than the new one.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
I think the idea here is that if you're already on
legacy.reactjs.orgthen you should be able to navigate to the old pages.Problem is, if google is indexing legacy.reactjs.org it will index those pages too.
Maybe there's a more clever solution like using
canonicalor something, but I ain't got time to figure it out. Since all the info on these pages is out of date anyway, seems like they should just always re-direct.Alternatively, we could also just kill all indexing of legacy.reactjs.org with a
noindex?