I just got hit with a bunch of messages regarding my clients' websites that Google Bot can't access the CSS and JS files. Now this has never been an issue before and they do have a "fix" for me to follow (changes to the robots.txt file), but before I do so has anyone else got such messages? And are they legit? Please advise. Thanks! Doreen
I deleted my robot.txt file and renamed the robot.txt.dist to replace it. (This needs to be done manually, the Joomla update only adds the .dist file) This helped with some of the blocks, but I still have some remaining that relate to Rokbox,RokNavMenu & Gantry. See attached screen shot.
This comment after the article seemed to make the most sense. Does anyone know about this?
"As I understand the issue, Google only has a problem with blocked CSS/JS if this negatively impacts the rendering of the page on mobile. It would be good if they clarify this in the email they are sending. It would prevent us banging our heads against internal teams who have chosen to block certain files, i.e. for legal reasons."
I do see in the Rockettheme Joomlas sites that the Template folder is disallowed in the robots.txt file and that folder does contain the CSS and JS files. However, I don't want to change that if it's not necessary - especially if Rockttheme has a good reason for doing that.
Any insight from Rockettheme on this would be appreciated.
Last Edit: 9 years 9 months ago by Deb Williams. Reason: typo
Deb - If you change the robot.txt file it will take care of that part. One of the last Joomla 3 updates adds a file called robot.txt.dist I'm not sure why, but you need to manually replace robot.txt file with that one.
If I understand this it doesn't really have much to do with the updated robots.txt file distributed by Joomla. I think there's only a one line difference between old and new. It's more to do with the extensions you use and Google. They now want to validate sites for responsiveness and mobile features. Specifically, they want to get into extensions directories they didn't want to in the past.