Google-Read-Aloud

Google · User-triggered fetchers · json

User-agent: Google-Read-Aloud
Disallow: /
robots.txt tokenGoogle-Read-Aloud
User-agent containsGoogle-Read-Aloud
OperatorGoogle
CategoryUser-triggered fetchers
robots.txtnot governed by robots.txt (user-initiated, by operator policy)
Verify bypublished IP ranges
Published ranges529 IPv4 + 529 IPv6 · json · source

What it is

Fetches a page so Google can read it out loud with text-to-speech, at the moment a user asks. Formerly google-speakr. Google publishes fetcher addresses in two files — user-triggered-fetchers.json and user-triggered-fetchers-google.json — and does not say per fetcher which one applies, so verification means checking both; this index mirrors both.

What blocking it costs you

A reader who asked Google to read your page aloud — often someone using it for accessibility — gets an error instead.

Full user-agent string

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)

Allow it instead

User-agent: Google-Read-Aloud
Allow: /

Operator documentation: https://developers.google.com/search/docs/crawling-indexing/google-user-triggered-fetchers
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-all-ai · allow-ai-search-only · block-disputed · maximum-ai-visibility