Safe Google Bots

Google-Read-Aloud

Operated by Google

Quick Facts

User-Agent:
Google-Read-Aloud
Category:
Google Bots
Operator:
Google
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
3/10
Official docs:
developers.google.com

What is Google-Read-Aloud?

Google-Read-Aloud fetches a page so its text can be spoken aloud, powering the read-aloud and text-to-speech features in Google Search and Android.

Google-Read-Aloud fetches a page so its text can be spoken aloud, powering the read-aloud and text-to-speech features in Google Search and Android. Google-Read-Aloud identifies itself with the user-agent token Google-Read-Aloud. You can control it with a User-agent: Google-Read-Aloud group in robots.txt. Robots.txt is voluntary, so for hard enforcement combine it with server-level blocking.

What happens if you block Google-Read-Aloud?

✅ Blocking Google-Read-Aloud has no effect on your rankings, because it does not index anything. The only consequence is that Google can no longer fetch your page to read it aloud, so text-to-speech playback of your content stops working for users who requested it. This is an accessibility feature, so consider that before blocking it.
Safe to allow. Blocking only disables spoken playback.

How to control Google-Read-Aloud with robots.txt

<code>User-agent: Google-Read-Aloud</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: Google-Read-Aloud Disallow: /
Allow all (robots.txt)
User-agent: Google-Read-Aloud Allow: /
Block private only (robots.txt)
User-agent: Google-Read-Aloud Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Block Google-Read-Aloud if ($http_user_agent ~* "Google-Read-Aloud") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Block Google-Read-Aloud SetEnvIfNoCase User-Agent "Google-Read-Aloud" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Google-Read-Aloud safe to allow?

Yes, Google-Read-Aloud is a **safe and legitimate** crawler. It is operated by Google and documented publicly, and it identifies itself honestly with the token Google-Read-Aloud. Safe to allow. Blocking only disables spoken playback.
Verify by reverse-DNS: genuine Google fetchers resolve to googlebot.com, google.com or googleusercontent.com. Confirm the forward lookup matches the original IP.

What does Google-Read-Aloud do?

Understanding what Google-Read-Aloud is for helps you decide whether to allow or block it.

  • Fetches page text for spoken playback
  • Powers read-aloud in Google Search and Android
  • Triggered by a user action, not a crawl schedule
  • Reads existing page content only
  • Respects robots.txt directives

Frequently Asked Questions

What is the user-agent string for Google-Read-Aloud?
Google-Read-Aloud uses the token Google-Read-Aloud. Match it case-insensitively in robots.txt and in any server-level rule.
Is Google-Read-Aloud safe?
Yes. Google-Read-Aloud is operated by Google and is documented publicly. Google-Read-Aloud fetches a page so its text can be spoken aloud, powering the read-aloud and text-to-speech features in Google Search and Android.
Will blocking Google-Read-Aloud hurt my SEO?
Blocking Google-Read-Aloud has no effect on your rankings, because it does not index anything. The only consequence is that Google can no longer fetch your page to read it aloud, so text-to-speech playback of your content stops working for users who requested it. This is an accessibility feature, so consider that before blocking it.
How do I block Google-Read-Aloud in robots.txt?
Add these lines to /robots.txt: 
User-agent: Google-Read-Aloud
Disallow: /
To restrict only part of your site, disallow specific paths and allow the rest.

Related Bots