Does GoogleAgent-Mariner respect robots.txt?

Not documented. No operator statement says whether GoogleAgent-Mariner reads robots.txt, so add the rule but verify in your logs that the requests actually stop.

How do I block GoogleAgent-Mariner?

Add the GoogleAgent-Mariner token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.

IPScanner

Autonomous agents

GoogleAgent-Mariner

Q: How do I verify a request really came from GoogleAgent-Mariner?

You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.

GoogleAgent-Mariner is a bot operated by Google that browses the web on its own to finish multi-step tasks. GoogleAgent-Mariner is an AI agent created by Google that can use a web browser. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.

GoogleAgent-Mariner at a glance

Reference data for the GoogleAgent-Mariner crawler
User agent	`GoogleAgent-Mariner` Token only. The operator has not published a full user-agent string, so match on the substring rather than an exact header.
Operator	Google
Purpose	Autonomous agents
Respects robots.txt	Not documented
Verification method	None published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof.
Crawl pattern	Not published
Robots.txt tokens	`GoogleAgent-Mariner`
Operator documentation	https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers

GoogleAgent-Mariner is an AI agent created by Google that can use a web browser. It can intelligently navigate and interact with websites to complete multi-step tasks on …

robots.txt

Allow or block GoogleAgent-Mariner

Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.

Block GoogleAgent-Mariner

User-agent: GoogleAgent-Mariner
Disallow: /

Blocks every path for this crawler only.

Allow GoogleAgent-Mariner

User-agent: GoogleAgent-Mariner
Allow: /

Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.

Allow, except the pages you never want quoted

User-agent: GoogleAgent-Mariner
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /search

Edit the Disallow paths to match your own account, checkout and search URLs.

What blocking actually costs you

Blocking GoogleAgent-Mariner stops automated sessions that fill forms, click through flows and read pages the way a logged-in user would. Rate limits and challenges usually work better here than a robots.txt line.

Block every crawler in the directory at once

Verification

Is that really GoogleAgent-Mariner?

A user-agent header is a string the client chooses. Scrapers copy GoogleAgent-Mariner precisely because site owners allow it. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof.

Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.

Datacenter IP detectionNearly every real AI crawler egresses from cloud ranges. A residential IP claiming to be one is the first thing to check.IP reputation checkSee whether the address behind a fake crawler hit has a history of abuse elsewhere.Residential proxy detectionScrapers that get blocked by user agent often come back through residential proxy pools.

Other crawlers run by Google

Gemini-Deep-ResearchAssistant fetchers Google-AgentAutonomous agents Google-CloudVertexBotAutonomous agents Google-ExtendedTraining crawlers Google-FirebaseOther automated crawlers Google-Gemini-CLICoding agents

Related crawlers

Gemini-Deep-ResearchGoogle · Assistant fetchers Google-AgentGoogle · Autonomous agents Google-CloudVertexBotGoogle · Autonomous agents ChatGPT AgentOpenAI · Autonomous agents Claude-WebAnthropic · Autonomous agents

Agentscan

Identify crawlers automatically instead of by hand

Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.

How Agentscan works API reference Pricing What is my IP

FAQ