Enter a URL and see what Google's crawler receives: text, title, meta tags, headings, links, images without alt text, canonical, robots directives, headers and anything robots.txt blocks.
Paste the full URL of the page and press Fetch as Googlebot. We request the page with Googlebot's user agent, follow redirects, and show what came back: the status code and headers, the title and meta description, the robots directives, the canonical, every H1 to H3, the links, the images with no alt text, and the visible text as a crawler reads it. Problems are flagged at the top. Fix them, then fetch again. This simulator does not run JavaScript, which is the point: it shows what a crawler gets before rendering.
Pages look complete in a browser and empty to a crawler far more often than people expect: a noindex left over from staging, a canonical pointing at the old domain, CSS and scripts blocked in robots.txt, a redirect chain, text that only exists after JavaScript runs. Googlebot does render JavaScript, but later and with a budget, and most other crawlers, including the ones behind AI answers, do not. Seeing the raw response is the fastest way to catch all of that.
No. This version fetches the HTML the way a crawler does on its first pass and analyses that. If your page shows almost no text here, the content is being added by JavaScript, and you should render it on the server so every crawler sees it.
Close, not identical. We send Googlebot's user agent and accept headers from our servers, not from Google's IP addresses, so a site that checks IP ranges can serve us something different. For the definitive view, use URL Inspection in Search Console. This tool is the fast first check.
Any public page. Pages behind a login, on a private network or on localhost cannot be fetched. Each fetch is capped at 2 MB and 10 seconds, and you get 20 fetches an hour.