Exclude /dart/ from crawling
#475
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
Contributor
Author
|
@alexander-yevsyukov PTAL. |
Contributor
Author
|
See #476 for the issue on re-enabling. |
…as we now have an explicit `Disallow: /dart/`.
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.
Previously, there were several thousand
404responses detected by Google Search Console review process, the majority of which were related to the generated documentation for Spine Dart client.Attempts to address the problem, or at least, locate its roots failed. Seems like some previously crawled pages are still in Google Search cache, but now (as of
1.9.0release) they are missing.Therefore, within this PR, the whole
/dart/subtree is excluded from crawling altogether. Hopefully, it will enforce the cache cleanup.In some future, we may re-enable the crawling for this part of the site. Most likely, it will make sense to do together with 2.0.0 release.