Google-Agent
Google · User fetch · robots.txt: No
Used by AI agents running on Google infrastructure to navigate the web and take actions when a user asks them to.
Block Google-Agent
User-agent: Google-Agent
Disallow: /
Unconfirmed by the operator Google's documentation we checked does not say what blocking Google-Agent changes beyond the crawler itself.
Allow Google-Agent
User-agent: Google-Agent
Allow: /
An allow group only changes anything if a broader rule would block Google-Agent. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.
Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.
Already have a robots.txt? Paste it into the robots.txt checker to see whether it blocks Google-Agent on a given path, and which line decides.
Block or allow it at the server
robots.txt asks; a server rule refuses. Every rule here matches Google-Agent, spelled as in the User-Agent Google documents (“compatible; Google-Agent;”), and matches it case-sensitively. The server answers 403.
What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user.
(Apache HTTP Server 2.4 documentation). A fake Google-Agent is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Google's published addresses.
Addresses in the “only the real one” rules: Google's list developers.google.com/static/crawling/ipranges/user-triggered-agents.json, 20 ranges, fetched 8 Oct 2026, list dated 8 Oct 2026. Operators change their lists; compare the date with the live list before you rely on it.
The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.
Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.
Who blocks it
Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 4 block Google-Agent from the whole site by name, 35 block it through their User-agent: * group, and 5 name it with partial rules (some paths closed, the home page open). 0 more name it only to let it in.
4
block it by name 0.8%
35
block it through * 6.9%
5
name it, partial rules 1.0%
Percentages are of the 508 files we could read, not of all 1,000 sites.
Highest-ranked sites that block Google-Agent by name
- sciencedirect.com rank 223
- cnbc.com rank 478
- usatoday.com rank 603
- lemonde.fr rank 711
Each links to the site's live robots.txt, which may have changed since 2026-10-09.
robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.
Facts
- Operator
- Purpose
- User-requested fetch
- Obeys robots.txt
- No. Google says its user-triggered fetchers generally ignore robots.txt, because a user requested the fetch, and it lists no robots.txt token for Google-Agent. A "User-agent: Google-Agent" group is therefore unlikely to have any effect.
- In your server logs
- The user-agent string contains "compatible; Google-Agent;", in mobile and desktop variants.
- How to verify it
- Match the IP against Google’s published user-triggered-agents list. Google says these fetchers’ reverse DNS names end in gae.googleusercontent.com or google-proxy-…google.com, and that Google is also experimenting with Web Bot Auth for this agent.
Published list: developers.google.com/static/crawling/ipranges/user-triggered-agents.json — 12 IPv4 and 8 IPv6 ranges when we fetched it, list dated 23 Sep 2026. Always match against the live list; operators update them. To count real and fake Google-Agent requests in your own server log against this list, drop the log into the log reader.
What Google says
Quoted word for word from the operator's documentation.
“Google-Agent is used by agents hosted on Google infrastructure to navigate the web and perform actions upon user request.”
“Because the fetch was requested by a user, these fetchers generally ignore robots.txt rules.”
“(KHTML, like Gecko; compatible; Google-Agent;”
“It uses IP ranges from user-triggered-agents.json.”
“The user-triggered fetchers' reverse DNS mask, depending on whether the fetcher is Google or user owned, matches ***-***-***-***.gae.googleusercontent.com or google-proxy-***-***-***-***.google.com respectively.”
“Google is also experimenting with the Web Bot Auth protocol”
Sources
- Google: List of Google's user-triggered fetchers — fetched and checked 2026-09-24
- Google: user-triggered agent IP ranges (user-triggered-agents.json) — fetched and checked 2026-09-24