New “Googlebot cannot access CSS and JS files” in Google Search Console

Google Search Console has begun sending out a brand new warning to webmasters who are blocking CSS and JavaScript on their websites.

The new warning, also referred to as [WNC-658001] is send by both email and as an alert in Google Search Console for affected websites.

Googlebot cannot access CSS and JS files on _____

Google systems have recently detected an issue with your homepage that affects how well our algorithms render and index your content. Specifically, Googlebot cannot access your JavaScript and/or CSS files because of restrictions in your robots.txt file. These files help Google understand that your website works properly so blocking access to these assets can result in suboptimal rankings.

Here is a copy of the notice in Google Search Console.

The warning also states emphatically that blocking Javascript and/or CSS “can result in suboptimal rankings.”  While Google has been making it known that they must be unblocked as part of the mobile friendly algo, they did also make the changes to the Google technical guidelines advising that it can hurt all rankings last year.

If you need to know which resources are blocked, here is how to find them.

The blocked resources also show up in the “Blocked Resources” section under “Google Index” in Google Search Console.  However, Michael Gray tweeted that he was getting the notice for resources that were not blocked.

The message also outlines details of how to fix the issue, likely to help those who have no idea what it means to block those resources and do not realize it is causing an issue.

Google has been increasing the number of messages they send to webmasters, alerting them to site issues that could negatively impact their rankings.

I have asked to see if there is information on how many webmasters received this warning, and will update if more becomes known.

Added: It looks like many are getting warnings from having “Disallow: /wp-content/plugins/” which can be blocked with some WordPress setups.  If you use Yoast SEO, you can find the robots.txt in its new location here: SEO / Tools / Files.

Some are getting alerts for 3rd party resources that are blocked, however, Google has previously said 3rd party resources are not an issue since webmasters since they are generally outside of the webmaster’s control.

You can also follow us @Jenstar and @TheSEMPost as we most more updates.

Update 12:30pm PST: Some people weren’t aware there is a much easier way to find blocked resources than the “Fetch as Google” option for every page that Google suggests doing.  Do double check, as some people who are reporting false positives actually discover they did have some resources blocked that they weren’t aware of.  How to Find Blocked CSS & Javascript in Google Search Console.

The following two tabs change content below.

• Bio
• Latest Posts

Jennifer Slegg

Founder & Editor at The SEM Post

Jennifer Slegg is a longtime speaker and expert in search engine marketing, working in the industry for almost 20 years. When she isn't sitting at her desk writing and working, she can be found grabbing a latte at her local Starbucks or planning her next trip to Disneyland.She regularly speaks at Pubcon, SMX, State of Search, Brighton SEO and more, and has been presenting at conferences for over a decade.

Latest posts by Jennifer Slegg (see all)

• Google Adds Autoplay Video Preview Clips to Search Results - August 21, 2017
• Cloudflare Credentials Stolen in Web Developer Chrome Extension Hack - August 18, 2017
• Google Search Console Sends Security Warning Notices for HTTP Sites - August 18, 2017
• Bing Testing Blended Local Mini One Pack in Search Results - August 15, 2017
• Google Still Ignores Last-Modified Meta Tag - August 11, 2017