Raw vs rendered HTML

See what changes when JavaScript runs: titles, headings, links, structured data and text that crawlers without a browser never see.

Crawling & indexingCheckerPaid plans
Raw vs rendered HTMLWe fetch the site from our server

Checking …

One moment while we look up this website.

What you’ll get

A clear answer in seconds.

  • A pass, warning or fail for every check
  • The evidence behind each result
  • What to change, in plain English
Example result

How it works

  1. Enter an addressYour site, a competitor's, or any public page.
  2. We check it liveOur server fetches it the way search engines and bots do.
  3. Read what to fixEach problem comes with the reason and the fix.

Why it matters

  • Many sites build their pages with JavaScript. Google renders them, but later and not always fully, and most AI crawlers (GPTBot, ClaudeBot, PerplexityBot) read only the raw HTML. Anything that appears only after JavaScript runs may be invisible to them.

  • We fetch the page twice: once as plain HTML, once in a real Chrome browser. Then we compare the parts that decide how a page is indexed and list the text that only exists after rendering.

Questions

Why is this on paid plans only?

Each check opens the page in a real Chrome browser in the cloud, which costs far more than a normal fetch.

What should I do if a lot changes?

Render the important content on the server: server-side rendering or static generation in frameworks such as Next.js, Nuxt or SvelteKit, or pre-rendering for single-page apps. At least the title, description, canonical, headings and main text should be in the raw HTML.

Want the full picture?

This tool checks one thing. A free Pagelyt scan checks speed, SEO, AI readiness, security and more, and tells you what to fix first.