Assistant fetchers
GoogleAgent-URLContext is a bot operated by Google that fetches single pages on demand for an AI assistant. GoogleAgent-URLContext is a web fetcher operated by Google that retrieves web content on behalf of Gemini API users. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"GoogleAgent-URLContext"
Checked against
Nothing published
Live check
No operator check exists for GoogleAgent-URLContext. This still shows what the address really is.
Reference
| User agent | GoogleAgent-URLContextToken only: match on the substring. |
|---|---|
| Operator | |
| Purpose | Assistant fetchers |
| Respects robots.txt | No policy |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | GoogleAgent-URLContext |
| Operator documentation | https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers |
GoogleAgent-URLContext is a web fetcher operated by Google that retrieves web content on behalf of Gemini API users. When a developer provides a URL as context in a Gemin…
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: GoogleAgent-URLContext
Disallow: /User-agent: GoogleAgent-URLContext
Allow: /User-agent: GoogleAgent-URLContext
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking GoogleAgent-URLContext means a person who asks about one of your URLs gets an error instead of a summary. That is a support and reputation trade-off, not a training one.
Build a file for every crawlerFAQ
GoogleAgent-URLContext is a bot operated by Google that fetches single pages on demand for an AI assistant. GoogleAgent-URLContext is a web fetcher operated by Google that retrieves web content on behalf of Gemini API users. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Not documented. No operator statement says whether GoogleAgent-URLContext reads robots.txt, so add the rule but verify in your logs that the requests actually stop.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the GoogleAgent-URLContext token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking GoogleAgent-URLContext means a person who asks about one of your URLs gets an error instead of a summary. That is a support and reputation trade-off, not a training one.