Safe Reported Google Bots

Gemini-Deep-Research

Operated by Google

Quick Facts

User-Agent:
Gemini-Deep-Research
Category:
Google Bots
Operator:
Google
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
None published by Google
Evidence:
Verified by AI Crawler Check: in 108 top-10k robots.txt files

Reported, not operator documented

Google has not published a crawler page that names Gemini-Deep-Research. It is listed here on our own evidence. Verified by AI Crawler Check: 108 of the 5,583 valid robots.txt files in the Tranco top 10,000 carry a rule for Gemini-Deep-Research, so site owners treat it as a real crawler name (how we measure this). That proves the spelling is in use, not who sends it. Reported Gemini Deep Research agent token. Not on Google's published crawler lists.

What that means for you: the Gemini-Deep-Research rule on this page is the best available spelling, but Google has made no statement of purpose, crawl rate or robots.txt compliance. Treat a Gemini-Deep-Research request in your logs as a clue, not proof of who sent it, and add a firewall rule if that traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.

What is Gemini-Deep-Research?

Gemini-Deep-Research 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-Deep-Research 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-Deep-Research uses the user-agent token Gemini-Deep-Research. 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-Deep-Research?

🔶 AI Visibility Trade-off - Blocking Gemini-Deep-Research will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
Generally safe to allow; provides legitimate crawling value.

How to block Gemini-Deep-Research with robots.txt

<code>User-agent: Gemini-Deep-Research</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: Gemini-Deep-Research Disallow: /
Allow all (robots.txt)
User-agent: Gemini-Deep-Research Allow: /
Block private only (robots.txt)
User-agent: Gemini-Deep-Research Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Gemini-Deep-Research if ($http_user_agent ~* "Gemini-Deep-Research") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Gemini-Deep-Research SetEnvIfNoCase User-Agent "Gemini-Deep-Research" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Gemini-Deep-Research safe to allow?

Gemini-Deep-Research is rated Safe in this directory, meaning there are no credible public reports of abusive crawling under this name. It is a Reported token: Google has not published documentation for it, so its purpose, crawl rate and robots.txt behaviour are not confirmed by the operator, and anyone can send the same user-agent string. Allow or block it on its stated purpose, and back the robots.txt rule with a firewall rule if the traffic matters to you.
Google publishes no IP ranges or reverse-DNS pattern for Gemini-Deep-Research, so the user-agent string cannot be verified. Rate-limit unusual volume instead of trusting the name.

What does Gemini-Deep-Research do?

Understanding Gemini-Deep-Research'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

Gemini-Deep-Research in context

Gemini-Deep-Research is a user-triggered agent operated by Google. In plain terms, it fetches a page when a person asks an assistant or app to open it. Our database files it under Google crawlers and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 20 of the 24 Google crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is critical. So Gemini-Deep-Research is both well behaved and costly to lose: the strongest case for allowing it. How we rate safety and impact.

How site owners treat Gemini-Deep-Research

In our own scan of the Tranco top 10,000 (5,583 valid robots.txt files), 108 files (1.9%) name Gemini-Deep-Research in a User-agent line. That shows site owners treat the token as a real crawler worth a rule. It does not, on its own, prove who operates it.

Does it follow robots.txt?

Gemini-Deep-Research's operator does not clearly document how it treats robots.txt. Write the Gemini-Deep-Research rule anyway, then confirm in your logs that its requests stop.

Google crawlers and close alternatives

Gemini-Deep-Research is one of 32 Google crawlers in our database. A User-agent: Gemini-Deep-Research group controls Gemini-Deep-Research only; the other Google tokens below need their own lines.

  • Gemini-Deep-Research: this crawler (Tier 3)
  • AdsBot-Google: Google Ads Quality (Desktop), checks pages for an SEO, uptime or analytics service (Tier 3)
  • AdsBot-Google-Mobile: Google Ads Quality (Mobile), checks pages for an SEO, uptime or analytics service (Tier 3)
  • APIs-Google: APIs-Google, fetches a page when a person asks an assistant or app to open it (Tier 3)
  • Chrome-Lighthouse: Lighthouse Audit, checks pages for an SEO, uptime or analytics service (Tier 4)
  • FeedFetcher-Google: Google Feed Fetcher, builds a search or answer index (Tier 3)
  • Google-Agent: Google Agent (Project Mariner), fetches a page when a person asks an assistant or app to open it (Tier 2)
  • Google-CloudVertexBot: Google Vertex AI, fetches a page when a person asks an assistant or app to open it (Tier 3)
  • Google-CWS: Chrome Web Store Fetcher, checks pages for an SEO, uptime or analytics service (Tier 4)

