en
/login
Koval SEO

robots.txt blocks a stylesheet or script the page loads

In the reportRendering resource blocked by robots.txt

blocked_rendering_resources · Review item

Short answer

This appears when a page's HTML names a stylesheet or script on the checked origin that robots.txt forbids Googlebot to fetch. If the page needs that file to show its content, Google cannot use it when it renders the page. Allow the file, or remove the reference if the page no longer needs it.

Severity: Medium. Review it in your next round of site changes; the check does not show whether the blocked file changes what Google sees.

Why it matters

Google renders pages much as a browser does. Its introduction to robots.txt advises not to block resource files whose absence makes a page harder for Google's crawler to understand.

What to do

  1. Look at the finding: it gives the number of blocked files and lists up to ten, each with the robots.txt line that blocks it.
  2. If the page needs the file, remove or narrow that line, or add an Allow rule for the file's folder.
  3. If the file is no longer used, remove its <script> or <link> from the page instead.

When to leave it as it is: if the blocked file plays no part in what the page shows, for example a script only editors use, blocking it does no harm. The check cannot tell how much a file matters.

What we read

We read each crawled page's HTML, without running JavaScript, and collect the <script src> and <link rel="stylesheet"> it declares outside <noscript> and <template>. Only files on the same HTTP origin as the captured robots.txt policy are judged by that policy. A www. twin or another protocol or port is unobserved rather than assumed allowed; unrelated external hosts, including CDN subdomains, are outside this check. Images, fonts, preload hints and files added by scripts are not collected.

Each file's address is matched against robots.txt with Googlebot's rules, the same way the other robots.txt checks match pages. A page is reported when at least one of its files is blocked, and the finding lists up to ten of them. A robots.txt that answers 404 or another 4xx other than 429 means nothing is blocked; a network failure, 429 or server error leaves pages that declare files on your own host unchecked. If no page in the audit declares one, the check does not apply. Pages marked noindex and pages that are only a frame for scripts are read too.

Example & evidence

Illustrative example — one page and one robots.txt, not a live audit.

Page https://bakery.example/menu/ declares:

<script src="/wp-includes/js/jquery/jquery.min.js"></script>

https://bakery.example/robots.txt answers 200 with:

User-agent: *
Disallow: /wp-admin/
Disallow: /wp-includes/

The script's path starts with /wp-includes/, so line 3 blocks it for Googlebot. The finding names the page, the script's address and that line.

A possible correction: delete line 3, or add Allow: /wp-includes/js/ to the same group. The longer allow rule then wins for the script's path, and the page is no longer reported.

Confirm & check again

Check for yourself: open your robots.txt and compare the blocked file's path with its rules; the live test in Search Console's URL Inspection lists page resources Google could not load.

Check again: Full audit — run a new audit of the site. The finding can close when the page is read again as complete HTML, none of its declared stylesheets or scripts on the checked origin is blocked, and no same-site CSS or script remains on an unobserved origin; it can also close when it declares no such files. It can also close when the address now answers directly with a 200 file that is not HTML, or starts with a permanent redirect within your site, even if the target fails. A page that is now only a frame for scripts or answers with an error cannot be confirmed. An unobserved same-site resource, or an unavailable robots.txt while a same-site file is declared, prevents confirmation.

Limits & sources

The check does not run JavaScript and does not show whether a blocked file changes what Google sees. A www. or non-www. twin, another protocol or port has its own robots.txt policy; the captured policy for this origin cannot prove that those files are blocked.

Confidence: Medium because a declared file may not matter to what the page shows; the file and the blocking line themselves are read directly.

Sources

  • Google, How Google interprets the robots.txt specification — explains how Google matches a path against robots.txt rules, and that the rules apply only to the host, protocol and port of the file. Checked 25 September 2026.
  • Google, Introduction to robots.txt — advises not to block resource files whose absence makes pages harder for Google's crawler to understand. Checked 25 September 2026.

Editorial review: 29 September 2026