Bot intelligence record

Google-Agent

Review first

Use the Google-Agent identifier to separate Google AI crawler, assistant, or AI search traffic from normal visitor requests in server logs.

Ai Ai Assistant Official Documented Confidence: High Verified: Yes robots.txt: No
Operator
Google
Family
Google
Type
Ai
Source type
Official
Last checked
2026-05-20

User-Agent Pattern

Google
Google-Agent
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy
No general robots.txt block is guaranteed; this is a user-triggered agent and may require server-side access controls.

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

Use this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.

AI crawling, assistant retrieval, AI search, or model-supporting discovery depending on the user-agent.

Record Details

Structured data
Operator
Google
Family
Google
Type
Ai
Purpose
Ai Assistant
Identity type
Official Documented
Confidence
High
Last verified
2026-04-01
Last checked
2026-05-20
Source type
Official
Verification
Verify as a Google user-triggered agent using reverse DNS and Google's published user-triggered agent IP ranges.
Spoofing risk
User-agent strings for Google-Agent can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.

Notes

Google-Agent is listed in the Botcrawl directory as an AI fetcher from Google. The primary identifier for log review is Google-Agent.

Identification

  • User-agent pattern: Google-Agent
  • Family: Google
  • Type: AI
  • Kind: Fetcher

Common use

AI crawling, assistant retrieval, AI search, or model-supporting discovery depending on the user-agent.

Verification and handling

Verify as a Google user-triggered agent using reverse DNS and Google's published user-triggered agent IP ranges.

Directory guidance marks the risk level as Neutral and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Verify as a Google user-triggered agent using reverse DNS and Google's published user-triggered agent IP ranges.
  • Match `Google-Agent` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • AI crawling, assistant retrieval, AI search, or model-supporting discovery depending on the user-agent.
  • User-agent strings for Google-Agent can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.