Fetch & Render

What Fetch & Render does

Enter a live URL and this tool fetches it two ways: once as a plain HTTP request with Googlebot's user agent (the raw HTML your server sends before any JavaScript runs), and once through a real headless Chromium browser that executes the page's JavaScript, waits for network activity to settle, and captures the fully rendered DOM — the same two views Google's own indexing pipeline works from.

How to use it

1. Enter the full URL of the page you want to check.
2. Click Fetch & render. The page is fetched and rendered on our server — a real browser instance, not your own — which takes a few seconds longer than a plain fetch.
3. Compare the Raw HTML and Rendered HTML panels. Content present in Rendered but missing from Raw only exists after JavaScript executes — invisible to any crawler or tool that doesn't render.

Why this matters

Google renders pages before indexing them, but rendering is a separate, resource-limited pass from the initial crawl — a page whose critical content (title, links, main copy) only appears after client-side JavaScript runs is gambling on that render pass succeeding, completing in time, and not silently failing on a script error. Comparing the raw and rendered HTML directly shows what depends on JavaScript versus what's there from the first byte.

Related tool

For a structured side-by-side of the SEO-relevant differences (title, meta description, canonical, H1s, word count, links) plus a full markup diff, use Pre-rendering Tester instead — it runs the same fetch-and-render pass but focuses on what changed rather than showing both full documents.

Privacy

The URL is fetched and rendered by our server only to produce this comparison, and isn't stored beyond the job's lifetime. Requests to private or local network addresses are blocked.