Gemini URL Context
Operated by Google
Quick Facts
- User-Agent:
- GoogleAgent-URLContext
- Category:
- AI & LLM Bots
- Operator:
- Safety:
- Safe
- Blocking Impact:
- Low - No SEO ranking impact
- SEO Impact Score:
- 2/10
- Official docs:
- None published by Google
- Named by:
- ai.robots.txt
Reported, not operator documented
Google has not published a crawler page that names GoogleAgent-URLContext. It is listed here because a credible public source does: ai.robots.txt. Reported Gemini URL-context token. Not on Google's published crawler lists.
What that means for you: the robots.txt rule on this page is the best available spelling, and a well-behaved crawler using this string will honour it, but there is no vendor statement of purpose, crawl rate or robots.txt compliance to rely on. Treat a matching request in your logs as a detection clue, not proof of who sent it, and combine the rule with a firewall rule if the traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.
What is Gemini URL Context?
Gemini URL Context is an on-demand AI fetcher operated by Google. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into Google's assistant.
Gemini URL Context is an on-demand AI fetcher operated by Google. It retrieves a page only when a user explicitly asks an AI assistant or agent to read, summarize, or act on a specific URL. Because it is triggered by real user intent rather than bulk crawling, blocking it mainly prevents users from pulling your content into Google's assistant.
Gemini URL Context uses the user-agent token GoogleAgent-URLContext. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.
What happens if you block Gemini URL Context?
User-agent / Disallow: / without any SEO penalty.Want to see whether Gemini URL Context actually visits you? Read how do I monitor AI bot traffic to my website?
How to block Gemini URL Context with robots.txt
<code>User-agent: GoogleAgent-URLContext</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Gemini URL Context safe to allow?
What does Gemini URL Context do?
Understanding Gemini URL Context's purpose helps you decide whether to allow or block it.
- Fetches a page only when a user asks an AI assistant to read it
- Summarizes or extracts the URL the user provided
- Triggered by real user intent, not bulk crawling
- Low traffic volume compared with training crawlers
- Blocking it prevents users from pulling your content into the assistant
Frequently Asked Questions
What user-agent string does Gemini URL Context use?
GoogleAgent-URLContext. That spelling comes from ai.robots.txt, not from Google, which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.Is Gemini URL Context safe?
Will blocking Gemini URL Context hurt my SEO?
User-agent / Disallow: / without any SEO penalty.How do I block Gemini URL Context in robots.txt?
/robots.txt file:User-agent: GoogleAgent-URLContext Disallow: /
This instructs Gemini URL Context not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does Gemini URL Context respect robots.txt?
GoogleAgent-URLContext will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.How do I verify if Gemini URL Context is crawling my site?
GoogleAgent-URLContext (for example grep -i "GoogleAgent-URLContext" /var/log/nginx/access.log). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that Google sent it.