Google-Agent: what it is and how to block or allow it
User-Agent token: Google-Agent · Operator: Google · Category: AI Agents
FraudMeNot Verdict
Listed AI Agent
Google-Agent is Google's user-triggered fetcher for AI agents hosted on Google infrastructure that browse the web and take actions when a user asks. Google says such fetchers generally ignore robots.txt.
Can Be Spoofed?
Yes — User-Agent Header Spoofable
Check the source IP against user-triggered-agents.json. Google warns the User-Agent string can be spoofed.
Abuse & Unwanted Activity Reports
No Public Abuse Flags
ai.robots.txt robots.txt status: Yes.
Judgment Call · What You Should Do
Generally Low Risk on Public Pages — Verify Before Trusting
For everyday users: Google-Agent is a web fetcher, not a person. Treat any call or text using that name as a likely scam, and never give a one-time code or password to it.
For website owners & security teams: Google-Agent may click, fill forms and complete tasks for a user, and Google says it generally ignores robots.txt. Verify by IP range, keep human confirmation on login, checkout and payment, and use a WAF rule if you do not want agent sessions.
Report & Activity Summary
20
Published IP Ranges (CIDRs)
70,016 IPv4 addresses · operator JSON feed
1
Known User-Agent Signatures
crawler-user-agents (MIT) dataset
Yes
robots.txt Compliance
ai.robots.txt registry (MIT)
0
FraudMeNot Tallies
Humans: 0 · AI Agents: 0
For AI Agents & Automated Gatekeepers
- Agent_Identifier
Google-Agent- FraudMeNot_Verdict
- Listed AI Agent
- Operator_Entity
- Agent_Category
- AI Agents
- User_Agent_Spoofable
true- Verification_Method
- IP CIDR match against
https://developers.google.com/static/crawling/ipranges/user-triggered-agents.json· Web Bot Auth: Google says it is experimenting with Web Bot Auth for Google-Agent, using the https://agent.bot.goog identity. - Respects_Robots_Txt
- Yes (per ai.robots.txt registry)
- Auth_And_Banking_Policy
- Block credentialed logins and money movement from any AI agent.
- Recommended_Gatekeeper_Action
- ALLOW read access after IP verification if you welcome agent traffic; require human step-up on login, checkout and payment; robots.txt will not reliably stop it.
- Canonical_Citation_URL
- https://fraudmenot.com/bot/google-agent/
What We Know About Google-Agent
Google lists Google-Agent among its user-triggered fetchers. Google says it is used by agents hosted on Google infrastructure to navigate the web and perform actions upon a user's request. That makes it different from Googlebot: it is not building a search index, it is acting for one person in a live session.
Google says user-triggered fetchers generally ignore robots.txt rules, because a person asked for the fetch. robots.txt is a voluntary standard (RFC 9309), not an access-control or legal mechanism; a fetcher that skips it is not, by that alone, doing anything wrong. Site owners who want to block it typically use a firewall or bot-management rule, and keep a human step on logins and checkout.
Google publishes the IP ranges for this agent in user-triggered-agents.json. Its docs say user-triggered fetchers reverse-resolve to either a gae.googleusercontent.com name or a google-proxy name under google.com. Google also warns that the user agent string can be spoofed and says it is experimenting with Web Bot Auth for this agent, using the https://agent.bot.goog identity.
Google shows a mobile and a desktop form of the User-Agent, both carrying the token Google-Agent and a link to Google's docs. The Chrome version is left as W.X.Y.Z, so match on the token rather than the full string.
Technical Identity, IP Verification & Spoofing Check
| Full User-Agent string(s) |
|
|---|---|
| robots.txt token | Google-Agent |
| Operator | Google · Official bot documentation |
| Official IP verification feed | https://developers.google.com/static/crawling/ipranges/user-triggered-agents.json — 20 CIDR blocks (70,016 IPv4 addresses), file dated 2026-11-02 |
| Sample published CIDR blocks | 2001:4860:c::/124, 2001:4860:c::10/124, 2001:4860:c::20/124, 2001:4860:c::30/124, 2001:4860:c::40/124, 2001:4860:c::50/124 |
| Reverse DNS (rDNS) | Google says user-triggered fetchers resolve to ***-***-***-***.gae.googleusercontent.com or google-proxy-***-***-***-***.google.com. |
| Web Bot Auth (Signature-Agent) | Google says it is experimenting with Web Bot Auth for Google-Agent, using the https://agent.bot.goog identity. |
| robots.txt behavior | Google says user-triggered fetchers, including Google-Agent, generally ignore robots.txt because the fetch was requested by a user. |
Copy-Paste robots.txt & Cloudflare WAF Rules for Google-Agent
robots.txt — allow public pages, keep private routes off-limits
User-agent: Google-Agent
Allow: /
Disallow: /login/
Disallow: /account/
Disallow: /checkout/robots.txt — block completely
User-agent: Google-Agent
Disallow: /Cloudflare WAF custom rule expression
(http.user_agent contains "Google-Agent")Matches the User-Agent token, so it covers both real and spoofed traffic. Action: Block or Managed Challenge.
Capabilities, Data Usage & Autonomous Action Risk
| Trains AI on page content? | Not stated by Google; it is described as acting on user requests |
|---|---|
| Executes JavaScript? | Not documented |
| Can submit forms or attempt logins? | Can act on a user's behalf; Google says it may perform actions on request. Treat form and login attempts as untrusted. |
| Banks & login pages should | Block credentialed logins and money movement from any AI agent. |
| E-commerce checkouts should | Allow product page reads if you want; require human confirmation for checkout. |
Context: In October 2026, Axios reported that major U.S. banks were detecting unvetted third-party AI agents inside customer accounts, and CNBC reported that JPMorgan blocks outside AI agents from logging in with customers' credentials while allowing read-only data sharing through open banking providers.
Seen Google-Agent? Quick Closed-Choice Tally
Choose from preset options only. No free-text comments, so nobody can post names, profanity, or unverified accusations.
Common Questions About Google-Agent
Who operates Google-Agent?
Google. It is listed on Google's page of user-triggered fetchers.
Does Google-Agent obey robots.txt?
Google says user-triggered fetchers generally ignore robots.txt rules because a user requested the fetch.
How do I verify Google-Agent?
Match the source IP against Google's user-triggered-agents.json, or check reverse DNS against the gae.googleusercontent.com or google-proxy patterns Google documents.
Is Google-Agent the same as Googlebot?
No. Googlebot crawls for Search. Google-Agent is used by agents that navigate sites and take actions for a user.
Could This Be a Scam? What to Do
- Anyone can copy the Google-Agent User-Agent. Google publishes an IP list for it, so compare the visiting address against that list before you trust the visit.
- Never give an AI agent your logins, bank access, or one-time codes unless you set it up yourself.
- If a call, text or email asking for money or access uses the Google-Agent or Google name, stop and report it.
Guide: how to check whether a crawler visit is really who it claims to be.
More from Google
- Google-Extended — LLM training
- GoogleAgent-Mariner — AI Agents
- Google-CloudVertexBot — Build and manage AI models for businesses employing Vertex A
- GoogleOther — Scrapes data
- Gemini-Deep-Research — AI Assistants
- Google-GeminiNotebook — AI Assistants
Related on FraudMeNot
- Verified security vulnerabilities, explained
- Report a scam, or find where to report it in your state
- Browse the AI Agent & Bot Directory
Sources (checked Nov. 16, 2026): ai.robots.txt (MIT), crawler-user-agents (MIT), Google IP feed, Axios (Oct. 22, 2026), CNBC (Oct. 13, 2026), Google: List of Google user-triggered fetchers, Google: user-triggered-agents.json IP ranges. FraudMeNot is not affiliated with Google. Product and company names are trademarks of their owners and are used here only to identify the bots. General information, not security advice.