View Page as Googlebot (Free Tool)

View page as Googlebot: request it with Googlebot's user agent and compare it to a normal browser; Search Console's URL Inspection shows what Google itself fetched.

Ready. Paste an address, tick the box, press the button.

All views
ViewStatusEnds onTitleAlikeJS signals
Desktop ChromeNot checked yet
iPhone SafariNot checked yet
GooglebotNot checked yet
Facebook crawlerNot checked yet
Ad click (Google)Not checked yet

View page as Googlebot: paste a URL and see the page as a Googlebot-labelled request gets it, next to the page a normal browser gets. Same engine as the website cloaking checker.

What we check

view user agent what it shows
Googlebot Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Googlebot/2.1; +http://www.google.com/bot.html) Chrome/142.0.0.0 Safari/537.36 the page for a Googlebot-labelled request
Desktop Chrome Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36 the page for a normal visitor

The Googlebot string is Google’s Googlebot Desktop agent, with our Chrome version in place of W.X.Y.Z. We compare final URL, redirects, status, title, visible text, link domains, forms and checkout, and script signals. JavaScript is read, not run. Both views run from one datacenter location, with 8 seconds and 2 MB per view. Results are not stored.

Three more views (iPhone, Facebook crawler, ad click) run too and sit under “All views”. Full field list: website cloaking checker.

What this cannot show

A request with Googlebot’s user agent is not Googlebot. Google documents how site owners confirm the real one: reverse DNS lookup on the IP, then a forward lookup to check it matches (Google docs). A site that does this sees a stranger.

So: no difference here does not prove the site shows Google the same page. A difference here is a real finding.

See what Google fetched on your own site

In Search Console, URL Inspection has a live test. “View tested page” shows a screenshot of the rendered page, the raw HTML, the HTTP headers and the JavaScript console output (Search Console Help). The URL must be in a property you have open.

User agents Google publishes

Google lists these for Googlebot (Google crawlers):

name string
Googlebot Desktop Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Googlebot/2.1; +http://www.google.com/bot.html) Chrome/W.X.Y.Z Safari/537.36
Googlebot Smartphone Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

W.X.Y.Z is the Chrome version. We also send the Desktop string; the Smartphone one is not in this tool. Reproduce by hand: check a site with curl.

Questions

How does Googlebot see your website?

Google fetches the page, renders it, and indexes what it sees. For a page on your own site, Search Console's URL Inspection live test shows the rendered page, raw HTML and HTTP headers Google got.

Does Google check to see if you are a bot?

Google does not have to: Googlebot announces itself with a user agent and crawls from published IP ranges. Sites can confirm a visitor really is Googlebot with Google's reverse DNS method.

Is this the same as what Google sees?

Not always. We send Googlebot's user agent from our own IP. A site that checks the IP will not treat us as Google. Use URL Inspection for your own site.

Is my page crawlable?

If the Googlebot view loads the same content as the browser view, the user agent is not blocking it. robots.txt and indexing are separate checks; use Search Console.