Check JavaScript rendering searchVIU shows you what JavaScript changes on your pages
searchVIU renders every URL in Chrome and compares the source code with the rendered HTML. For every page, you see which signals JavaScript changes.
/sale/In the raw HTML: None · After rendering: noindex/zelte/2-personen/In the raw HTML: /zelte/2-personen/ · After rendering: /zelte//marken/In the raw HTML: Beispiel-Shop · After rendering: Marken von A bis Z | Beispiel-Shop/ratgeber/zelt-aufbauen/In the raw HTML: None · After rendering: Zelt aufbauen in fünf SchrittenSame structure as the “Signals changed by JavaScript” table in the report. Example values, URLs shortened.
What is the difference between source code and rendered HTML?
The source code is the HTML response from your server. The rendered HTML is the state after the browser has run JavaScript. Google indexes the rendered HTML, while many AI crawlers only read the source code.
If the two versions differ, Google and these bots see different pages. Google also points out that not all bots can run JavaScript. Google Search Central, Understand the JavaScript SEO basics
Our overview of AI crawlers lists 39 bots. For 14 of them, there is a statement from the operator or a measurement, and 8 of these 14 do not run JavaScript, including GPTBot and ClaudeBot. AI crawlers and JavaScript rendering at a glance
Summary
You can check a single page in four steps
For a single URL, you don't need a crawl. The URL Inspection tool in Search Console shows you what Google has rendered.
To test how Google crawls and renders a URL, Google recommends the URL Inspection Tool in Search Console. It shows loaded resources, JavaScript console output and the rendered DOM. Google Search Central, Fix Search-related JavaScript problems
Open the page's source code in your browser. It shows what the server delivers without JavaScript.
In the URL Inspection tool in Search Console, “View crawled page” shows the HTML and JavaScript console output of the last crawl. “Test live URL” adds a screenshot.
Compare the title, meta description, canonical, meta robots, hreflang, structured data, headings, text and links in both versions.
Check the homepage, a category, a product and an article one by one. The homepage alone is not enough because deviations depend on the template.
To check every page, you need a crawler that renders
Spot checks show individual URLs. For the whole website, you need a crawler that renders every page in a browser and keeps both versions.
Our study of over 200 domains from 2020 shows how often the two versions differ. There were differences on 96% of the domains and 56% of the URLs. To the JavaScript crawling study
Set up the crawler to render every URL in a browser. Some crawlers only read the source code by default.
Crawl as a smartphone and allow scripts and CSS in robots.txt. Google cannot render blocked files either.
For each URL, compare the title, meta description, canonical, robots directives, text and internal links in the source code and in the rendered HTML.
Group the deviations by page type. If a template or a script is behind them, one fix solves many URLs.
searchVIU renders every URL and shows what JavaScript changes
searchVIU renders every single URL in Chrome, even with millions of URLs, and shows you every place where JavaScript changes the title, canonical, robots directives, content or links.
The full crawl runs every week and loads every URL in Google Chrome, as a smartphone by default.
For every URL, searchVIU stores the raw and the rendered HTML, plus a screenshot, network log and HTTP headers.
The “Signals changed by JavaScript” table lists the changed signal for each URL with both values, “In the raw HTML” and “After rendering”.
Click a row in “Links and content removed by JavaScript” to see every link that was removed and every link that was added.
You can find the report in the app under SEO Analysis. The “Changed URLs” table shows what is new or fixed since the last crawl.
More about JavaScript SEOThese are the differences searchVIU shows for every URL
Every deviation is in the report with both values. Your development team gets the URL, the signal and the difference.
| Element | What searchVIU compares | In the JS Rendering report |
|---|---|---|
| Robots directives | noindex and nofollow in the raw and the rendered HTML | Robots tag changed |
| Canonical | Type and target URL of the canonical in both versions | Canonical changed |
| Title | Title in the raw and the rendered HTML | Title changed |
| Meta description | Meta description in both versions | Meta description changed |
| Internal links | Links that only appear in the raw HTML, and links that only appear after rendering | Links removed by JavaScript, Links added by JavaScript |
| Text | Text missing after rendering, as a share of the page's text | Content removed, column “Text removed” |
| JavaScript errors | Errors in the browser console during rendering | JavaScript errors |
As of November 16, 2026. The app interface is in English, and the names here match the report.
Does searchVIU render like Googlebot?
searchVIU renders with the current stable version of Google Chrome and updates it every month. Google's documentation says Google Search runs JavaScript with an evergreen version of Chromium. You see your pages with the same browser technology Google uses to render them.
What do you do when JavaScript changes SEO signals?
Whatever Google and AI crawlers should read belongs in the source code. These four findings deserve a closer look.
Title, canonical or hreflang only appear via JavaScript
Google processes the title and canonical from the rendered HTML, and in searchVIU's experiment this also applied to hreflang. According to Google, you shouldn't use JavaScript to change the canonical URL to something else than the URL you specified as the canonical URL in the original HTML. Crawlers without rendering only see the source code, so that is where these signals belong. Canonical via JavaScript put to the test
Experiment on hreflang in the rendered HTMLnoindex only in the source code
When Google encounters the noindex tag in the source code, it may skip rendering and JavaScript execution, according to its documentation. A script that removes noindex later then has no effect. If you do want the page indexed, don't use a noindex tag in the original page code.
Experiments with Google Tag ManagerLinks only appear via JavaScript
Google follows such links if they are an a element with an href attribute in the rendered HTML. Crawlers without rendering don't find them. That is why navigation and important internal links belong in the source code.
Link patterns from our studyContent only appears after a click
Google Search does not interact with your page. Content that only loads after clicking or scrolling is missing from the rendered HTML. Deliver it on page load and show it with CSS.
Google Search Central, Fix lazy-loaded contentBoth versions match again, and you can prove it.
- No signal changed by JavaScriptSignals changed by JavaScript table
- No internal links removedLinks and content removed by JavaScript table
- No new findingscompared with last week's crawl
Frequently asked questions about JavaScript rendering
How do you test and optimize JavaScript rendering for search engines?
You compare the source code with the rendered HTML. For individual pages, the URL Inspection tool in Search Console is enough. For the whole website, you use a crawler that renders every URL.
Optimizing means that the title, canonical, robots directives, main content and internal links are already in the source code. Google says server-side rendering or prerendering is still a great idea because not all bots can run JavaScript.
How do you crawl a JavaScript website?
With a crawler that loads every page in a browser, runs the JavaScript and reads links and content from the rendered HTML. Without rendering, a crawler only gets the basic shell of a client-side rendered website.
searchVIU loads every URL in Google Chrome. A custom script for your website closes consent banners and opens content hidden behind a click.
How do I compare raw and rendered HTML for many pages?
In every full crawl, searchVIU stores both versions of every URL and compares them, even with millions of URLs. The JS Rendering report lists the changed signal for each URL, the value in the raw HTML and the value after rendering. More on crawling large websites
The full crawl runs every week. In between, Page Watch checks your most important pages continuously, throughout the day, and renders them just like the crawler.
Which crawler is right for JavaScript websites?
That depends on the size of the website and how often you want to check. Desktop crawlers such as Screaming Frog and Sitebulb run on your own computer. Screaming Frog only crawls the source code by default, according to the vendor, and JavaScript rendering is part of the paid license. Sitebulb shows the comparison of server response and rendered page in Sitebulb Pro and in the cloud version, according to the vendor.
Cloud crawlers handle rendering in different ways. Botify enables JavaScript crawls on request through the account manager, according to its help center. At Oncrawl, a crawl with JavaScript uses three times as many crawl tokens, as its help center states, and at JetOctopus a rendered page counts as two pages, according to its FAQ. Lumar renders with the current version of Google Chrome, according to its own documentation. Enterprise SEO crawlers compared
searchVIU renders every URL in every crawl. Rendering is included in SEO Monitoring.
All vendor information as of November 16, 2026.
Which SEO crawlers render JavaScript like Googlebot?
Google's documentation says Google Search runs JavaScript with an evergreen version of Chromium. Several crawlers say they render with Chrome or Chromium, including Screaming Frog, Sitebulb, Lumar, Botify and JetOctopus. JavaScript SEO basics
searchVIU uses the current stable version of Google Chrome, updates it every month and crawls as a smartphone by default. What Google actually rendered for a single URL is shown in the URL Inspection tool in Search Console.
Let's talk about your website.
In the demo, Michael shows you how searchVIU works, using your website and a demo project.
- Request in three short steps
- Quick alignment on crawler access, NDA and Search Console
- Demo with your website and the demo project
- Start planned and supported together
Which website is it about?
Please enter your website and your business email.We need your business email for the demo. Without a company address, you can use our free tools instead.
What do you need?
Select as many as you like.
Who are you?
We only use your details for the demo. More in our privacy policy.
We can't send the request without the spam protection checkbox.
We need your business email for the demo.Please check your email address.Please enter your website.Please check your website address.The spam check could not be loaded. Please email us at info@searchviu.com.That didn't work. Please email us at info@searchviu.com.

Thanks! Now pick a time.
The calendar shows the open slots for your call with Michael.