XunLMove cross-border work forward
中文

GOOGLEBOT SIMULATOR / RAW HTML VS RENDERED

Googlebot Simulator

Open a page as Googlebot, run its JavaScript, and see exactly which text and links Google can read.

Free · follows robots.txt

One check takes about 15–40 seconds: read robots.txt → request the page as Googlebot → run its JavaScript in an isolated browser → compare raw and rendered HTML.

YOUR NEXT STEP

Turn a website check into a monitoring routine

Create a company account to manage sites and notifications. Pro supports 5 sites and 5-minute availability monitoring, with deep diagnostics available according to your plan and permissions.

Create company accountExplore ProContact us

New companies receive a 14-day Pro trial, with no card required. Trials exclude the paid monthly credit grant.

Already have an account? Open your workspace →

How to use it

  1. Enter the page URL (product, category or article pages all work) and choose the smartphone or desktop Googlebot.
  2. Start with the verdict and the findings: red items affect indexing, yellow items are risks, and each one tells you how to fix it.
  3. Under Text Google sees, yellow paragraphs only appear after JavaScript runs and may be invisible to other search engines and AI crawlers. Under SEO tags compared, check whether JavaScript changes the title, canonical or noindex.

How Google processes JavaScript pages

1. CrawlGooglebot requests the URL, obeying robots.txt, and receives the raw HTML.
2. QueuePages that need JavaScript wait in the render queue, for seconds or much longer.
3. RenderA headless, up-to-date Chrome runs the JavaScript and builds the final page.
4. IndexGoogle indexes the rendered text, links and tags.

Content already in the raw HTML from step 1 is the most reliable. Content that only appears in step 3 waits for rendering and is lost if rendering fails. Bing, Yandex, Baidu and most AI crawlers such as ChatGPT and Perplexity barely run JavaScript and see only the raw HTML.

Risk by site technology

Site technology and JavaScript risk
TechnologyRiskRecommendation
WordPress, Shopify and other classic themesLowContent is in the server HTML; do not block /wp-content/ in robots.txt.
React / Vue single-page apps (browser-only rendering)HighThe raw HTML is an empty div and everything depends on rendering. Move to server rendering or static generation with Next.js / Nuxt.
Next.js, Nuxt, Astro (SSR / SSG)LowContent ships in the HTML; check that client-only components do not hide key content.
Site builders with third-party widgets (reviews, prices, stock)MediumWidget content usually loads via JavaScript: Google may see it, other crawlers do not.
Infinite scroll and load-more buttonsHighGoogle does not scroll or click; provide plain paginated links.

Frequently asked questions

How is this different from URL Inspection in Search Console?

Search Console only covers sites you have verified and needs a login. This tool checks any public page, including competitors, and directly compares raw and rendered HTML, highlighting paragraphs that need JavaScript. Search Console is authoritative; this tool is for fast diagnosis.

Does Google run JavaScript?

Yes. Google renders with an up-to-date Chrome, but rendering comes after crawling, and blocked resources, script errors or slow loading leave the rendered page incomplete. The safest approach is to put important content directly in the HTML.

Why is the smartphone Googlebot the default?

Google uses mobile-first indexing for nearly every site, crawling and ranking mainly with the smartphone Googlebot. Content missing from the mobile page does not count even if the desktop page has it.

Can AI search (ChatGPT, Perplexity) see JavaScript-dependent content?

Mostly not. Major AI crawlers largely read only the raw HTML. To be cited by AI search, keep product specs, prices and FAQs in the HTML; the paragraphs highlighted in yellow here are the ones at risk.

Will the site treat this as the real Googlebot?

This tool sends Googlebot's published User-Agent, but requests come from our server, not Google's IPs. Some firewalls block anything claiming to be Googlebot, so results may differ from the real crawler; confirm in Search Console.

Which requests does it make? Will it affect my site?

It reads robots.txt, the page itself and the scripts, styles and data requests needed to render it (about 80 at most). It follows your robots.txt rules for Googlebot, loads no images or video, submits no forms and never logs in: about the load of one normal visit.

Googlebot simulator practical guide and common questions

What does a Googlebot simulator do?

Each page is read twice: the raw HTML without JavaScript (what Bing and most AI crawlers see) and the page rendered in an isolated browser (what Google indexes). Paragraphs are compared to highlight JavaScript-dependent text, and the title, canonical, noindex, H1, links and structured data are checked for JavaScript changes.

Who is this for, and when is it useful?

Site owners, SEOs and export marketers on React, Vue, site builders or plugins who need to know whether Google sees their specs, prices and copy, or why a page is not indexed or lost rankings.

How do I use this Googlebot simulator?

Enter a URL, choose the smartphone or desktop Googlebot, and after 15–40 seconds read the verdict, findings and the text Google sees.

How should I interpret the results?

Requests come from our server, not Google's IPs, and some firewalls treat them differently; rendering loads no images or video and is capped at about 30 seconds and 80 requests. Use it for diagnosis; Search Console is authoritative on indexing.

Where is the work performed, and which services receive data?

Requests come from our server with Googlebot's published User-Agent and follow the site's robots.txt rules for Googlebot; rendering runs in an isolated browser that loads no images or video, submits no forms and keeps no results.