Google-Agent

Google-Agent fetches a page live when someone asks the AI platform about it. Most operators use a separate user agent for each job, so you can usually allow or block one without affecting the others.

Page fetches requested by AI platform users. A verified request establishes a page read, not a citation or a human visit.

Requests from Google-Agent carry this token in their user agent string. Match the token rather than a full string, which changes as Google updates versions.

Google says Google-Agent fetches pages a person asked for and generally ignores robots.txt, so a robots.txt rule is not a reliable way to block it. To stop it, block its requests at your host, CDN or firewall.

Google publishes the IP addresses Google-Agent uses. A request that claims to be Google-Agent from any other address is not genuine.

• developers.google.com/static/crawling/ipranges/user-triggered-agents.json

SurfacedBy's AI traffic tracking recognizes Google-Agent in the user agent and checks each request against Google's published addresses. Only requests that pass count as crawls; the rest are shown separately.

Details on this page come from Google's own documentation: developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers.

• Google-Extendedrobots.txt control
• GooglebotSearch indexing