Google-Read-Aloud fetcher
Google-Read-Aloud is a user-triggered Google fetcher that retrieves a page so Google can convert its text to speech and read it aloud to a user. It is documented among Google's user-triggered fetchers, is not the search crawler, and because it acts on a user's request it generally ignores robots.txt the way other user-triggered fetchers do.
What this means
Google-Read-Aloud fetches a page so its text can be spoken aloud through Google's text-to-speech features. It is a user-triggered fetcher: it runs because a person asked for the page to be read, not because Google is indexing it.
Because it acts on a user's behalf, Google documents user-triggered fetchers as generally not bound by robots.txt the way the indexing crawlers are. Blocking it in robots.txt is therefore not the right control for this behaviour.
How Google-Read-Aloud identifies itself
It uses the user-agent token Google-Read-Aloud and is listed among Google's user-triggered fetchers. Match on the stable token rather than a version string.
Verify the source IP against Google's published user-triggered-fetchers range list when you need to confirm authenticity, since the user agent alone can be copied.
- User-agent token: Google-Read-Aloud
- Category: user-triggered fetcher (text-to-speech)
- Not the search crawler; user-triggered fetchers are treated differently for robots.txt
How it appears in analytics and logs
A request with the Google-Read-Aloud token means a Google feature fetched the page to read it aloud for a user. It is automation acting on behalf of a person at request time, not Googlebot crawling for the index.
Diagnostic use case
Recognise text-to-speech fetches in your logs, understand they are user-triggered rather than indexing, and verify them against Google's user-triggered-fetcher ranges.
What WebmasterID can help detect
WebmasterID classifies Google-Read-Aloud as a user-triggered Google fetcher distinct from Googlebot, so text-to-speech fetches stay out of search-crawl coverage and human analytics.
Common mistakes
- Expecting a robots.txt Disallow to stop Google-Read-Aloud — user-triggered fetchers are handled differently from the indexing crawlers.
- Counting read-aloud fetches as search-crawl activity or as human visits.
- Trusting the user agent without IP verification on sensitive endpoints.
Privacy and accuracy notes
Google-Read-Aloud is identified only by its user-agent token; no visitor identity is exposed. WebmasterID records it as a bot/automation event, never as a human profile.
Related pages
- APIs-Google fetcher
APIs-Google is a Google fetcher user agent used when Google products send push notifications or other API-driven requests to a developer's server — for example a PubSubHubbub (WebSub) delivery. It is not the search crawler and is not used to build the search index. Google documents it in the list of Google crawlers and fetchers, and it is verifiable against Google's published crawler IP ranges.
- Google Site Verifier fetch
Google-Site-Verification is the fetcher Google uses to confirm a site-ownership verification token — for example retrieving an HTML verification file or checking a meta tag — when you verify a property in Search Console or other Google services. It is documented among Google's special-case fetchers and is unrelated to ongoing search indexing.
- Googlebot-News — Google News crawling
Googlebot-News is the user agent that governs crawling for Google News. Google documents it as relying on Googlebot for actual crawling, with the Googlebot-News token letting publishers control Google News inclusion separately from general Search.
- Web crawlers
How crawlers and fetchers are detected and categorised.
Sources and verification notes
- Google Search Central — Google crawlers and fetchers overviewGoogle-Read-Aloud listed among user-triggered fetchers.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.