Google-Gemini-CLI
Google-Gemini-CLI is an AI coding tool operated by Google. Developers use it to write, debug, or understand code, and it visits the web to fetch documentation, package metadata, code samples, or related references.
Visits are user-initiated. A developer types a question or pastes a URL and Google-Gemini-CLI retrieves it on their behalf. You will not see scheduled crawling, just bursts that follow user activity.
Allowing this agent makes your developer documentation available to a much larger audience than just the people who land on your site directly. Your docs end up inside the IDE.
See Google-Gemini-CLI on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
Verify by IP
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
Sometimes
IP verification
Published IP ranges
Crawl frequency
Burst, user-driven
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Google runs 103 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Link Unfurler
25- Google Feed Fetcher
- Google Image Proxy
- Google Publisher Center
- Google Web Preview
- Google-AdWords-Express
- Google-PageRenderer
- Google-Read-Aloud
- GoogleDocs
- GoogleImageProxy
- GoogleProducer
- Gmail Image Proxy
- Google Calendar Importer
- Google Page Renderer
- Google Web Snippet
- Google API
- Google Cloud Scheduler
- Google-Document-Conversion
- Google Sheets
- Google Slides
- Google Docs
- Google Area 120 Privacy Policy Fetcher
- Chrome Privacy Preserving Prefetch Proxy
- Google Cloud Function
- GoogleApps-DocumentScanner
- GoogleStackdriverMonitoring
Search Engine
14DevOps & Monitoring
13- Chrome-Lighthouse
- Google Inspection Tool
- Google Schema Markup Testing Tool
- Google Trust Services (DCV Check)
- Google-Structured-Data-Testing-Tool
- GoogleAssociationService
- ProjectShield Url Check
- Google Read Aloud
- Google Search Console
- Google Page Speed Insights
- Google Partner Monitoring
- Google Structured Data Testing Tool
- Google Stackdriver Monitoring
Ads Network Bot
11Training Crawler
9Agentic Browser
8Security Scanner
7SEO Crawler
4Brand Intelligence
3Shopping Bot
3Live-Fetch AI
2Ad Verification
2AI Coding Tool
1- Google-Gemini-CLIYou are here
Agentic Commerce
1Should I let Google-Gemini-CLI through?
In most cases, yes. Lets your developer documentation reach a much larger audience inside the IDE. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Google-Gemini-CLI affect my Google rankings?
No. Google-Gemini-CLI fetches a page only when a user is actively asking Google a question. It has nothing to do with how Google or Bing rank you. The cost of blocking is that Google can't quote your content in its answer.
How do I confirm a request is really from Google-Gemini-CLI?
Two checks. The User-Agent header should match a known Google-Gemini-CLI string, and the request's source IP should fall inside Google's published ranges. The User-Agent alone is trivially spoofable, so the IP check is what gives you confidence. Google publishes the ranges so you can validate at the CDN or edge.
Does a Google-Gemini-CLI visit count as a real user visit?
Sort of. There is a human asking Google a question on the other end, but they never load your page in their own browser. They see whatever Google quotes back, usually a snippet plus a citation link. Count it as upstream attention rather than as a session.
How is Google-Gemini-CLI different from Google's other bots?
Google splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Google family above to see which ones actually matter for your site.
What's the cleanest way to control Google-Gemini-CLI?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.