Google-Agent guide explains how to admit verified agents

Google has published a guide for sites that want to admit Google-Agent traffic through their firewall or bot protection. Its 17 November documentation changelog confirms the new guidance. The…

SSophie Harrington1 min read

Google has published a guide for sites that want to admit Google-Agent traffic through their firewall or bot protection. Its 17 November documentation changelog confirms the new guidance. The practical distinction is between verifying an assistant and trusting a name in a request header.

Verify the request before skipping challenges

The official guide combines a User-Agent containing Google-Agent with an address from Google’s published user-triggered agent IP list. Some requests also carry experimental Web Bot Auth signatures, which should be verified when present. A User-Agent string alone is not the prescribed check.

Google recommends reviewing rule priority, interactive challenges, the full navigation path and underlying APIs, shared-IP limits, IP-list updates and preservation of headers through proxies. Allowing the homepage while challenging search or add-to-cart can still interrupt the task.

Keep the permission narrow

For a merchant or app team that controls a CDN, headless frontend or app endpoint, our recommendation is to ask the service provider to show how it verifies Google-Agent before granting an exception. Keep a record of the rule, its owner and the test that demonstrated the problem.

Verification identifies the requesting agent infrastructure; it is not customer authentication or permission to access an account. Preserve login checks, payment controls and application-level authorisation. Test public browsing separately from actions involving a particular shopper.

Start with an observed blocked request rather than copying a broad allow rule across all traffic. Compare the result at search, product selection and cart steps, then monitor challenge and error logs. Merchants who do not control their storefront’s infrastructure should route the question to their platform or protection vendor instead of assuming they can change its edge settings.

ℹ️
Do not allow traffic solely because its User-Agent says Google-Agent. Verify its origin and preserve customer authentication and authorisation.
Filed underAI

More from AI

See all →