SEO browser · crawler simulator

See any page the way a crawler does.

Paste a URL to compare what a browser receives, what a crawler receives, and what JavaScript changes.

Worked example below:
example.com · captured 2026-09-06 · 559 bytes of source.

FIG.01

One page, four ways of seeing it.

A crawler doesn't keep the pixels. It strips a page down to source, then to text, then to the links that carry it onward. Below is exactly that, run on the saved example.com capture — every character is from the real 559-byte response.

STAGE 1Renderedwhat a person sees

STAGE 2Sourcewhat the crawler downloads

<!doctype html>
<html lang="en">
<head>
 <title>Example Domain</title>
 <meta name="viewport">
</head>
<body>
 <h1>Example Domain</h1>
 <p>This domain is…</p>
 <a href="…iana.org…">Learn more</a>
</body></html>

STAGE 3Textindexable words · 19 total

STAGE 4Linksthe crawl frontier · 1 edge

FIG.01 — example.com across four crawler stages. Source SHA-256ff67a9…a299d, 559 bytes, captured 2026-09-06. Vermilion marks what survives each strip.

FIG.02

The worked result: example.com

Requested as Browser with JavaScript rendered on. This page ships no JavaScript, so every crawler identity receives the same bytes — a clean baseline for reading the four diagnostic groups below. Run your own URL in the console above for a live report.

Access

from saved response headers

Status	HTTP/2 200
Content-Type	text/html
Server	cloudflare
Last-Modified	Wed, 02 Sep 2026 22:14:26 GMT
Redirects	none — single 200 response
robots.txt / X-Robots	unknown — not captured

Content

parsed from 559-byte source

Title	Example Domain
H1 (×1)	Example Domain
Meta description	none present in source
Canonical	none present in source
Lang	en
Indexable words	19
Structured data	none present in source

Rendering comparison

source vs. rendered DOM

JavaScript off — source

19 words

3 nodes · 1 link

JavaScript on — rendered

19 words

3 nodes · 1 link

Identical. example.com carries no scripts, so rendering adds nothing. Content does not depend on JavaScript — this page is fully visible to a source-only crawler.

Links & resources

outbound & sub-resources

External links1 — iana.org/domains/example
Internal links0
Scripts0
Stylesheets1 inline
Images0
Favicondata:, (empty)

Go deeper on one dimension.

The homepage runs the general comparison. These specialist tools isolate a single question.

/googlebot-simulator/Googlebot simulator

Fetch with Googlebot's desktop and smartphone identity, then set it beside the normal-browser response to spot what the crawler is served differently.

Open tool /javascript-seo-checker/JavaScript SEO checker

Diff source HTML against the rendered DOM to find content that only appears once scripts run.

Open tool /guides/how-search-engines-see-your-website/How search engines see your site

The crawl, render and index walkthrough — with honest limits on what any simulator can show.

Read guide

FIG.03

Crawl, render, index — and where a simulator stops.

Three stages sit between a URL and a search result. This tool reproduces the first two faithfully. The third belongs to Google alone.

01 · CRAWL

Fetch the source

A crawler requests the URL with its own identity and downloads the raw HTML — the same bytes shown in Stage 2, before any script runs.

02 · RENDER

Run the page

The crawler may execute JavaScript and build a rendered DOM. Comparing source to rendered output is where JavaScript-dependent content shows up — or fails to.

03 · INDEX

Decide and store

The search engine weighs signals, deduplicates, and chooses whether and how to store the page. This is private, changing, and never fully observable from outside.

The honest limit: no third-party simulator can reproduce Google's Web Rendering Service or its indexing exactly. This tool shows the crawl and render stages truthfully — what is fetched and what is rendered. For the index decision itself, use Google's own URL Inspection and Rich Results Test.