Free tools/What Google Sees
Raw HTML vs rendered page

Compare what arrives first with what JavaScript adds later.

See the readable text, title, description, headings and canonical in the initial server response beside the browser-rendered result. It is a practical way to diagnose JavaScript-dependent SEO.

Complete one-URL report · No account required · Public pages only · Shareable result

Report includesEvidence based

A side-by-side rendering diagnosis

Initial response

The HTML a crawler receives before client-side JavaScript executes.

Rendered browser

The page after a browser loads and runs available scripts.

Content gap

Readable words and key elements that appear only after rendering.

Stored excerpts

Inspectable evidence from both snapshots, not only a score.

Results describe the submitted URL and separate measured evidence from anything still unverified.
What the check covers

Useful answers, with the limits made clear.

01

Readable text

Compare word counts and text excerpts between both versions.

02

SEO metadata

Verify whether title, description and canonical exist in initial HTML.

03

Heading structure

Compare H1 and H2 signals before and after rendering.

04

SPA shell risk

Flag pages where most meaningful content depends on JavaScript.

Why this matters

Google can render JavaScript, but initial HTML still matters

Googlebot can render many JavaScript pages, but rendering is a separate stage and failures still happen. Other search, social and AI crawlers may execute less JavaScript or none at all. Serving essential content and metadata early reduces that dependency.

This checker does not pretend to reproduce Google’s private indexing systems. It provides a repeatable technical comparison between a direct HTTP response and a browser-rendered snapshot so you can see where the risk lives.

Questions answered

What Google Sees FAQ

Is this exactly what Googlebot sees?+

It is a diagnostic comparison, not Google’s private renderer. It shows what is present in the initial response and what appears after a modern browser renders the page.

Is JavaScript bad for SEO?+

No. The risk appears when essential content, links or metadata fail to render reliably or are absent from the initial response for crawlers that do not execute JavaScript.

What is an SPA shell?+

It is a minimal HTML response that relies on JavaScript to add most visible content. A shell is not automatically a problem, but it increases crawler and rendering dependency.

What should match between both versions?+

Important page copy, title, description, canonical, primary heading and crawlable links should remain consistent enough that crawlers understand the same page.