What you’ll need
A public page URL, crawler identity and language.
SEO TOOL · FREE TO USE
Fetch & Render
Compare the fetched HTML with the page after JavaScript runs.
Free to use · No saved inputs01Rendering workspace
- 1 Add your input
- 2 Run the tool
- 3 Get your results
A public page URL, crawler identity and language. New here? Start with “Try an example”.
More settings (optional)
The URL and chosen crawler/language settings reach our inspection server, which contacts the target website. No login pages, credentials or private-network addresses are supported. Inputs and results are not stored.
Public target inspection · No paid API
How it works
Fetch source and load it in isolated Chromium; extract SEO fields, screenshot and rendered DOM.
Know the limits
A finite load window and blocked risky requests may affect output. This is not a verified Googlebot session.
GET FROM A QUESTION TO A NEXT STEP
Find what changes after JavaScript runs
A page can look complete in your browser while its initial HTML contains very little useful content. Fetch & Render compares the fetched response with the page after JavaScript runs in an isolated browser. Use it when a client-rendered page loses a title, loads a canonical late or hides important links behind scripts. The comparison helps you frame a concrete issue for your developer.
How to use Fetch & Render
Enter a public page URL and choose the available crawler and language settings. Use the exact page where the problem occurs.
Run the live inspection. Review source signals, rendered signals and the screenshot together, not just a single status value.
Look for important text, headings, links or structured data that differ between the two views. Save the report before changing the page.
What do the results mean?
A difference identifies a rendering dependency in this inspection. It does not establish what Google has indexed. Time limits, blocked resources, consent screens and network failures can affect the rendered snapshot; an incomplete run needs investigation rather than a clean bill of health.
What to do next
After a fix, repeat the inspection and confirm search-engine-specific behavior with the relevant verified webmaster tools.
Keep the scope in mind
A finite load window and blocked risky requests may affect output. This is not a verified Googlebot session.
Common questions about Fetch & Render
Is the rendered view exactly what Googlebot sees?
No. This is an isolated Chromium inspection with selectable request settings. It is not a verified Googlebot session or a copy of Google’s indexing pipeline.
Why does my screenshot look incomplete?
The page may need a resource that failed or was blocked, take longer than the inspection window, or require interaction. Compare request errors and source content before concluding that the underlying page is broken.