Free tool
What AI bots see on your page.
Enter a page address. I fetch it twice: as raw HTML, the way most AI bots read it, and after JavaScript runs, the way a browser and Google see it. You will see what is missing without JavaScript and what is worth moving into the HTML.
Addresses you enter are not stored. A check usually takes 5-20 seconds.
Why raw HTML matters.
Google renders, but later
Googlebot runs JavaScript, but in a second wave. Content, links and meta tags in the raw HTML Google sees straight away, the rest later.
AI bots usually skip JavaScript
Bots from ChatGPT, Claude or Perplexity mostly read raw HTML. What is not there, they cannot cite.
Less JavaScript, faster page
Content in the HTML also appears faster for people, which helps LCP and the overall experience.
How to move content into the raw HTML.
The best fix is server-side rendering (SSR) or static site generation (SSG). The server sends ready HTML with the content, and JavaScript only adds interactivity. This is how Next.js, Nuxt, Astro and classic WordPress work.
If a rebuild is not an option, prerendering helps: a separate service prepares ready HTML and serves it to bots. Bots must get the same content as people, otherwise it is cloaking, which breaks Google's rules.
Day to day, the most common problems are simpler: menus built from elements without <a href>, FAQs and reviews loaded from external widgets, structured data added via Google Tag Manager, or a canonical set by a script. Each of these can usually be moved into the page template.
Test limitations.
The rendered version comes from Chrome in the Cloudflare cloud, waiting until the page stops loading data. The page may look slightly different than for you, e.g. without consent banners or logged-in content. Bot protection can block the check. Content comparison is based on text fragments, so treat percentages as approximate.
Sources
- Understand JavaScript SEO basics Google Search Central
- Dynamic rendering as a workaround Google Search Central
- Spam policies: cloaking Google Search Central
See technical SEO Also check whether AI bots can access the site
Questions about raw HTML and JavaScript.
Does Google see content loaded by JavaScript?
Usually yes. Googlebot renders pages in Chrome, but later than fetching the HTML, and on large sites not always for every page. The key elements, title, canonical, robots, main content and links, are safer in the raw HTML.
Do ChatGPT and Perplexity run JavaScript?
Companies rarely publish details, but industry tests suggest most AI bots read raw HTML and do not run JavaScript. Content built only in the browser is often invisible to them.
What are SSR and SSG?
SSR (server-side rendering) generates HTML on the server on each visit. SSG (static site generation) builds ready HTML files in advance. Either way, browsers and bots get the full content straight away.
Is prerendering for bots cloaking?
Not if bots get the same content as people, just ready-made. Cloaking means showing bots different content than users, which breaks Google's rules.
Why did the rendered version not load?
Usually bot protection or the free rendering limit. The raw HTML analysis still shows what bots see without JavaScript.
Is your page empty without JavaScript?
As part of technical SEO I check exactly what Google and AI bots see and prepare a concrete plan for your developer to move content into the HTML.