Does GoogleAgent-URLContext respect robots.txt?

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.

How do I block GoogleAgent-URLContext?

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.

IPScanner

Assistant fetchers

GoogleAgent-URLContext

Q: How do I verify a request really came from GoogleAgent-URLContext?

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.

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.

GoogleAgent-URLContext at a glance

Reference data for the GoogleAgent-URLContext crawler
User agent	`GoogleAgent-URLContext` Token only. The operator has not published a full user-agent string, so match on the substring rather than an exact header.
Operator	Google
Purpose	Assistant fetchers
Respects robots.txt	Not documented
Verification method	None 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

Allow or block GoogleAgent-URLContext

Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.

Block GoogleAgent-URLContext

User-agent: GoogleAgent-URLContext
Disallow: /

Blocks every path for this crawler only.

Allow GoogleAgent-URLContext

User-agent: GoogleAgent-URLContext
Allow: /

Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.

Allow, except the pages you never want quoted

User-agent: GoogleAgent-URLContext
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /search

Edit the Disallow paths to match your own account, checkout and search URLs.

What blocking actually costs you

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.

Block every crawler in the directory at once

Verification

Is that really GoogleAgent-URLContext?

A user-agent header is a string the client chooses. Scrapers copy GoogleAgent-URLContext precisely because site owners allow it. 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.

Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.

Datacenter IP detectionNearly every real AI crawler egresses from cloud ranges. A residential IP claiming to be one is the first thing to check.IP reputation checkSee whether the address behind a fake crawler hit has a history of abuse elsewhere.Residential proxy detectionScrapers that get blocked by user agent often come back through residential proxy pools.

Other crawlers run by Google

Gemini-Deep-ResearchAssistant fetchers Google-AgentAutonomous agents Google-CloudVertexBotAutonomous agents Google-ExtendedTraining crawlers Google-FirebaseOther automated crawlers Google-Gemini-CLICoding agents

Related crawlers

Gemini-Deep-ResearchGoogle · Assistant fetchers Google-AgentGoogle · Autonomous agents Google-CloudVertexBotGoogle · Autonomous agents Amzn-UserAmazon · Assistant fetchers ChatGPT-UserOpenAI · Assistant fetchers

Agentscan

Identify crawlers automatically instead of by hand

Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.

How Agentscan works API reference Pricing What is my IP

FAQ