chore(robots): disallow NLB crawler from parsing beyond the application bundle #1134
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
liangyuanruo
requested changes
Jan 19, 2021
There was a problem hiding this comment.
Since Go is a React single-page app, disallowing bundle.js effectively means that the crawler is blind and can't even see the landing page at all. Is this what we want?
How about if we only allow loading the landing page, but disallow all other server routes, including /api and redirect endpoints?
From what I can see loading Go in Chrome Devtools, this should work:
user-agent: <NLB crawler>
allow: /
allow: /bundle.js$
allow: /css2
allow: /assets/*
allow: /s/*.woff2$
disallow: *
liangyuanruo
approved these changes
Jan 19, 2021
liangyuanruo
changed the title
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.
Keep crawlers away from bundle.js as there are no real links in here