Repository navigation
fix: keep crawlers off the badge builder and badges - #18
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.
Category
Bugfix (sort of - nothing's broken, it's just wasted requests)
Overview
Crawlers follow the "Customise it in the badge builder" link on every profile and repo page, so they walk one builder URL per account and pull every badge along the way. In a 20-odd minute slice of the logs that was 40% of all requests, nearly all from Google, Ahrefs and Claude's bots, which all read robots.txt. So the builder's query-string URLs and the badge and shields endpoints are disallowed now, and the link gets
rel="nofollow".The plain builder page, the listings and the profiles stay crawlable. README badges are fetched by GitHub's image proxy and Shields, and neither looks at robots.txt, so they keep working. Google won't get the badge image when it renders a page any more, which I don't think matters for a 20px picture.
Issue Number
None