Blocked CSS and JavaScript: Why Your Page Looks Broken to AI

To do that they need the files the page depends on: stylesheets, scripts, sometimes fonts and images.

If your robots.txt blocks the folders those files live in, the crawler gets the page and nothing else. It builds what it can from the pieces it's allowed to load, and ends up with a version of your site that nobody has ever seen.

This is a quiet problem, because the page itself isn't blocked. It opens fine. The damage is to what the crawler concludes about it: text that should be visible looks hidden, layout collapses, sections that load on demand never appear.

The usual cause is a single broad rule written years ago for a sensible reason. Someone blocked a whole directory to keep uploads or plugin folders out of search results, and your stylesheets happened to live inside it.

Google's guidance on this is direct: don't block resources that the page needs in order to render, or it can't be processed properly. The JavaScript SEO basics documentation covers it.

1. Open yoursite.com/robots.txt and look at every Disallow line.

2. Flag anything that could contain design or script files. On WordPress the classic offender is:

That single line blocks your themes, your plugins and your uploaded images all at once. Other common ones name /assets/, /css/, /js/, /static/ or /includes/.

3. Remove the rules that cover those folders. There's rarely a good reason to block them. If you were trying to keep specific files out of results, block those files rather than the folder they share with everything else.

4. Keep blocking what should be blocked. Admin areas, checkout, account pages and search result pages are all reasonable. The rule of thumb: block pages you don't want visited, not the files your pages are built from.

5. Check the result. Google Search Console has a URL inspection tool that shows you the page as Google rendered it, including which resources it couldn't load. It's free, and it's the clearest view you can get of this particular problem.

Some security plugins and hosting panels rewrite robots.txt on their own schedule. If a Disallow line reappears after you delete it, it's being injected rather than stored. Check your security plugins and your hosting control panel, or ask your host directly.