feat: set noindex
header for build asset dir /_nuxt
#174
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.
π Linked issue
β Type of change
π Description
Some users may find some of their assets within the asset build directory
/_nuxt
(or the directory itself) or getting indexed by Google.For example just search google for
inurl:/_nuxt
In almost all instances this is undesirable the only exception may be images that you'd like indexed but these should be included within your
/public
directory anyway.This won't fix the indexing if users are using certain web servers which will automatically create directories for these files which is the case for some.
It's important to note that we DO NOT put this in robots.txt as it will cause issues with your pages being crawled and the module will now warn you if you do this.