Does the Rich Results Test inspect rendered HTML?

Definition: Yes. For a URL test, the Rich Results Test's code explorer uses the rendered source code. Rendered HTML is the page representation produced after rendering, which can include changes made by JavaScript.

Key facts

• Google's Rich Results Test help says the test lists rich result types found on the page, together with errors or suggestions for the structured data.
• The help page says that you expand an individual item with an error or warning, then click its description to open the code explorer at the corresponding location. The explorer uses rendered source code.
• The test accepts JSON-LD, RDFa, and Microdata, according to the same help page.
• Google's JavaScript troubleshooting guide says the Rich Results Test can show loaded resources, JavaScript console output and exceptions, and the rendered DOM.
• For a URL test, page resources must be accessible to an anonymous user accessing the code from the internet, as the Rich Results Test help explains.

What does the explorer inspect?

The explorer is tied to the result produced by the test. Google describes the test as reporting the rich result types it found and any errors or suggestions. When an item has an error or warning, the documented route is to expand that individual item, click the description, and open the code explorer at the corresponding location. The help page names the displayed material rendered source code.

Google's JavaScript troubleshooting guide, last updated 18 December 2025, places this behavior in a wider rendering workflow. It says that the Rich Results Test can show the rendered DOM and that you can use it to check whether rendered HTML contains all the content you expect. This supports reading the explorer as a view of the rendered page state used by the test, rather than as a simple view of the initial response text.

Detected Items
  > item with an error or warning
    > error or warning description
      > code explorer

How does rendering affect the result?

Google's JavaScript SEO documentation describes three phases for JavaScript web apps: crawling, rendering, and indexing. It says that, once resources allow, a headless Chromium renders the page and executes JavaScript, and that Google uses the rendered HTML to index the page. These statements describe Google Search's rendering process; the Rich Results Test help separately identifies rendered source code as the explorer's source.

For a page that adds structured data or visible content with JavaScript, inspect the rendered view reached through the detected item. A missing item or an error may therefore require checking what the test exposed after rendering, along with the resource and console information that Google's troubleshooting guide says the test can show.

How do you locate a detected item's error?

Start in the result's detected items or detected structured data area. Google says that items found on the page, including items with warnings, errors, or parsing problems, are listed with a description of the item and its issues. Expand the relevant item to see details, then click the issue description. The code explorer opens at the corresponding location in the rendered source code.

If you test a URL, the help page also reports crawl-related checks such as the user agent used for the crawl, whether crawling is allowed by robots.txt, and whether the page could be fetched. The same page says that the default user agent is smartphone. These checks are separate from the detected item's code location, but they can explain why the test has incomplete page material to inspect.

Related terms

• Structured data
• JavaScript rendering and AI crawlers
• Rendered DOM
• JSON-LD

FAQ

Does the explorer show the original server response?

The help page identifies the explorer's source as rendered source code. Google's JavaScript documentation distinguishes the initial HTML response from the rendered HTML produced after JavaScript execution.

Can you test code without publishing a URL?

Yes. The Rich Results Test help says that you can test an arbitrary code snippet, choose Code instead of URL in the landing page, paste the code, and run the test again after modifying it.

What should you click when an item has an error?

Expand the individual item, then click the description of the error or warning. Google documents that this opens the code explorer at the corresponding location.

Sources

1. Google Search Console Help, "Rich Results Test", undated
2. Google Search Central, "Fix Search-related JavaScript problems", 18 December 2025
3. Google Search Central, "Understand the JavaScript SEO basics", undated

---

Check how a page reads to answer engines. Open the GEO score analyzer