All Tools

  1. SEORCH
  2. Source Code Comparison

Comparing the source code of a website for different user agents

Source Code Comparison?

  • Googlebot first fetches the static HTML and renders the page with JavaScript later – the two versions can differ.
  • You can use this tool to compare if a website is returning different data for different bots or user agents.
  • From an SEO point of view, it is important that the content of static and rendered versions differs as little as possible.

What is the difference between a static and a rendered fetch?

Google processes a page in two steps: first Googlebot loads the HTML as the server delivers it. Then Google renders the page with a current version of Chrome and runs its JavaScript. The rendered version is what gets indexed. Rendering can happen with a delay.

Static fetch:
The source code as the server sends it. It only contains the content, links and meta tags that are in the HTML without JavaScript.

Rendered fetch:
The page after a browser has run the JavaScript and added content loaded later. This is also how visitors see it.

How do I check this at Google?

In Google Search Console, the URL Inspection tool shows the rendered HTML of a URL under "View crawled page". In 2019 it replaced the former "Fetch as Google" feature (Fetch & Render).

With the SEORCH source comparison you compare both versions for different bots and browsers directly, also for pages that are not in your Search Console.

What if the code is different?

If the source code differs between the static and the rendered version, this may indicate a potential problem with Googlebot's processing and rendering of the webpage. Here are some examples that could lead to such differences:

  1. JavaScript execution:
    Rendering uses a headless browser that can execute JavaScript and handle dynamic content. If your page relies heavily on JavaScript to generate or modify its content, the rendered version may differ from the static version because no JavaScript is run in the static fetch.
  2. AJAX Calls:
    If your webpage makes AJAX calls to fetch additional content or data after the initial page load, the static version fetched by Googlebot will not contain the results of those AJAX calls. When rendering, however, the JavaScript is executed and the page is displayed as it appears after the AJAX calls are complete. This can lead to differences between the static and rendered versions.
  3. Dynamic content generation:
    If your page generates content dynamically based on user interactions or server-side logic, the static version fetched by Googlebot only captures the initial state of the page. The rendered version, however, shows the dynamic content as it appears after all processing is complete.

It's important to note that Google's ability to process JavaScript and render dynamic content has improved over time. Since 2019, Googlebot renders pages with an up-to-date (evergreen) Chromium and can handle most JavaScript-driven websites.
However, it is recommended to ensure that critical content is available in static HTML rather than exclusively rely on JavaScript execution for optimal indexing and accessibility.

Relevant SEO content should be the same in both the static and JavaScript versions.

This includes:

  • HTTP status codes
  • Title Tag and Meta Description
  • Robots Instructions and Canonical Tags
  • Hreflang Tags
  • Headings (H tags)
  • Body text
  • Internal links
  • Images

You can neglect:

  • Login areas
  • Cart functions
  • Cookie Consents
  • Ad Pixel, Tracking Pixel
  • Third party integrations such as iframes
  • Personalizations