Google · Answers
Google-Read-Aloud
The trigger is somebody pressing play. Google's description is one sentence and it is the whole story: upon user request, Read Aloud fetches and reads out web pages using text-to-speech. The fetch exists to get an article's text into a speech synthesiser, which makes it a delivery mechanism for a reader who is driving, cooking or using a screen reader, not an ingestion pipeline. Nothing about the request feeds an index, a model or a citation surface, making it the most narrowly scoped token Google publishes.
- Operated by
- Purpose
- Answers
- robots.txt token
- Google-Read-Aloud
- Verification
- IP verified
Fetches a page in real time to answer a question someone just asked.
How to verify Google-Read-Aloud
Google publishes the IP ranges Google-Read-Aloud crawls from, and we fetch that list on a schedule. A request claiming to be Google-Read-Aloud can therefore be checked against 2,163 published ranges: one that does not match is not this crawler.
Published ranges last confirmed by us on .
Google documents reverse-DNS verification: a genuine request resolves to a hostname under .gae.googleusercontent.com or .google.com that forward-resolves back to the same address.
User agent
Google publishes this user agent for Google-Read-Aloud. Match on the Google-Read-Aloud product token rather than the whole string: vendors revise the surrounding version and URL fragments without notice.
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)robots.txt for Google-Read-Aloud
No: covered by Google's rule that user-triggered fetchers generally ignore robots.txt.
Block
User-agent: Google-Read-Aloud
Disallow: /Allow
User-agent: Google-Read-Aloud
Allow: /robots.txt is a request, not an enforcement mechanism. It is honoured by convention, and a crawler that ignores it is stopped at your edge, not in a text file.
What blocking Google-Read-Aloud costs you
The loss is an accessibility one, and it lands on individual readers rather than on your metrics: somebody who asked to have your page spoken aloud gets silence or an error, including users who rely on text-to-speech rather than choosing it for convenience. Nothing about your search presence, AI citations or ad quality moves either way. You buy a negligible reduction in requests in exchange for making your content unlistenable to the people least able to route around it, which makes this the hardest of Google's tokens to justify blocking.