-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Removed Disallow: /cache/ #6940
Conversation
This PR is to fix # 6939 I removed "Disallow: /cache/" so that Google will be able to index CSS & JS files stored in /cache/
@test |
well, this is controversial issue, as Joomla store css/js under I just can say, if you worried about Google, then you can use "Allow: /cache/blablabla" in your site installation .... it not really standard but Google allow this |
My concern with removing the cache folder is it is used by devs for more than web assets. I know my own extensions and some Akeeba products store data there that Google shouldn't be indexing. |
I have a yootheme template and the minify and gzip compresion store the files inside the cache folder... Because of that Google penalize the page... Is a mistake of the template use this folder? Could be a problem remove the disallow cache folder? |
It isn't an issue that developers use the cache folder for stuff, it's Joomla's system-wide cache folder. The only concern is the added emphasis on mobile readiness and for Google that means being able to index all web assets. If the cache folder only stored that kind of stuff, there'd be no issue removing it from the disallow list. But, the folder is used for more than that. HTML files get written here with cached output when Joomla's system cache is enabled and extensions cache data here (be it update information, cached data from external services, or web assets). So it isn't a folder that we should completely allow search engines to index. I'd be concerned if Google were to start indexing site cache folders and exposing that cached data that shouldn't be directly accessed, which is why I'm making these comments. Removing the disallow on the cache folder isn't as clear of a decision IMO as removing it on the images, media, or templates folders. |
@Casporro I would suggest add
I also use such thing on my sites 😄 |
Thank you @Fedik |
I really dont agree with this On 14 May 2015 at 14:59, Casporro notifications@github.com wrote:
Brian Teeman |
@brianteeman And what do you propose to Google not penalize you in these cases? |
You edit the robots file. Problem solved. On 14 May 2015 at 19:51, Casporro notifications@github.com wrote:
Brian Teeman |
@brianteeman I don't agree with remove Disallow: /cache/ too, but I think it could be at least a warning or an easier solution from the administration panel. |
Setting to needs review so the CMS maintainers can make a decision. This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6940. |
Based on the various comments I'm rejecting this PR. |
This PR is to fix #6939
I removed "Disallow: /cache/" so that Google will be able to index CSS & JS files stored in /cache/