-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugins CSS and JS excluded from robots.txt #2006
Comments
This would probably belong best in the learn documentation. I don't think it should be Grav Core providing this very specific and opinionated behavior. Do you think the best behavior in general is to let google crawl CSS and JS? |
I don't have any strong opinions about this, and I haven't used Grav long enough to comment on the philosophical choices. That being said, I only use official Team Grav plug-ins at the moment, some of which ship with Grav out of the box. As a user, I would expect there not to be any issues. I think it should just work out of the box (like it does for pretty much everything else). I could see this being a user configurable option in the Admin panel for those who want to hide CSS and JS from web crawlers for whatever reason. |
What are the warnings you are seeing? Also how are you checking these? |
In my particular case, search engines fail to fetch the following files:
Regardless of whether or not they should be trying to fetch these in the first place, it seems to me a bit of an inconsistency in Grav, since CSS and JS files in Themes are not excluded by default. |
That's fair @gmpreussner , I personally wasn't even aware of these warnings for assets. We'll look into it, thanks! |
Awesome, thanks! |
Just to add, there are also compiled css files in |
See also #3067 |
Fixed by bc22c8d |
Some search engine crawlers, such as Google throw low severity warnings, because plug-in .css and .js files are excluded from robots.txt. I added the following to resolve the warnings:
The text was updated successfully, but these errors were encountered: