Gemini-Deep-Research
Fetches sources when a Gemini user runs Deep Research. A user-triggered fetcher, so robots.txt rules generally aren't honored.
Reference reviewed by Sona
| Operator | |
|---|---|
| Powers | Gemini's Deep Research reports |
| Purpose | User-triggered fetch |
| User-agent token | Gemini-Deep-Research |
| Respects robots.txt | No (user-triggered) |
Gemini-Deep-Research is the fetcher behind Gemini's Deep Research feature - when a user commissions a research report, it gathers and scans the source pages the report reads and cites. Expect bursts of multi-page fetches driven by a single user request.
Google classifies it among its user-triggered fetchers, which its documentation says generally ignore robots.txt because a person initiated the request. To enforce a block, filter the user-agent at the server or firewall level rather than relying on robots.txt.
Allow Gemini-Deep-Research
Deep Research reports can read and cite your pages - high-value, high-intent exposure inside long-form research users act on.
User-agent: Gemini-Deep-Research Allow: /
Block Gemini-Deep-Research
You don't want agentic research traffic - but note a robots.txt rule alone won't stop it; enforce it in your WAF.
User-agent: Gemini-Deep-Research Disallow: /
Heads up: Gemini-Deep-Research does not reliably honor robots.txt. To enforce a block, combine the rule above with server- or firewall-level filtering of the user-agent.
Can Gemini-Deep-Research read your page right now?
Test any URL and see exactly what AI crawlers receive.