Internal Blocked Resource

What This Means

An internal resource — typically a CSS file, JavaScript file, or image — that the page depends on is blocked from crawlers. This may be via robots.txt disallow rules, authentication requirements, or server-level access controls that the crawler cannot bypass.

Why It Matters for SEO

Google renders pages using a Chromium-based renderer. When CSS or JavaScript files are blocked, the rendered version of the page that Googlebot sees differs from what users see — potentially missing layout, content, or interactive elements that load via JavaScript. Blocked CSS can cause pages to appear in raw, unstyled form; blocked JS can prevent content from loading at all.

What the Platform Checks

The platform identifies all resources referenced by the page (via link, script, img, and similar tags), checks them against robots.txt rules and HTTP access responses, and flags any internal resource that returns a blocked or forbidden response.

How to Fix It

• Review your robots.txt for Disallow rules that cover CSS, JavaScript, or image directories.
• Google specifically recommends allowing Googlebot to crawl all CSS and JS files needed to render pages correctly.
• If you need to restrict certain resources from public access, consider using signed URLs or authentication that Googlebot can bypass via its verified user-agent.
• Test with Google Search Console's URL Inspection tool which shows what Googlebot actually sees when rendering the page.