Project Mariner (Google-Agent): What SEO Professionals Need to Know

I almost missed the Project Mariner rollout. On March 20, 2026, Google slipped a new entry into its crawler docs: Google-Agent. No blog post fanfare, no developer conference keynote. Just a quiet documentation update that signals a massive shift in how the web works.

Google-Agent isn't a crawler. It's an AI that browses websites and does things: clicks buttons, fills forms, compares prices. On behalf of real users. That's a fundamentally different kind of web traffic, and most sites aren't ready for it.

What is Google-Agent?

Google-Agent is the user-agent string for AI agents running on Google's infrastructure. These agents visit websites, click buttons, fill out forms, and complete tasks, all directed by a human user through Project Mariner, Google's AI research prototype built into Chrome.

Picture this: someone tells their AI assistant "find me the cheapest flight to Lisbon next Thursday." The AI needs to visit airline sites, compare prices, maybe even start a booking. Google-Agent is the identity it uses while doing that. It's not indexing your content. It's using your site the way a human would, just faster.

How it differs from Googlebot and Google-Extended

Google now has three crawlers, and they serve very different purposes:

• Googlebot: The classic indexing crawler. Block it and you disappear from search results. Simple.
• Google-Extended: Feeds content to Gemini and Vertex AI for training. Blocking it keeps your content out of Google's AI models but doesn't touch your rankings.
• Google-Agent: Acts on behalf of a specific person. It visits your site to do something (compare prices, read an article, start a purchase). User-triggered, not automated.

Here's why this matters: Google-Agent is someone who wants to interact with your business right now. Blocking it is like telling a customer's personal shopper they can't enter your store.

What this means for your website

The answer depends on what your site does, but for most businesses, the implications are big.

E-commerce and service businesses

This is where it gets interesting. If someone's AI agent is comparison-shopping across five sites and yours blocks it, you just lost that sale to a competitor. I expect AI-assisted purchases to account for a meaningful share of e-commerce transactions within 12 months.

Content publishers

AI agents reading your articles for a specific user is fundamentally different from AI training. It's closer to a screen reader or a browser extension that summarizes pages. Blocking it means a real person can't access your content through their preferred tool.

Privacy-sensitive sites

Banks, healthcare providers, government portals: you'll want to think carefully about what AI agents should and shouldn't access. The good news: Google-Agent respects robots.txt, so you have granular control over which paths are open.

How to prepare your site

Three things to do this week, none of them take more than 10 minutes.

1. Check your robots.txt

I've seen this on dozens of sites: a broad wildcard rule that blocks all bots except Googlebot. Google-Agent gets caught in that net. Check yours now. You might be blocking it without knowing.

# Allow Google-Agent (recommended for most sites)
User-agent: Google-Agent
Allow: /

# Block if needed (for sensitive areas)
User-agent: Google-Agent
Disallow: /admin/
Disallow: /api/

Use the Lumina Crawler Access Checker to check your current configuration.

2. Monitor your server logs

Start watching for the Google-Agent user-agent string. Traffic will be low right now since Project Mariner is still rolling out. But when it scales, you'll want baseline data to compare against.

3. Review your WAF/CDN rules

Cloudflare, AWS WAF, Sucuri: if you use any bot protection, double-check that Google-Agent isn't getting blocked. Google publishes its IP ranges in user-triggered-agents.json, so you can allowlist them explicitly.

What is Google Project Mariner?

Before you see Google-Agent in your logs, a user has to activate Project Mariner on their end. Mariner is Google's Chrome-based AI agent prototype: you tell it what you want in natural language, and it navigates the web to complete the task. Google first showed it publicly in December 2024 and has been expanding access in phases ever since.

How to access Google Project Mariner

Access is limited. Google announced Project Mariner in December 2024 and has been expanding it through a waitlist ever since. The path in runs through a Google AI subscription plan that includes Labs access. Even then, availability varies by region, and no public API exists yet.

Project Mariner security and privacy implications

Security is the real question nobody has fully answered yet. A Google-branded agent that clicks buttons and submits forms has enormous power over any session it's authenticated into. Google says the agent runs inside the user's own Chrome instance and uses existing cookies, which keeps credentials on the device. The obvious attack surface is prompt injection: a malicious page could try to hijack the agent's instructions. Google has talked about confirming destructive actions with the user, but the full threat model is still being worked out.

The bigger picture: the agentic web

Google-Agent isn't arriving in isolation. OpenAI already has ChatGPT-User and OAI-SearchBot. Anthropic ships Claude-User. Every major AI lab is building agents that browse the web for people. The pattern is unmistakable.

What's emerging is a new layer of web traffic: not bots, not humans, but AI acting on behalf of humans. Sites that work well with these agents will win twice: better visibility in AI-powered search results, and more conversions from AI-assisted tasks.

This is the core of what I've been calling Generative Engine Optimization (GEO): making your site work for search engines and for AI systems that actively use it. The sites that figure this out first will have a real edge for years.