Gemini: user agent, purpose, and whether to allow it
Gemini is no longer in use. A robots.txt rule naming Gemini has no effect today. It was replaced by Google-Extended, which is the token to address instead.
There is no Gemini crawler. Google documents no standalone Gemini user agent or robots.txt token: Gemini is served by existing Google crawlers, and access is controlled with Google-Extended.
Specification
| Operator | |
|---|---|
| Purpose | Live fetchFetches a page in real time because a person asked. Traffic here tracks human interest, not a crawl schedule. |
| Agent kind | FetcherFetches on a person's request. Appears in your logs. Request volume follows human activity. |
| User agent | Not documented by Google. Kymo matches this agent on the token Gemini, observed in real logs rather than published in operator documentation. |
| robots.txt token | None. This agent cannot be addressed directly in robots.txt. |
| robots.txt compliance | No operator statement located |
| Verification | No published method, user agent is the only signal |
| Sends referral traffic | Yes |
| Attaches a citation | Yes |
| Status | Deprecated |
| Legacy Kymo category | ai_answer |
| Source | Observed in real logs, no operator documentation locatedGoogle publishes no crawler documentation that Kymo could locate. Everything on this page comes from observed traffic, not from a vendor page. |
| Verified on |
What blocking it costs you
A robots.txt rule naming Gemini has no effect, because no crawler answers to that token. Use Google-Extended to opt out of Gemini training and grounding. Kymo previously matched the bare string Gemini in user agents; that token was removed after it matched zero stored requests and because it is short enough to collide with unrelated strings.
Questions
What is the Gemini user agent?
Google documents the robots.txt token Gemini but does not publish a full user-agent string for it. Kymo records this agent from observation rather than from documentation.
Does Gemini respect robots.txt?
No operator statement located
What does blocking Gemini cost me?
A robots.txt rule naming Gemini has no effect, because no crawler answers to that token. Use Google-Extended to opt out of Gemini training and grounding. Kymo previously matched the bare string Gemini in user agents; that token was removed after it matched zero stored requests and because it is short enough to collide with unrelated strings.
Related crawlers
All AI crawlers and control tokens
See this bot in your own logs
Kymo classifies every crawler hit server-side using this registry, so Gemini shows up under Google with its purpose attached. Read how crawler detection works, or run a free free AI visibility check to see what each crawler currently gets back from your server. No account needed for the check.