add http headers to help search engines index the docs #3264
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
davidhewitt
force-pushed
the
no-index
branch
6 times, most recently
from
e03a727 to
b991ea6
Compare
davidhewitt
force-pushed
the
no-index
branch
3 times, most recently
from
36b2b0e to
457e9c3
Compare
|
On the deploy preview I see the Link header coming through as expected, so I think this is good to merge. |
adamreichold
approved these changes
Jun 22, 2023
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.
Quite often we have users linking to old versions of the guide.
I became aware today that we can set HTTP headers to encourage search engines to prefer our latest version of the docs. So here's an experiment in doing so.