Repository navigation
feat(seo): noindex collections and repo hubs, drop their sitemaps - #342
Merged
Merged
Conversation
Owner decision: author profiles, collections, owner hubs and multi-Skill repository hubs are not indexed. Their sitemaps go with them.
Contributor
🤖 MERGED
GitHub merged this pull request.
Review completed. No finding above 80/100. Selected findings run after merge and open separate pull requests. |
One decision per page: a hub that renders a Skill emits no robots tag of its own.
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.
❓ Type of change
📚 Description
Owner decision: "we don't need these indexed". Author profiles, collections, owner hubs and multi-Skill repository hubs now render
noindex,follow. They stay live and linked. Theauthorsandsourcessitemaps are gone from the index and the module config.A single-Skill repository hub is the Skill's own page. It stays
index,followwhen the trending admission rule admits it, and the skills sitemap still lists it. The sitemap equals the indexable set, andX-Robots-Tagrepeats the meta, as in #322.A hub that renders a Skill emits no robots tag of its own, so the Skill page decision is the only one on single-Skill hubs.
Loose end: the
/gh/<owner>hubs were insources.xmltoo, so they go noindex with the rest. Otherwise they would be indexable and unlisted.