Repository navigation
fix: discourage crawlers from following Discord invites - #307
Merged
Merged
Conversation
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.
What Problem This Solves
Official Discord invitation links should tell crawlers not to follow the invite redirect.
User Impact
Links keep their existing destinations, source tags, appearance and analytics behavior.
nofollowis a crawler hint, not an access restriction.Why This Change Was Made
Add
nofollowto the docs shell and canonical article renderer, including localized and cached articles, while preserving existingreltokens. Generated translations, code examples and unrelated links remain unchanged.Evidence
reltokens and third-party negatives.Merge is held until the coordinated before/after measurement boundary is recorded.