DOM
Also called: document object model, dom tree
The DOM (Document Object Model) is the browser's in-memory, tree-shaped representation of a web page, built by parsing the HTML and then applying JavaScript. It is the rendered version search engines actually index, not the raw HTML you see in View Source.
The DOM is a programming interface that represents a document as a tree of nodes (elements, text, attributes). Per MDN, “when a web browser parses an HTML document, it builds a DOM tree and then uses it to display the document.” Scripts read and rewrite that tree, which is how modern pages change without a reload.
Rendered DOM vs raw HTML
Your server sends a raw HTML document. The browser parses it into a DOM tree, then runs JavaScript that can add, remove, or rewrite nodes. What you see under Inspect > Elements is the rendered DOM; View Source shows the raw response before scripts run. On JavaScript-heavy sites these can differ a lot.
Google processes pages in three phases: it crawls the raw HTML, queues the page, then renders it with a headless Chromium instance that executes JavaScript and builds the final DOM. Indexing uses that rendered output. Google’s docs state that “Google can only see content that’s visible in the rendered HTML,” so anything that never lands in the rendered DOM cannot be indexed. Googlebot builds the DOM but does not click, scroll, hover, or fill forms, so content gated behind interaction may never enter the indexed DOM.
One trap: Google may read a noindex in the raw HTML before rendering, so stripping that tag later with JavaScript often will not work. To check, compare View Source against the rendered DOM in DevTools, then use the URL Inspection tool in Search Console to see the exact HTML Google rendered.
How it affects your traffic
The gap between your raw HTML and rendered DOM is where JavaScript sites quietly lose rankings. If headings, body copy, canonical tags, or internal links only appear after hydration, and Googlebot's render stalls or misfires, those pages get indexed thin (or skipped), capping the organic traffic they can earn. Diagnosing that gap (View Source vs rendered DOM vs the URL Inspection snapshot) and getting critical content into server-rendered HTML is core Technical SEO work. Fix it and pages that were invisible to crawlers start ranking on the content you already published.
Get Technical SEO that moves the needle
We turn terms like this into ranked pages and qualified pipeline. Start with a free Initial SEO Strategy.