When checking webpage rendering results, compare the rendered view, blocked resources, and indexability of the same URL. First see whether the page loads correctly, then identify which resources cannot be retrieved and whether they relate to any missing content. A blocked resource does not necessarily mean the page failed to render. If the page looks wrong, the blocked-resource list alone cannot establish why. The interface instructions below are based on Screaming Frog’s 2016 documentation for version 7.0; the current version may work differently.
Start by comparing the rendered view with the blocked-resource list for each page
Screaming Frog’s version 7.0 announcement explains that, after crawling a site in JavaScript rendering mode, you can select a URL in the upper list to display a “Rendered Page” tab below. This tab shows a screenshot of the rendered page alongside its blocked resources, making page-by-page comparisons easier.
- First inspect the rendered view: does the content you want to check appear, and does the page load correctly?
- Then check the list: which resources are blocked on that page, and do they relate to content that is not displayed?
- To review multiple pages, that version let you check “Response Codes > Blocked Resource” and export affected pages and resources in bulk through “Bulk Export > Response Codes > Blocked Resource Inlinks”.
Version 7.0 also let you adjust the AJAX timeout, viewport size, and user agent to test different scenarios, including simulating Googlebot Smartphone. These are only test scenarios within the tool; the rendering results do not directly establish how Google actually processes a page.
To assess the connection, check whether the page loads correctly without the resources
A 2026 Search Engine Journal report quotes John Mueller explaining what happens when embedded content is blocked by the robots.txt file on the site hosting it. Googlebot follows that rule, so it will not fetch the content and cannot use it during rendering. Beyond checking whether anything is blocked, you therefore need to ask whether the page still loads correctly when those URLs are not fetched.
The example in the report involved an age-verification pop-up loaded from an external domain. Mueller said that situations like the one described would generally not be a problem. That assessment applies under specific conditions; it does not mean that all JavaScript, CSS, or resources for main content can safely be blocked. Comparing the rendered view with the resource list can reveal possible connections to investigate. But a rendering problem and blocked resources appearing together are not enough to establish causation.
Beyond rendering, check the URLs themselves
A 2021 Screaming Frog article also notes that some single-page applications update content dynamically without generating distinct URLs that can be accessed individually. You should therefore also crawl the site to confirm whether URLs intended for indexing can be found and record whether they are indexable.
The article’s checklist includes blocked resources, noindex, nofollow, canonicals pointing to other URLs, page-level redirects, and fragment URLs. Check these items separately rather than treating them all as consequences of blocked resources. Also, do not treat nofollow as having the same effect as noindex.
Inspecting webpage rendering and blocked resources: perspectives from across the web
What is the value of inspecting rendered pages in a test environment?
Inspecting rendered pages in a test environment can help you analyze what search engine bots might see. Screaming Frog’s 2016 article noted that this was particularly useful when Search Console’s Fetch & Render could not be relied on in a test environment at the time. However, the tool shows results under test conditions; it does not directly establish what a search engine actually sees.
Has blocking important resources ever affected search rankings?
Some sites temporarily lost rankings after continuing to block important resources. Search Engine Journal notes that this happened after Google began rendering webpages and asking sites to allow downloads of the resources users would see. However, this does not mean that blocking resources always causes rankings to drop. A ranking change alone also cannot establish that blocked resources were the cause.
References
- Google Says It’s Okay To Block Some JavaScript Resources With Robots.txtwww.searchenginejournal.com · 2026-11-03T11:16:50+00:00 — Discusses: Has blocking important resources ever affected search rankings?
- Conducting an SEO Content Audit: 6 Things You Might Be Overlookingwww.screamingfrog.co.uk · 2021-11-15T13:37:48+00:00 — Source used in the article above.
- Screaming Frog SEO Spider Update – Version 7.0www.screamingfrog.co.uk · 2016-12-12T10:38:50+00:00 — Discusses: What is the value of inspecting rendered pages in a test environment?



