\n functional. If these resources are blocked from crawling, then Googlebot can’t use them when it
\n renders those pages for Search. Google Webmaster Tools now includes a
\n Blocked Resources Report<\/a>
\n to help you find and resolve these kinds of issues.\n<\/p>\n
![](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-ba874a2f295e.png\")
<\/p>\n
\n This report starts with the names of the hosts from which your site is using blocked resources
\n such as JavaScript, CSS, and images. Clicking on the rows gives you the list of blocked resources
\n and then the pages that embed them, guiding you through the steps to diagnose and resolve how
\n we’re able to crawl and index the page’s content.\n<\/p>\n
\n An update to \n Webmaster Tools attempts to show you only the hosts that you might have influence over, so at the \n We hope this new feature makes it easier for you to spot and then unblock resources used by your
\n Fetch and Render<\/a>
\n shows how these blocked resources matter. When you request a URL be fetched and rendered, it now
\n shows screenshots rendered both as Googlebot and as a typical user. This makes it easier to
\n recognize the issues that significantly influence why your pages are seen differently by
\n Googlebot.\n<\/p>\n
\n moment, we won’t show hosts that are used by many different sites (such as popular analytics
\n services). Because it can be time-consuming (usually not for technical reasons!) to update all
\n robots.txt files, we recommend starting with the resources that make the most important visual
\n difference when blocked. Our
\n Help Center article<\/a>
\n has more information on the steps involved.\n<\/p>\n
\n website! Should you have any questions, you can drop by our
\n webmaster help forums<\/a>.\n<\/p>\n