Blocked resources are CSS, JavaScript, image, and other files that a crawler is not allowed to fetch while rendering a page, usually because of a Disallow rule in robots.txt. This entry covers the SEO meaning. The search results for the phrase mostly show ad blockers, network filters, and malware warnings, which are a different topic.
Why do blocked resources matter for SEO?
Google renders pages and indexes the rendered HTML. According to Google, Search “won’t render JavaScript from blocked files or on blocked pages.” If content or links depend on such a script, they can be missing from the rendered page. Blocked stylesheets can change how Google sees the layout.
Google’s robots.txt FAQ allows blocking unimportant image, script, or style files if the page isn’t significantly affected without them. If the missing files make it harder for Google’s crawler to understand the page, Google advises against blocking them.
Render-blocking resources are a separate performance topic. They are files that delay how quickly a page is displayed.
Example
This robots.txt blocks all scripts and stylesheets under /assets/ for Googlebot:
User-agent: Googlebot
Disallow: /assets/js/
Disallow: /assets/css/
Removing the Disallow lines, or releasing the files the page needs with Allow, fixes it.
How can you find blocked resources?
The live test in the URL Inspection tool of Search Console lists the page resources that were loaded and shows a screenshot of the rendered page. Google’s help page notes that differences between the screenshot and your browser can result from resources blocked for the inspection tool.
Sources
- Robots.txt FAQ – Google Search Centraldevelopers.google.com
- Understand JavaScript SEO basics – Google Search Centraldevelopers.google.com
- URL Inspection tool – Search Console Helpsupport.google.com
Last updated: