Google-Agent user agent identifies AI agent traffic in server logs

Google launched a brand new person agent, known as Google-Agent, that alerts when AI brokers act on customers’ behalf, marking an early shift towards agent-driven internet interactions.

What occurred. Google added Google-Agent to its listing of user-triggered fetchers on March 20 and has begun a gradual rollout.

• The Google-Agent person agent identifies requests made by AI brokers operating on Google infrastructure, together with experimental instruments like Undertaking Mariner.

The way it works. Google-Agent seems in HTTP requests when an AI agent visits a web site to finish a user-initiated job.

• Instance use instances embrace looking pages, evaluating content material, or taking actions similar to submitting kinds.
• This differs from Googlebot and different crawlers, which run repeatedly within the background with out direct person prompts.

IP ranges. Google shared the IP ranges for its desktop agent:

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; appropriate; Google-Agent; +https://builders.google.com/crawling/docs/crawlers-fetchers/google-agent) Chrome/W.X.Y.Z Safari/537.36

And the IP ranges for its cell agent:

Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Construct/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Cell Safari/537.36 (appropriate; Google-Agent; +https://builders.google.com/crawling/docs/crawlers-fetchers/google-agent)

Why we care. This allows you to determine agent-driven visitors in server logs. Now you can distinguish conventional crawl exercise from visits triggered by actual customers by AI brokers. That ought to make it easier to observe agent-assisted conversions, perceive rising person conduct, and put together for agentic search.

What they’re saying. In line with Google’s announcement:

• “The Google-Agent person agent is rolling out over the subsequent few weeks, and can be utilized by Google brokers hosted on Google infrastructure to navigate the online and carry out actions upon person request.”

What to look at. Early volumes can be low because the rollout continues, however now could be the time to determine a baseline. What to do:

• Monitor logs for Google-Agent exercise.
• Be certain that CDNs and WAFs aren’t blocking the revealed IP ranges.
• Validate that key web site actions, together with kinds and flows, work for automated brokers.

Dig deeper. Google’s releasing Google-Agent: Here’s what to know