To give Gemini-Deep-Research the same answer as its siblings, stack User-agent: Gemini-Deep-Research with their lines above one set of rules; to treat Gemini-Deep-Research differently, give it its own group.

No other crawler in our Google crawlers category has exactly the same purpose, which makes Gemini-Deep-Research an unusual case: decide about it on its own merits.

We first recorded Gemini-Deep-Research on March 17, 2026. We could not find a page where Google names it, so treat the token as reported rather than documented.

Which rule Gemini-Deep-Research actually follows

Gemini-Deep-Research reads exactly one group in robots.txt, the most specific one that names Gemini-Deep-Research, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Gemini-Deep-Research
Disallow: /drafts/
  1. Find the group. Gemini-Deep-Research looks for a group naming Gemini-Deep-Research. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Gemini-Deep-Research, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Gemini-Deep-Research if the file also has a User-agent: Gemini-Deep-Research group?

No. Once a group names it, Gemini-Deep-Research reads only that group. Put every rule you want it to follow inside its own group.

Related: how AI engines choose their sources

Test yourself: will blocking Gemini-Deep-Research remove your pages from AI answers?

Often, yes. Gemini-Deep-Research is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: gemini-deep-research the same as User-agent: Gemini-Deep-Research?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Gemini-Deep-Research? Decide by situation

Recommended setting for Gemini-Deep-Research by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. Gemini-Deep-Research fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI trainingBlocking it does not stop training, because Gemini-Deep-Research is a user-triggered agent. Block the operator's training crawler instead.
You run an online shopAllow it unless it is overloading your servers.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Gemini-Deep-Research on your own site

  1. Open /robots.txt on your domain and search for Gemini-Deep-Research. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Gemini-Deep-Research follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Gemini-Deep-Research even when robots.txt allows it, and that never shows in the file.
  4. Run our AI search visibility check to see how Gemini-Deep-Research and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Gemini-Deep-Research

The errors we see most often with Gemini-Deep-Research in the files and firewalls we test:

  1. Assuming a robots.txt rule will stop Gemini-Deep-Research. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
  2. Blocking Gemini-Deep-Research as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
  3. Counting Gemini-Deep-Research visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check Gemini-Deep-Research from outside after every change.

Spotting Gemini-Deep-Research in your logs

robots.txt says what Gemini-Deep-Research may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "Gemini-Deep-Research" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "Gemini-Deep-Research" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Gemini-Deep-Research user-agent, so confirm the source before acting on a match:

  • Gemini-Deep-Research: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Gemini-Deep-Research request with caution.

Frequently Asked Questions

What user-agent string does Gemini-Deep-Research use?
Gemini-Deep-Research is reported to identify itself with Gemini-Deep-Research. Evidence that the spelling is in real use comes from our own robots.txt study: 108 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), 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-Deep-Research safe?
Gemini-Deep-Research is rated Safe in this directory, meaning there are no credible public reports of abusive crawling under this name. It is a Reported token: Google has not published documentation for it, so its purpose, crawl rate and robots.txt behaviour are not confirmed by the operator, and anyone can send the same user-agent string. Allow or block it on its stated purpose, and back the robots.txt rule with a firewall rule if the traffic matters to you.
Will blocking Gemini-Deep-Research hurt my SEO?
🔶 AI Visibility Trade-off - Blocking Gemini-Deep-Research will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
How do I block Gemini-Deep-Research in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: Gemini-Deep-Research
Disallow: /

This instructs Gemini-Deep-Research not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Gemini-Deep-Research respect robots.txt?
Not documented. Google has published no statement that Gemini-Deep-Research reads robots.txt. A rule for Gemini-Deep-Research 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-Deep-Research is crawling my site?
Search your access logs for Gemini-Deep-Research (for example grep -i "Gemini-Deep-Research" /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.

Related Bots

WhatsApp us