Subscribe

Google tells websites how to wave its AI agent past bot checks

New guidance asks sites to verify and admit Google-Agent, a fetcher acting for a person that Google says generally ignores robots.txt.

Google tells websites how to wave its AI agent past bot checks

Google has told website owners how to let its browsing agent through their defences, advising them to allow Google-Agent traffic in their content delivery network and, for verified requests, to "skip bot challenges". The guidance was updated on 17 November.

Google describes Google-Agent as the name used by agents on its infrastructure that browse the web and "perform actions upon user request". Sites verify a request by checking its IP address against a list Google publishes, and an experimental cryptographic method is also offered.

Google's guidance goes beyond opening webpages. It asks site owners to confirm that allowing the agent covers on-site search, filtering, product pages, adding to basket and booking, including the APIs behind those actions.

For retailers accustomed to blocking automated traffic, the question is changing. Some of that traffic may now be acting on behalf of genuine shoppers.

The control point is the firewall, not robots.txt. Google lists Google-Agent among its user-triggered fetchers, which it says "generally ignore robots.txt rules" because a person asked for the fetch. A site that wants to keep the agent out has to block it deliberately, and one that wants it in has to stop its own security tools getting in the way.

No word on who referred the sale

The update gives guidance for enabling access rather than requiring every site to allow it. It says nothing about what happens to referrals.

For affiliates, the concern is whether a sale still earns commission when an AI agent takes over the shopping journey. If someone reads a product review or clicks through a cashback site, then asks an agent to complete the purchase, the original affiliate cookie or referral ID may not follow into the agent's browsing session. The publisher could lose credit for a sale it helped influence.

For brands, that creates a measurement problem too. A sale completed through an agent may arrive without the affiliate referral that helped generate it, making the partner's contribution harder to recognise and reward. Other tracking methods could preserve that connection, but Google's guidance says nothing about attribution or which products use Google-Agent.

Hello Partner reported in February on agentic checkout arriving in Google Shopping.

Retailers can decide whether to admit verified Google-Agent traffic and ask their affiliate networks how referrals would be tracked if an agent subsequently completes a purchase.

Google has explained how to let its agent reach the basket. Whether an affiliate gets credit if that journey ends in a sale remains unanswered.

Newsdesk

Newsdesk

Daily news on partnerships, the creator economy and AI commerce from the Hello Partner team.

All articles

More in AI & Commerce

See all

More from Newsdesk

See all

From our partners