`Google-Read-Aloud`

The Google Read Aloud article, updated 2025-12-02, says Google-Read-Aloud reads web pages with text-to-speech when a person turns that on, and that it is not a web crawler and does not follow links. The article says a site cannot opt out with a robots.txt file. The opt-out it names is a meta tag, name google and content nopagereadaloud. This check does not read meta tags. The user-triggered list publishes mobile and desktop HTTP strings and lists google-speakr as a deprecated former agent. This card does not include that string. This check matches the whole token and still reports the RFC 9309 decision.

robots.txt token: Google-Read-Aloud
Operator: Google
Kind: user_fetch
robots.txt: does_not_follow. The vendor says this crawler does not follow robots.txt rules.
HTTP user-agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36 (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943) The user-triggered list also publishes this desktop agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36 (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943). It does not print a separate robots.txt User-agent line. The Read Aloud article says google-speakr is a deprecated former agent and the current name is Google-Read-Aloud. google-speakr is not this card.
IP list: None on the cited page. The user-triggered fetchers section names https://developers.google.com/static/crawling/ipranges/user-triggered-fetchers.json (creationTime 2026-10-16T14:46:09.000000), https://developers.google.com/static/crawling/ipranges/user-triggered-fetchers-google.json (creationTime 2026-10-16T14:46:08.000000), and https://developers.google.com/static/crawling/ipranges/user-triggered-agents.json (creationTime 2026-10-16T14:46:09.000000), and does not say which file this fetcher uses. Each URL returned HTTP 200 on 2026-10-18. Botcard does not copy the prefixes. The page says the reverse DNS mask matches ***-***-***-***.gae.googleusercontent.com when Google owns the fetcher, or google-proxy-***-***-***-***.google.com when a user owns it. A user-agent string can be spoofed.
Source: List of Google user-triggered fetchers. Retrieved 2026-10-18, page says updated 2026-08-19. CC BY 4.0 (Google Developers page, except as that page notes).

JSON

curl -s https://whosthatbot.com/v1/crawlers/google-read-aloud

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Google-Read-Aloud on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Google-Read-Aloud\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["google-read-aloud"]}}}'

That call returns fetched_target false. This row is disallow via group Google-Read-Aloud, rule Disallow: /.