In short. The rendered DOM is the browser's current page structure, which JavaScript can change after the server returns HTML.
Definition: The rendered DOM is the document object model, the browser's tree of page elements, in its current state after HTML parsing and any JavaScript changes. Response HTML is the document returned by the server; scripts can add, remove or change content in the DOM.
Key facts
- As of October 2026, Google's JavaScript SEO documentation describes separate crawling, rendering and indexing phases, with rendered HTML used for indexing.
- Chrome's DOM documentation distinguishes initial HTML from the active page content represented by the DOM.
- Google's JavaScript troubleshooting guide identifies the Rich Results Test and URL Inspection tool as ways to inspect the rendered DOM and JavaScript errors.
- Search Console's URL Inspection help distinguishes information about the indexed page from a live test of the current page.
How does response HTML become a rendered DOM?
Chrome's HTML versus the DOM explanation describes how a browser parses the server's HTML into a tree of objects called nodes. JavaScript can then modify those nodes. The DOM therefore represents the page state at the time of inspection.
The documentation gives this script as an example:
const h1 = document.querySelector('h1');
h1.parentElement.removeChild(h1);
const p = document.createElement('p');
p.textContent = 'Wildcard!';
document.body.appendChild(p);
The script removes the heading and adds a paragraph containing “Wildcard!”. The initial HTML still contains the original heading. This example shows why reading the server response alone can give a different account of page content from inspecting the DOM after scripts run.
Why does the difference matter for crawling?
Google's JavaScript SEO basics describes an app shell, an initial HTML document that lacks the actual page content. Google needs to execute JavaScript to access that content. Googlebot, Google's search crawler, extracts links from the response and again from the rendered HTML, which Google also uses for indexing.
Server-side rendering supplies page content in the HTTP response. The same documentation recommends server-side rendering or pre-rendering and notes that some bots cannot run JavaScript. That distinction matters when assessing which content a crawler can access.
Google's troubleshooting guide explains another source of differences: its Web Rendering Service, the component that renders pages, clears cookies and browser storage across page loads. Content that depends on a previously stored state therefore needs particular attention during rendering checks.
How can the two versions be checked?
Chrome's DOM tutorial places the current DOM tree in the DevTools Elements panel. Searching that tree for a specific sentence helps locate the corresponding node after JavaScript changes.
For Google's view, the JavaScript troubleshooting guide recommends the Rich Results Test or URL Inspection tool. These expose the rendered DOM, loaded resources and JavaScript console output. Comparing the expected content with that output helps identify rendering problems.
The URL Inspection help describes the live-test path: Test live URL, then View tested page. Its additional information includes page code, loaded resources and JavaScript console output. The Screenshot tab shows the page as Google-InspectionTool sees it after a successful live test. The indexed report concerns the previously indexed version, so a live test is useful after a change.
Related terms
- JavaScript rendering and AI crawlers
- Server-side rendering
- Static site generation
- Crawlable internal links
FAQ
Can I rely on the initial HTML to inspect JavaScript content?
Google's JavaScript SEO documentation explains that an app shell can omit the actual content from its initial HTML. For such a page, inspect the rendered output as well as the response.
Where can I investigate missing rendered content?
Google's troubleshooting guide recommends inspecting loaded resources and JavaScript console output alongside the rendered DOM. You can use the Rich Results Test or URL Inspection tool for this check.
Sources
- Google Search Central, "Understand the JavaScript SEO basics", updated 4 March 2026
- Chrome for Developers, "Get started with viewing and changing the DOM", updated 1 March 2019
- Google Search Central, "Fix Search-related JavaScript problems", updated 18 December 2025
- Google Search Console Help, "URL Inspection tool", undated
Check how a page reads to answer engines. Open the GEO score analyzer