How To Quickly Fix ‘Googlebot Cannot Access CSS and JS Files’ Warning in Search Console
User-Agent: Googlebot Allow: .js Allow: .css
Google Looks at CSS and JS for Homepage and Mobile View
Google Doesn’t Care About Third Party Embedded CSS/JS Elements
In that same Google+ post, John Mueller also cleared the air surrounding third party/offsite elements, saying that the notification shouldn’t have been sent out to users for blocked CSS/JS elements that are offsite:
We’re looking for local, embedded, blocked JS & CSS. So it would be for URLs that you can “allow” in your robots.txt, not something on other people’s sites (though blocked content on other sites can cause problems too, eg, if you’re using a JS framework that’s hosted on a blocked URL).
How Many Websites Received the Blocked Elements Notification?
John Mueller stated on Twitter that Google only sent out about 18.7%, or roughly 1/5, of the number of alerts they sent out when they began including mobile usability warnings – so if you survived through the mobile usability changes and came out on the other side alive, chances are your website will rebound from this without a scratch.