Technical Audits
Part of JavaScript and search visibility
Compare Source HTML with Rendered Page Content
Compare a page's initial HTML with its rendered document to find changed content, links and search signals without guessing at the cause.
Use the same exact URL to compare its initial HTML response with its rendered DOM. Record changes to content, routes and search signals, then judge whether they affect the page or how its links can be discovered. A difference is a reason to investigate, not proof that JavaScript caused a search problem.
Capture both views
In a browser, use View Source (Ctrl+U in Chrome) to open and save the initial HTML. For a browser-rendered comparison, the View Rendered Source Chrome extension provides Raw, Rendered and Difference views, with changed lines highlighted; this is the browser’s rendering, not Google’s.
To check Google’s rendering, use the URL Inspection tool in Google Search Console and run a live test. Inspect its rendered DOM, loaded resources and JavaScript console output, then record the matching DOM details alongside the saved source. Note the URL, capture date and method for both views.
Keep Search Console’s older indexed information separate from a live source-versus-rendered comparison. Content updates, different requests or test conditions can also create differences without a change to the page’s JavaScript.
How to Capture and Compare Source HTML and Rendered Page Content
- Save initial HTMLUse View Source (Ctrl+U in Chrome) to open and save the initial HTML response.
- Use View Rendered Source extensionInstall the View Rendered Source Chrome extension to view Raw, Rendered and Difference views with highlighted changes.
- Check Google’s renderingUse the URL Inspection tool in Google Search Console to run a live test and inspect the rendered DOM, loaded resources and JavaScript console output.
- Record detailsNote the URL, capture date and method for both views. Keep indexed Search Console data separate from live comparisons.
Compare the elements that matter
| Element | Question for the two views |
|---|---|
| Main heading and answer | Was essential content present initially, added later or removed? |
| Important qualification | Does the condition remain beside the claim it limits? |
| Page destinations | Did rendering create usable anchors with href values? |
| Title and description | Do the final values describe the visible page? |
| Canonical and robots instructions | Are the delivered and rendered signals consistent with the intended URL? |
For example, a page title that looks correct in the initial HTML may be changed by JavaScript in the rendered DOM; compare the exact values, because the rendered title can be the one Google uses. A comment plugin that inserts a new <h1> after rendering is another concrete content change: note the added heading and where it appears.
For routes, compare the actual destinations in anchors, not just whether link text is visible. Googlebot parses links in the initial response and parses the rendered HTML for links again, so a destination present only after rendering is available in a different link-discovery pass.
For canonical or robots discrepancies, record both values and refer them to the separate canonical and indexability checks. Google advises against changing an existing canonical to a different URL during rendering, and an initial noindex can cause Google to skip rendering.
Investigate the discrepancy
Content added after rendering can be appropriate if the final page gives the right answer. Content present in the source but missing from the rendered DOM may point to a component, failed request or error state; use the loaded resources and JavaScript console output to investigate.
For a material difference, compare another page using the same template. This can help show whether the change is isolated or repeated, but the HTML difference alone does not establish its cause.
Record the exact URL, capture dates, methods and changed elements. After a change, capture and compare both views again; a matching live result is a test result, not a guarantee of indexing.
Pros and Cons of Using Rendered Content for SEO
- ProsEnsures Google sees the same content users see; helps identify dynamic content issues; supports accurate indexing of JavaScript-driven pages.
- ConsDifferences may arise from temporary errors, failed requests or test conditions; not all discrepancies indicate SEO problems; requires careful validation to avoid false conclusions.
