Directory Assistants fetching for a user
Google user-triggered fetchers Bot
Fetches feeds and files, operated by google. Fetched because a person asked an assistant.
- Operator
- Does
- Fetches feeds and files
- Traffic
- Its operator’s own
- robots.txt
- No token
Identity
Publishes its IP addresses
- SignedSigns every request (Web Bot Auth): cryptographic proof.
- IP listPublishes the IP addresses it comes from.
- Reverse DNSIts IP addresses resolve to the operator’s domain.
- User agentNames itself in its user agent, which anyone can copy.
- HiddenLooks like a person’s browser: detected by behaviour.
How to recognise it
Reverse DNS
The hostname ends in
googlebot.com,google.com,googleusercontent.com, then forward-confirmed.User agent
Contains
Google-Read-Aloud,Google Read Aloud,Google-Pinpoint,FeedFetcher-Google,GoogleProducer,Google-Site-Verification,Google-CWS,GoogleMessages. Anyone can copy it, so it names the client without proving it.
Details
- ID
google.user-fetchers- Category
- Bot
- Operator
- Agent Card
- Not published: this agent doesn’t identify itself with an Agent Card.
- First seen
- 2026-09-28
Registrations
- Catalog Self
- Verified
- 2026-09-28
- Checked
- 2026-09-28
Reputation
Computed 2026-11-13
A score shows from 30%
- Identity40% of the score19 / 100
0 verified sources
A verified Agent Card adds 25 points, 40 if it is signed.
- Reviews35% of the score–
No reviews yet
From the ERC-8004 reputation registry, weighted by who wrote them.
- Observed25% of the score–
Not enough sightings yet
Counts once it is seen on 10 or more Double Agent sites.
Change history
No card history: this agent doesn’t publish an Agent Card.
With Double Agent
Sessions from Google user-triggered fetchers are labelled bot with agent_id: google.user-fetchers, and tagged in your analytics. Nothing is blocked unless you choose to.
Related
All 226 clients
Source: https://developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers