Google · User-triggered fetch
GoogleAgent-Mariner
- Operator
- Purpose
- User-triggered fetch (Plumb's classification)
- Verification
- Published IP ranges
- Follows robots.txt
- Not documented
01Identify and verify
How it shows up in your logs
User-agent contains
GoogleAgent-Mariner
Matching is case-insensitive. Anyone can send this string, so a match alone says only what the request claims to be.
Is it really GoogleAgent-Mariner?
Plumb checks the request IP against the operator's published ranges.
Ranges checked: google:user-fetchers, google:googlebot, google:special, google:user-fetchers-google
02Publishers
How major publishers treat it
Its robots.txt token is not documented, so the leaderboard cannot grade it.
03robots.txt
robots.txt token not documented
Google does not document a robots.txt token for GoogleAgent-Mariner, and the leaderboard does not grade one, so Plumb offers no rule to paste. A guessed name would match nothing and block nothing. To stop it, block its user agent at your CDN or firewall.
04Same operator
Google's other agents
- Google-AgentUser-triggered fetch
- Google-CloudVertexBotOther
- Googlebot-ExtendedAI search indexing
- Google-ExtendedModel training
- GoogleOtherOther
- GooglebotSearch engine