• About
    • History of Dallas SEO
    • SEO Expert Witness Service
  • Contact
  • Topics
    • Bing
    • Blogging
    • Branding
    • Domain Names
    • Google
    • Internet Marketing
    • Link Building
    • Local Search
    • Marketing
    • Public Relations
    • Reputation Management
    • Search Engine Marketing
    • Search Engine Optimization
    • Search Engines
    • Social Media
    • Tech
  • Advertise
  • Email Newsletter

Bill Hartzer

Bill Hartzer on Search, Marketing, Tech, and Domains.

names

Home » Google » Google Sends Warnings About Blocking CSS and JavaScript Files

Google Sends Warnings About Blocking CSS and JavaScript Files

Posted By Bill Hartzer on July 28, 2015at 1:33 pm

Google has been very aggressive about sending out warnings in Google Search Console that says that your site is blocking CSS and JavaScript files on your site. Today I received a warning message from Google regarding my site’s blocking of CSS and JavaScript files. But when I first looked at the message, I thought that I wasn’t actually blocking any .CSS or .JS files on my site. Until I looked a little bit further.

Here’s the message I received, July 28, 2015 from Google. Apparently it was so important that Google sent it via the Search Console (formerly Google Webmaster Tools) but they also sent it via email:

Google search console blocking css javascript files

Googlebot cannot access CSS and JS files on https://www.billhartzer.com/
July 28, 2015

To: Webmaster of https://www.billhartzer.com/,

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’s how to fix this issue:

Identify blocked resources

Use the “Fetch as Google” feature to identify those resources that robots.txt directives are blocking.

Fetch as Google

Update your robots.txt file

Remove the restrictions on your site’s CSS and JavaScript files from your robots.txt directives and test the changes with the Robots.txt tester. Then update your revised robots.txt file on your site and submit it to Search Console.

Test Robots.txt

Validate the fix using “Fetch as Google”

Fetch and Render your page with the “Mobile: smartphone” option selected to double-check that Googlebot for smartphones renders your content properly.

As an SEO myself, I have been fully aware that you need to make sure that you’re not blocking .CSS or JavaScript files. Typically you do this in your robots.txt file, you can find mine here: https://www.billhartzer.com/robots.txt. That’s where your robots.txt file should be, and where you should find one. If it’s not there, then you need to put one there.

And here’s my robots.txt file, where I don’t appear to be blocking any .CSS or .JS (JavaScript) files:

google search console robots.txt tester

As you can see above, there are no warnings or errors. So it appears that Google sees that I am NOT blocking any .CSS or .js files.

So, if I am not, and have not, been blocking .CSS or JavaScript files, then why is Google sending me a warning message about the fact that my site IS blocking these files? I only have two possibilities here:

1. Google has sent a false message, and they’re wrong. Well, that’s a possibility, they have been before.
2. I am, in fact, blocking a .CSS or .JS file on my site.

Looking into this further, I am blocking access to my wp-admin folder on my site, for security purposes. There in fact happens to be a common.min.js file in that wp-admin folder on the site. So, most likely that may be the culprit.

How did I find this?
Well, I went to google and did this search query: site:billhartzer.com/wp-admin/ which is a folder that I am blocking. Turns out that there IS, in fact, a .JS file there. So I am, in fact, blocking one .JS file. That’s related to a theme that I have installed, so I’ll need to update my robots.txt file so that I don’t block the wp-admin folder. Oh well. So much for security, huh?

Update
So, I went ahead and updated my robots.txt file to allow indexing of the wp-admin folder where the rogue .JS file is located. I could have actually “allowed” indexing of that file, by adding an “allow” command. But for now I’m going to see what effect it has on allowing the whole wp-admin folder to get indexed. I’m pretty confident with the security of my site, so I’m not too worried about allowing that directory to be indexed.

Also, I added the locations of my sitemap files to the robots.txt file, as well. So if you look at my site’s robots.txt file you’ll see those there as well.

Related Posts:
  • 47 TakeAways from Google's John Mueller's AMA on Reddit47 TakeAways from Google's John Mueller's AMA on Reddit
  • Bill Hartzer SEO ConsultantBill Hartzer SEO Consultant
  • 56 Takeaways from Google's Gary Illyes' AMA On Reddit56 Takeaways from Google's Gary Illyes' AMA On Reddit
  • Google Penalty Recovery Service by SEO Expert Bill HartzerGoogle Penalty Recovery Service by SEO Expert Bill Hartzer
  • Should You Hire an SEO Consultant or an SEO Agency?Should You Hire an SEO Consultant or an SEO Agency?
  • How to Create a Google Page for Your BusinessHow to Create a Google Page for Your Business

Filed Under: Google, Search Engines

About Bill Hartzer

Bill Hartzer is CEO of Hartzer Consulting, LLC, an SEO Consulting firm that includes services such as search engine optimization, technical SEO audits, domain name consulting, and online reputation management.

You May Like: Bill Hartzer’s Recent Posts

  • Results of Removing My Google My Business Listing December 2, 2019
  • Google AdSense Sunsetting iOS and Android Apps November 18, 2019
  • Network Solutions Suffers Data Breach in 2019 November 1, 2019
  • State of Search Digital Marketing Conference November 4-5, 2019 October 30, 2019
  • Google My Business Congratulates Local Biz for Getting 1 Click October 20, 2019
  • Google Indexing, Ranking Bing Search Results and Redirects October 18, 2019
  • Yahoo Groups Shutting Down December 14, 2019 October 16, 2019
  • Google My Business Bug Causes 404 Errors on Websites October 13, 2019
  • Bill’s List: Speakers to See and Meet at Pubcon Las Vegas 2019 October 5, 2019
  • Google Bulletin is Shutting Down September 25, 2019
  • How to Protect Your Google Account with Google Advanced Protection September 21, 2019
  • Sales Calls Selling Amazon Alexa Voice Search Listings September 16, 2019
  • Fake Conference Attendee Contact Lists Being Sold September 13, 2019
  • Google Says Goodbye to Old Google Search Console September 9, 2019
  • US Govt. Social Media Keyword Watch List: Don’t Use These Words on Social Media Posts September 5, 2019
  • How Expired Domain Names Are Used for PBNs, Rebuilds, and Redirects August 29, 2019
  • Do You Have the Legal Right to be Listed in Google? August 23, 2019
  • What Happened When I Removed My Google My Business Listing August 4, 2019
  • Should Google Link Out and Endorse SEOs? August 2, 2019
  • Travoom: US-Based SEOs Need Not Apply July 25, 2019

DFWSEM logo

Jim & I are the original Founders of the Dallas/Ft Worth Search Engine Marketing Association.

Bill Hartzer is a Brand Ambassador for:



Industry Friends

WTFSEO
SEO By the Sea
WordPress Website Management
Jeff Lenney

Connect With Bill Hartzer

Bill Hartzer on Twitter
Bill Hartzer on Instagram
Hartzer Consulting on Facebook
Bill Hartzer on Facebook
Bill Hartzer on YouTube


Note: All product names, logos, and brands are property of their respective owners. All company, product and service names used in this website are for identification purposes only, and are mentioned only to help my readers. All other trademarks cited herein are the property of their respective owners. Use of these names, logos, and brands does not imply endorsement.


Hartzer Consulting Technical SEO Consultants

Website, Content, and Marketing by Hartzer Consulting, LLC.
Copyright © 2019 by Bill Hartzer and Hartzer Consulting, LLC.

Disclaimer - Privacy Policy - Terms of Use