Google runs it as a classic search crawler, which means it does ordinary search indexing, of the kind that has existed for decades. That matters more than it used to rather than less: several assistants answer by searching a conventional index first and reading the top results.
What blocking it costs you: You are invisible to Google Search and to AI Overviews built on it. Ordinary search indexing stops, and increasingly that index is the substrate AI answers are built from as well.
The user agent, and the token a rule matches on
These are two different strings and confusing them is why a rule that looks right does nothing. A robots.txt rule matches on the product token, case-insensitively, and ignores the rest of the user-agent header entirely.
An empty Disallow: and Allow: / mean the same thing to a crawler. What does not mean the same thing is having no rule at all: absence is permission by default, but it is permission nobody wrote down, and it survives only until somebody adds a blanket User-agent: * block without thinking about this crawler.
Blocking Googlebot
User-agent: Googlebot
Disallow: /
Before you paste that: you are invisible to Google Search and to AI Overviews built on it. That is the cost, and it is paid silently — no error appears in your logs, no report tells you, and the traffic you lose was traffic you never saw arrive.
Deciding one crawler at a time is how a robots.txt ends up refusing things nobody meant to refuse. The free robots.txt generator asks the question once per category instead — train on me, cite me, fetch on demand, shop on my behalf — and writes the whole file for all 54 crawlers, naming what each refusal costs before you copy it.
How the web actually treats Googlebot
Measured on 2026-09-06, by reading the robots.txt of 292 public websites and resolving each one against this crawler specifically.
Verdict
Sites
Share
Blocked
0
0%
Explicitly allowed
238
82%
No rule either way
54
18%
No site is named, here or anywhere else on this domain. The count is the useful part; a league table of businesses that never asked to be measured is not.
The row worth reading twice is the last one. 54 of 292 sites have written no rule about Googlebot at all, which means their position on it is an accident rather than a decision — whatever their User-agent: * block happens to say.
What Googlebot is not
Google runs 6 other crawlers with different jobs, and this is where the expensive mistake happens. Somebody means “do not train on my content”, writes one rule against the operator’s name as they remember it, and blocks the crawler that would have sent them a customer instead.
it fetches one page at the moment a person asks an assistant to open it. There is no index and no schedule: somebody has pasted your link or asked for your site by name, and is waiting for the answer while the request happens.
it fetches one page at the moment a person asks an assistant to open it. There is no index and no schedule: somebody has pasted your link or asked for your site by name, and is waiting for the answer while the request happens.
it works through a task on somebody’s behalf — compare these suppliers, book the table, find the part that fits. It reads pages to decide, and what it cannot read it cannot put on the shortlist it hands back to the person.
it works through a task on somebody’s behalf — compare these suppliers, book the table, find the part that fits. It reads pages to decide, and what it cannot read it cannot put on the shortlist it hands back to the person.
it reads documentation while a developer is building something against your API, usually with the developer watching. What it cannot fetch, the developer gets as a guess from the model instead.
it collects text to train a model on. It sends nobody to your site, now or later, and it is the only category on this list where that is true.
Rules are matched per token. Blocking one of these says nothing about the others, which is the point: you can refuse training and keep every crawler that puts your link in front of a person.
Checking what your site does right now
Reading your own robots.txt is not the same as knowing what a crawler concludes from it. Precedence between a User-agent: * group and a named one, the longest-match rule between overlapping paths, and a token you spelled slightly wrong all produce a file that looks correct and behaves otherwise.
npx axray-cli your-site.com
The scan resolves your file against all 54 crawlers on this list individually and reports which ones are allowed, blocked, or covered by nothing. It is free, needs no account, and installs nothing.
Questions people ask about Googlebot
What is Googlebot?
Googlebot is a classic search crawler operated by Google: it does ordinary search indexing, of the kind that has existed for decades. That matters more than it used to rather than less: several assistants answer by searching a conventional index first and reading the top results.
Should I block Googlebot in robots.txt?
Only if you are willing to pay what it costs. You are invisible to Google Search and to AI Overviews built on it. Ordinary search indexing stops, and increasingly that index is the substrate AI answers are built from as well.
What is the Googlebot user agent string?
Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) — and the robots.txt product token, which is what a rule actually matches on, is Googlebot.
How do I check whether my site is blocking Googlebot right now?
Scan your site with AXRAY. It resolves your robots.txt against 54 named AI crawlers individually rather than reporting one verdict for all of them, so it will tell you whether this specific crawler is allowed, blocked, or covered by no rule at all. It is free and needs no account.