In short. Use Test live URL, then View tested page and the HTML tab to inspect rendered content, and distinguish the live output from indexed page data.
Definition: Rendered HTML is a page's HTML after scripts have run and modified the page. Inspecting this output shows whether expected content is present after rendering.
Key facts
- As of 17 October 2026, Google's URL Inspection documentation distinguishes indexed page data from a live test that fetches the URL in real time.
- Google's rendered-source guide identifies the HTML tab under View tested page as the rendered HTML output.
- Google's JavaScript SEO basics explains that Google uses rendered HTML to index a page.
- Google's JavaScript troubleshooting guide lists loaded resources and console exceptions among the inspection outputs.
Where is the rendered HTML?
In Search Console, the complete page URL goes into the inspection bar. Google's URL Inspection documentation requires the URL to belong to the currently opened property, the site scope selected in Search Console.
The rendered-source guide gives this route after inspection:
Test live URL > View tested page > HTML
The HTML tab contains the rendered code. The same guide explains that a browser's Show source command typically displays the original response before scripts run, while Chrome's Inspect command displays the rendered page structure.
What should be checked in the output?
The inspection should look for the content expected on the page. Google's JavaScript SEO basics describes sites whose initial HTML contains an application shell, with actual content added by JavaScript. Google executes JavaScript during rendering and then uses the resulting HTML for indexing.
A practical check is to look for the main text in that output. The same documentation specifically recommends checking rendered HTML for web components, HTML elements with internal document content. Google combines that internal content with content supplied inside the element during rendering.
When content is missing, Google's troubleshooting guide directs inspection toward loaded resources and JavaScript console exceptions. It also explains that Google's Web Rendering Service, the component that renders pages, may skip resources unrelated to essential content. The relevance of a failed resource therefore matters when diagnosing missing text.
What are the limits of this inspection?
Google's URL Inspection documentation provides screenshots only for successful live tests. A screenshot shows the visual result; the HTML tab supports inspection of the code. Indexed data represents Google's most recently indexed version, so a live test can show changes absent from that stored version.
A successful live test confirms access for indexing. Google's checks during indexing also cover conditions such as duplicate pages and page quality. The Google-selected canonical, the URL Google chooses to represent similar pages, is available in indexed data; a live test cannot predict that selection.
The JavaScript troubleshooting guide also states that rendering clears cookies and local or session storage between page loads. Content that depends on a returning browser session therefore needs particular attention during inspection.
Related terms
FAQ
Can I inspect a page outside my Search Console property?
Google's rendered-source guide offers the Rich Results Test for pages on any site. You can enter a publicly accessible URL and open View tested page, then HTML; the page must allow Google access without login or a robots.txt block.
Why is View tested page unavailable?
Google's URL Inspection documentation says this typically happens when the live test cannot reach the page. You can check the Page fetch details for the reported failure.
Can JavaScript remove a noindex instruction before Google uses it?
Google's JavaScript SEO basics says the noindex robots instruction excludes a page from indexing and can cause rendering and JavaScript execution to be skipped. The instruction can appear as:
<meta name="robots" content="noindex">
If you want indexing, the original page code should omit that instruction.
Sources
- Google Search Console Help, "URL Inspection tool", undated
- Google Search Console Help, "View the rendered source for a page", undated
- Google Search Central, "Understand the JavaScript SEO basics", 4 March 2026
- Google Search Central, "Fix Search-related JavaScript problems", 18 December 2025
Check how a page reads to answer engines. Open the GEO score analyzer