Gemini-Deep-Research
Gemini-Deep-Research is blocked by 312 sites in the October 2026 survey, or 5.1% of readable files. Its operator is unclear in the community reference.
Who runs Gemini-Deep-Research?
| Fact | Gemini-Deep-Research reference entry |
|---|---|
| Operator | “Unclear at this time.” |
| Purpose | “AI Assistants” |
| Does Gemini-Deep-Research obey robots.txt? | “Unclear at this time.” |
| Frequency | “Unclear at this time.” |
| Cloudflare managed list for Gemini-Deep-Research | No |
These facts quote the stored community ai.robots.txt reference.
“Gemini-Deep-Research is the agent responsible for collecting and scanning resources used in Google Gemini's Deep Research feature, which acts as a personal research assis…”
The stated role here is an AI assistant. Reading a page to answer a user has a different purpose from building a model with it. Owners may allow the requested visit.
How many sites block it?
Our readable sample has 312 whole-site blocks, 5.1% of 6,171 files, with Disallow: / as the instruction. Of that full sample, 108 name this crawler, or 1.8%. The count without a whole-site block is 5,859.
For the top 1,000 ranks, its name appears in 28 files out of 552, or 5.1%. Whole-site blocks total 59. Blocking is more common among the leading sites, at 10.7%. Lower in the ranking, blocking reaches 253 files out of 5,619, a 4.5% share.
| Readable files | Named by | Named share | Blocked by | Blocked share |
|---|---|---|---|---|
| Gemini-Deep-Research, all ranks | 108 | 1.8% | 312 | 5.1% |
| Gemini-Deep-Research, top 1,000 | 28 | 5.1% | 59 | 10.7% |
| Gemini-Deep-Research, remaining ranks | 80 | 1.4% | 253 | 4.5% |
Counts include a whole-site ban in a User-agent: * group if no named group overrides it. Of 312 blocks, 233 come only from that general rule, without naming this crawler. Names and bans overlap in 79 files. We also found 29 files with a name and no whole-site ban, plus 6,063 files omitting the name. Case changes and repeated spellings are merged.
Has that changed since August?
Between August and October, 15 sites that had blocked it stopped and 15 started, so the number blocking it is unchanged across the same 5,889 sites. A further 266 blocked it in both months, and 5,593 did so in neither. Keeping the sites the same lets us count changes in their rules.
August’s full sample had 303 blocks among 6,236 readable files. October’s was 312 among 6,171. Those monthly totals also reflect which files we could read on each visit.
| August to October | Files |
|---|---|
| Started blocking | 15 |
| Stopped blocking | 15 |
| Blocked in both | 266 |
| Blocked in neither | 5,593 |
| Net change | +0 |
How to block or allow it
Add these lines to robots.txt at your site root. For Gemini-Deep-Research, the robots.txt standard gives a named group priority over User-agent: *.
Block the whole site
User-agent: Gemini-Deep-Research
Disallow: /Allow access
User-agent: Gemini-Deep-Research
Allow: /It's the 58th most-named crawler of the 171 we counted in the crawler index.
How we counted
For Gemini-Deep-Research, the survey covered 10,000 top Tranco sites, collected on 19 October 2026. Files had an 8-second timeout and a 262,144-byte limit. Missing, unreachable and oversized files do not contribute to these shares. Reading files again used scripts/robots_2026_08_06.py (robots.py at app commit 07104ff) as well. See the full survey method.
Common questions
Does a User-agent line mean it is blocked?
This survey includes 29 files with the name and no whole-site ban, out of 108 naming files.
What do the top-ranked sites show?
Its name appears in 5.1% of readable leading files and 1.8% overall. Blocking affects 10.7% in the leading group and 5.1% in all ranks.
Which nearby entry can I compare?
SBIntuitionsBot is named by 107 files and blocked by 105, or 1.7%. For this crawler, 108 files name it and 312 block it, a 5.1% share.