GoogleAgent-Mariner

AI Browser Agent

Operated by Google

Last updated:

Monitor

Autonomous AI agent, relatively new category with evolving behavior.

Recommended action: Monitor activity patterns and review regularly.

Category

AI Browser Agent

Primary use case

Autonomous web tasks

Trust level

Review recommended

robots.txt

Unknown

GoogleAgent-Mariner Traffic (Last 90 Days)

Not enough network data yet.

Track this bot on your site

What is GoogleAgent-Mariner?

AI Agent bot

What GoogleAgent-Mariner means for your site

GoogleAgent-Mariner is an autonomous AI agent that browses the web using a real browser, operated by Google. Unlike traditional crawlers, it can interact with your pages like a human, navigating links, reading content, and completing multi-step tasks. This is a new and rapidly evolving category of web visitors.

What should you do?

  • Monitor activity patterns to understand what the agent does on your site
  • Review which pages the agent visits most frequently
  • Note: may not respect robots.txt, server-side rules needed for blocking
  • Keep an eye on form submissions or interactive behavior

See GoogleAgent-Mariner on your own site

BotSights tracks every GoogleAgent-Mariner visit in real time, including which pages it crawls, how often, and from where.

Start free

How to identify GoogleAgent-Mariner

GoogleAgent-Mariner uses the user-agent "googleagent-mariner" and robots.txt compliance unconfirmed. AI browser agents may behave more like humans than traditional bots.

googleagent-marinerGoogleAgent-Mariner

How to block GoogleAgent-Mariner

Three robots.txt options below. Pick the one that matches your goal. Each snippet lists every known GoogleAgent-Mariner user-agent pattern so the rules apply regardless of which one the bot announces. Compliance with robots.txt is unconfirmed for GoogleAgent-Mariner, so verify with crawl logs after deploying.

Edit robots.txt with care

A single misplaced line can de-index your entire site. Common mistake: pasting User-agent: * followed by Disallow: / blocks every bot, not just GoogleAgent-Mariner, including Googlebot. Always paste the snippet between existing rules (not over them), keep the User-agent line scoped to GoogleAgent-Mariner's patterns, and verify with Google's robots.txt tester before deploying. If you are not sure, ask a developer first.

Option 1: Block all access

Tells GoogleAgent-Mariner not to crawl any URL on your site. Use this when you want the bot completely off your content.

User-agent: googleagent-mariner
User-agent: GoogleAgent-Mariner
Disallow: /

Option 2: Block specific paths only

Keep public content crawlable but exclude sensitive or non-public sections. Add one Disallow: line per path. Replace the example paths with your own.

User-agent: googleagent-mariner
User-agent: GoogleAgent-Mariner
Disallow: /admin/
Disallow: /private/
Disallow: /checkout/

Option 3: Slow down with a crawl delay

Crawl-delay is a voluntary directive that asks the bot to wait the given number of seconds between requests. Useful when GoogleAgent-Mariner is hammering your origin and slowing the site down for real visitors, but you do not want to block it outright. The value is in seconds, so 10 means at most one request every ten seconds. Not all bots honour this directive (Googlebot ignores it; Bingbot, Yandex, and many AI crawlers do respect it).

User-agent: googleagent-mariner
User-agent: GoogleAgent-Mariner
Crawl-delay: 10

Frequently Asked Questions

What is the User-Agent for GoogleAgent-Mariner?

GoogleAgent-Mariner identifies itself with the User-Agent string "googleagent-mariner" (alternate forms: GoogleAgent-Mariner). AI browser agents may use a real browser engine (Chromium-based), so the UA can look human at first glance — check for the operator-specific marker.

Is GoogleAgent-Mariner a real user?

No. GoogleAgent-Mariner is an AI agent acting on behalf of a human user. It browses autonomously using a real browser, often clicking links and reading content like a person would, but the navigation decisions are made by an AI, not the user directly.

Should I treat GoogleAgent-Mariner as a human or as a bot?

Technically a bot — count it separately in analytics. But treat it like a high-intent visitor, since each visit represents a real human task being executed on their behalf. GoogleAgent-Mariner sessions often correlate with research, comparison, or buying intent.

Will GoogleAgent-Mariner fill out forms or trigger conversions?

Possibly. AI browser agents can interact with forms, click buttons, and complete checkouts when instructed. Monitor your conversion funnels for unusual patterns and consider extra verification (CAPTCHA, rate limiting) on critical actions.

Should I block GoogleAgent-Mariner?

Monitor first. AI browser agents are a new and rapidly evolving category — many provide real user-on-behalf-of value (research, shopping, scheduling). Block only if you see unwanted behavior like form spam, scraping at scale, or terms-of-service violations.

How do I tell GoogleAgent-Mariner apart from a real user in analytics?

Server logs show the User-Agent. GoogleAgent-Mariner UA is "googleagent-mariner". BotSights detects this and flags it separately from human visits, so your conversion-rate calculations stay clean.

Monitor AI agents browsing your site

AI agents navigate your site autonomously. Track which pages they visit, how they interact, and whether the activity is useful.

  • Real-time AI agent detection
  • Page-level activity monitoring
  • Understand a new kind of web visitor
Monitor AI agents

Free plan available. No credit card required. Setup in 2 minutes.