The rendered DOM is the document tree a browser builds for a page after its supported scripts have run and rendering has finished. It represents the markup as a visitor (and a rendering crawler) actually sees it, not the raw file the server first sent.
| Term | Rendered DOM |
|---|---|
| Category | Page Structure and Technical SEO |
| Also known as | Rendered Document Object Model, DOM |
| Where it appears | Page measurement and Force HTML |
What it means in RankGear
RankGear reads the rendered DOM when it measures a page, and its Force HTML option controls whether the crawler evaluates the fully rendered tree or the raw server response. Because RankGear compares your page against the pages currently ranking for a keyword, working from the rendered DOM lets it count and inspect elements as they exist after JavaScript has populated them — a heading injected by a framework, text loaded into a container, structured data written on the client. What lands in the rendered tree is the version of the page RankGear treats as real when it tallies elements and word counts.
How to interpret it
Check both presence and implementation. An element can sit in the rendered DOM and still be empty, duplicated, hidden, blocked, or semantically weak. Presence confirms a browser assembled the element; it does not confirm the element carries the content or meaning you intended. When a page depends on client-side rendering, compare the rendered view with the raw HTML to see what survives before scripts run — a large gap between the two is worth understanding, because not every renderer resolves the same way.
| View | What it shows |
|---|---|
| Raw HTML | The server’s original response, before any scripts execute. |
| Rendered DOM | The tree after supported scripts and page rendering have run — what RankGear measures with Force HTML off. |
Example
Say a product page builds its main heading through a JavaScript framework. In the raw HTML the <h1> is an empty shell; in the rendered DOM it holds the real heading text. Reading the rendered DOM, RankGear finds the populated <h1> and compares its content and count against the ranking pages — where a raw-HTML-only read would have flagged the heading as missing entirely.
Important considerations
- The rendered DOM reflects only the scripts RankGear’s rendering supports; unusual or heavy client-side behavior can still differ from what Google’s renderer ultimately produces.
- Technical conformance in the rendered DOM improves accessibility and machine readability, but it does not guarantee rankings.
- Force HTML changes what is measured — know whether you are looking at the rendered tree or the raw response before drawing conclusions.
- Comparisons against ranking pages are comparative indicators, not Google scores. Correlation is not causation; a present, well-formed element does not by itself move a page up.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.