robots.txt blocks CSS/JS needed to render
Google renders a page before it judges it, so if I block the CSS and JavaScript it needs, it sees a broken or empty version. I have watched this quietly sink pages that looked flawless in a browser.
Resource files required to render the page are disallowed.
Why it matters
Google renders pages in Chrome; if it cannot fetch the CSS/JS, it may not see content or layout, harming both classic and AI-feature visibility.
How to fix it
Allow the resource directories. Use URL Inspection’s rendered view to confirm the page renders as a user sees it.
How to find it on your site
- In Search Console URL Inspection, run a live test and open the rendered screenshot and the resources list.
- Look for resources reported as blocked by robots.txt.
- Check robots.txt for Disallow rules covering /assets, /static, /_next, /wp-includes or similar.
- Compare the rendered HTML against the source to confirm the main content appears.
Cross-reference to ranking and citation factors
Rendering quality feeds straight into content evaluation. Blocked render resources can mean Google never sees the main content, which undercuts every on-page signal.
Impact
High. Render failures can hide primary content from indexing; the AI guide stresses crawlable, renderable content. Direct.
Evidence
Google must access the same resources as the user’s browser, or it may not understand the page. Google Search Central, SEO Starter Guide; Google Search Central, Understand JavaScript SEO Basics
Sources