Stay organized with collections
Save and categorize content based on your preferences.
Wednesday, March 11, 2015
Webmasters often use linked images, CSS, and JavaScript files in web pages to make them pretty and
functional. If these resources are blocked from crawling, then Googlebot can't use them when it
renders those pages for Search. Google Webmaster Tools now includes a
Blocked Resources Report
to help you find and resolve these kinds of issues.
This report starts with the names of the hosts from which your site is using blocked resources
such as JavaScript, CSS, and images. Clicking on the rows gives you the list of blocked resources
and then the pages that embed them, guiding you through the steps to diagnose and resolve how
we're able to crawl and index the page's content.
An update to
Fetch and Render
shows how these blocked resources matter. When you request a URL be fetched and rendered, it now
shows screenshots rendered both as Googlebot and as a typical user. This makes it easier to
recognize the issues that significantly influence why your pages are seen differently by
Googlebot.
Webmaster Tools attempts to show you only the hosts that you might have influence over, so at the
moment, we won't show hosts that are used by many different sites (such as popular analytics
services). Because it can be time-consuming (usually not for technical reasons!) to update all
robots.txt files, we recommend starting with the resources that make the most important visual
difference when blocked. Our
Help Center article
has more information on the steps involved.
We hope this new feature makes it easier for you to spot and then unblock resources used by your
website! Should you have any questions, you can drop by our
webmaster help forums.
Posted by
John Mueller, Webmaster
Trends Analyst, Google Switzerland
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eGoogle Webmaster Tools now includes a Blocked Resources Report to help webmasters find and resolve issues with blocked resources like images, CSS, and JavaScript that prevent Googlebot from fully rendering web pages.\u003c/p\u003e\n"],["\u003cp\u003eThe report identifies hosts with blocked resources, lists the specific resources, and shows the pages embedding them, guiding webmasters through diagnosis and resolution.\u003c/p\u003e\n"],["\u003cp\u003eAn updated Fetch and Render tool shows screenshots of pages rendered both as Googlebot and a typical user, highlighting differences caused by blocked resources and their impact on indexing.\u003c/p\u003e\n"],["\u003cp\u003eWebmasters are advised to prioritize unblocking resources that create significant visual differences when blocked, focusing on hosts they can control.\u003c/p\u003e\n"]]],["Google Webmaster Tools introduced the Blocked Resources Report to identify issues where JavaScript, CSS, and images are blocked from crawling. The report lists hosts with blocked resources, then the specific resources and the pages embedding them. The Fetch and Render update now shows screenshots of how Googlebot and users see a page, highlighting the impact of blocked resources. Prioritization of unblocking is recommended, starting with the most visually impactful. Additional information is available in the Help Center article.\n"],null,["# Unblocking resources with Webmaster Tools\n\nWednesday, March 11, 2015\n\n\nWebmasters often use linked images, CSS, and JavaScript files in web pages to make them pretty and\nfunctional. If these resources are blocked from crawling, then Googlebot can't use them when it\nrenders those pages for Search. Google Webmaster Tools now includes a\n[Blocked Resources Report](https://support.google.com/webmasters/answer/6153277)\nto help you find and resolve these kinds of issues.\n\n\nThis report starts with the names of the hosts from which your site is using blocked resources\nsuch as JavaScript, CSS, and images. Clicking on the rows gives you the list of blocked resources\nand then the pages that embed them, guiding you through the steps to diagnose and resolve how\nwe're able to crawl and index the page's content.\n\n\nAn update to\n[Fetch and Render](https://support.google.com/webmasters/answer/6066467)\nshows how these blocked resources matter. When you request a URL be fetched and rendered, it now\nshows screenshots rendered both as Googlebot and as a typical user. This makes it easier to\nrecognize the issues that significantly influence why your pages are seen differently by\nGooglebot.\n\n\nWebmaster Tools attempts to show you only the hosts that you might have influence over, so at the\nmoment, we won't show hosts that are used by many different sites (such as popular analytics\nservices). Because it can be time-consuming (usually not for technical reasons!) to update all\nrobots.txt files, we recommend starting with the resources that make the most important visual\ndifference when blocked. Our\n[Help Center article](https://support.google.com/webmasters/answer/6153277)\nhas more information on the steps involved.\n\n\nWe hope this new feature makes it easier for you to spot and then unblock resources used by your\nwebsite! Should you have any questions, you can drop by our\n[webmaster help forums](https://support.google.com/webmasters/go/community).\n\n\nPosted by\n[John Mueller](https://twitter.com/johnmu?rel=arthur), Webmaster\nTrends Analyst, Google Switzerland"]]
