Google Request Access to CSS and JS Files

There has been a huge number of messages going out from Google HQ regarding Google’s inability to access the Javascript (.JS) and Cascading Style sheets (.CSS) on a domain and asking that users make the necessary changes so that they can

For me this looks a little strange, as the Robots.txt file that they are asking to be amended is only really a request, any spider (they are actually electronic robots’ could in my view look at what it likes. I don’t think it would be really possible to stop a robot from accessing these areas on a page, as if you did you would also stop a Browser and that would mean the page would not work (in most cases).

So, the real reason they are asking is a bit of a mystery to me and I am expecting some more ‘fallout’ from this request later on.

In the meantime of course, it probably just as well to make the changes requested.

Another interesting thing is that this issue seems to be only about the Mobile Web, Google’s Search Console revealing that it is all about how a site would look if it could  not access these ‘restricted’ areas, which me me makes it more to do with Google REALLY wanting to make sure that a site is indeed MOBILE FRIENDLY.

I have always thought that Google are as interested in the fact that a site takes the ‘trouble’ to make sure it can be used on mobile devices as in the fact that it can be used, this extra effort being a sign that the website in worth ranking in Google’s eyes. Just my opinion of course…

Here’s the article:-

Google Roll Out Mass of ‘Cannot Access CSS and JS’ Notices

With the announcement that Google had finally begun their rollout of the latest version of Google Panda (4.2) we knew that as soon as they noted that the changes would take ‘a couple of months’ to completely take effect, this was never going to be a notice free roll out for many and it seems that our thoughts were correct as webmasters take to the online community to share tales of receiving notice that Google can’t access everything that they would like to on your website.

The latest string of warning notices delivered in Google Webmaster Tools (Search Console) centre around Google telling site owners that they are failing to be able to completely access Javascript and CSS elements within a site, which could cause them to be unable to see valuable aspects of your website.


As with every warning notice that any website owner receives from the search engine giants, panic was seen to have broken out as site owners rushed to check their robots.txt permissions on their sites to try to get to the bottom of their problem however with many claiming that they aren’t seeing blocks that would relate to the issue, they are beginning to believe that there could have been a mistake in the fact that they received the notice, but listen up, we may be able to shed some light on that for you.

A look at the ‘Google cannot access CSS and JS files’ messages that website owners are waking up to shows that Google consider this to be ‘an issue’ and the terminology does seem to offer a fear factor for those that are unsure towards what could be causing Google to have to reach out to the owner, however if you have received one of the notices, you aren’t alone.

One thing that you should note about this notice is that Google does not deem this ‘an issue’ that would require a ranking penalisation or dampening as you would see from triggering something like the metrics that the Google Panda algorithm is designed to detect, instead they are simply saying that they have a reduced understanding of your website and that in turn could potentially mean that your site would not rank as competitively as it should, in theory. It should be pointed out that opening up your CSS and JS files would not mean that you would be given a boost in the search engine results.

Website owners that have received these notices are advised that they should be looking to make use of the Google Fetch and Render tool found within your Search Console (Webmaster Tools) platform and should be looking to ensure that what Google sees from the image rendered is the same as what is being shown to the user and to check your robots.txt file for the potential block that could be in place.

For the full detail blog please see