Update robots.txt to improve crawler access #323
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
|
I guess the problem is that the rule says "Google" instead of "Googlebot". The patch does unnecessary additional edits, I think, would you mind doing that small edit only? |
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.
Allow search engine visibility and ensures proper crawling behavior for Google.
Revise the robots.txt file to disallow all crawlers by default while allowing specific access for Googlebot, DuckDuckBot, and Bingbot.
Currently, searching for "Rails contributors" on Google results in:
The reason is the page is blocked by Robots.txt
Robots.txt validator shows the site is disallowed if the User Agent is Googlebot.
Changing the User-Agent order allows Google to crawl the site.