Bot intelligence record
GoogleAgent-Mariner
Review firstClaimed Google Project Mariner user-agent token for agentic browser activity.
- Operator
- Family
- Google Mariner
- Type
- Ai
- Source type
- Observed
- Last checked
- 2026-06-02
User-Agent Pattern
GoogleGoogleAgent-Mariner
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 copyUser-agent: GoogleAgent-Mariner Disallow: /
Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
Claimed user-agent token for Google Project Mariner or related agentic browsing activity.
Record Details
Structured data- Operator
- Family
- Google Mariner
- Type
- Ai
- Purpose
- Agentic Browsing
- Identity type
- Observed
- Confidence
- Low
- Last verified
- 2026-06-02
- Last checked
- 2026-06-02
- Source type
- Observed
- Verification
- Low-confidence record. Google documents Google-Agent and common crawlers, but this exact token should be verified against current Google documentation or server logs.
- Spoofing risk
- User-agent strings can be spoofed. Pair the claimed identifier with operator documentation, IP verification, reverse DNS, signatures, or other available trust signals before creating low-friction allow rules.
Notes
GoogleAgent-Mariner is listed in the Botcrawl directory as a ai bot from Google Mariner. The primary identifier for log review is GoogleAgent-Mariner.
Identification
- User-agent pattern:
GoogleAgent-Mariner - Family: Google Mariner
- Type: Ai
- Kind: Agent
Common use
Claimed user-agent token for Google Project Mariner or related agentic browsing activity.
Verification and handling
Confirm the user-agent against server logs and use published operator documentation, IP ranges, reverse DNS, signatures, or other trust signals when available.
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: Unknown.
Evidence and Source
- Low-confidence record. Google documents Google-Agent and common crawlers, but this exact token should be verified against current Google documentation or server logs.
- Match `GoogleAgent-Mariner` as a case-insensitive substring in HTTP user-agent logs. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Claimed user-agent token for Google Project Mariner or related agentic browsing activity.
- User-agent strings can be spoofed. Pair the claimed identifier with operator documentation, IP verification, reverse DNS, signatures, or other available trust signals before creating low-friction allow rules.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.
