Safe Official docs Google Bots

Google-Read-Aloud

Q: 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.

Operated by Google

Scout's quick take

Google-Read-Aloud visits a page only when a person asks Google's assistant to open it. It is not a background crawler. Heads up: Google says robots.txt may not apply to it, so use a firewall rule if you need it stopped.

# Block only if you really mean to
User-agent: Google-Read-Aloud
Disallow: /

See which AI bots are blocked Build a full robots.txt

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

Confirmed by the operator

Google names Google-Read-Aloud on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

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

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

Google-Read-Aloud in context

Google-Read-Aloud is a user-triggered agent operated by Google. In plain terms, it fetches a page when a person asks an assistant or app to open it. Our database files it under Google crawlers and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 20 of the 24 Google crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is low. So the decision about Google-Read-Aloud rests on what you want from Google, not on its behaviour. How we rate safety and impact.

How site owners treat Google-Read-Aloud

Our robots.txt study of the Tranco top 10,000 did not track Google-Read-Aloud as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Google-Read-Aloud's operator says it does not follow robots.txt for these requests, so a robots.txt rule will not stop Google-Read-Aloud. Use a firewall, CDN or server rule if you need to block it.

Google crawlers and close alternatives

Google-Read-Aloud is one of 32 Google crawlers in our database. A User-agent: Google-Read-Aloud group controls Google-Read-Aloud only; the other Google tokens below need their own lines.

Google-Read-Aloud: this crawler (Tier 3)
AdsBot-Google: Google Ads Quality (Desktop), checks pages for an SEO, uptime or analytics service (Tier 3)
AdsBot-Google-Mobile: Google Ads Quality (Mobile), checks pages for an SEO, uptime or analytics service (Tier 3)
APIs-Google: APIs-Google, fetches a page when a person asks an assistant or app to open it (Tier 3)
Chrome-Lighthouse: Lighthouse Audit, checks pages for an SEO, uptime or analytics service (Tier 4)
FeedFetcher-Google: Google Feed Fetcher, builds a search or answer index (Tier 3)
Gemini-Deep-Research: Gemini-Deep-Research, fetches a page when a person asks an assistant or app to open it (Tier 3)
Google-Agent: Google Agent (Project Mariner), fetches a page when a person asks an assistant or app to open it (Tier 2)
Google-CloudVertexBot: Google Vertex AI, fetches a page when a person asks an assistant or app to open it (Tier 3)

To give Google-Read-Aloud the same answer as its siblings, stack User-agent: Google-Read-Aloud with their lines above one set of rules; to treat Google-Read-Aloud differently, give it its own group.

No other crawler in our Google crawlers category has exactly the same purpose, which makes Google-Read-Aloud an unusual case: decide about it on its own merits.

We first recorded Google-Read-Aloud on May 31, 2026. Google documents it on developers.google.com, and we recheck that page before each release.

Which rule Google-Read-Aloud actually follows

Google-Read-Aloud reads exactly one group in robots.txt, the most specific one that names Google-Read-Aloud, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Google-Read-Aloud
Disallow: /drafts/

Find the group. Google-Read-Aloud looks for a group naming Google-Read-Aloud. One exists, so it ignores User-agent: * completely.
Apply only that group. It is refused /drafts/ and nothing else.
The surprise. /private/ is open to Google-Read-Aloud, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.

Test yourself: does a rule under User-agent: * apply to Google-Read-Aloud if the file also has a User-agent: Google-Read-Aloud group?

No. Once a group names it, Google-Read-Aloud reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Google-Read-Aloud remove your pages from AI answers?

Often, yes. Google-Read-Aloud is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: google-read-aloud the same as User-agent: Google-Read-Aloud?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Google-Read-Aloud? Decide by situation

Recommended setting for Google-Read-Aloud by type of site
If you are...	Recommended setting
You publish content and want AI answers to cite it	Allow it. Google-Read-Aloud fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI training	Blocking it does not stop training, because Google-Read-Aloud is a user-triggered agent. Block the operator's training crawler instead.
You run an online shop	Allow it unless it is overloading your servers.
Your server is under load from bots	Rate-limit before blocking. It is rated safe in our database.

Check Google-Read-Aloud on your own site

Open /robots.txt on your domain and search for Google-Read-Aloud. If it is not named, it follows User-agent: *.
List the Disallow lines in the group Google-Read-Aloud follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
Look beyond the file. A firewall or bot manager can refuse Google-Read-Aloud even when robots.txt allows it, and that never shows in the file.
Run our AI bot checker to see how Google-Read-Aloud and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Google-Read-Aloud

The errors we see most often with Google-Read-Aloud in the files and firewalls we test:

Assuming a robots.txt rule will stop Google-Read-Aloud. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
Blocking Google-Read-Aloud as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
Counting Google-Read-Aloud visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check Google-Read-Aloud from outside after every change.

Spotting Google-Read-Aloud in your logs

robots.txt says what Google-Read-Aloud may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "Google-Read-Aloud" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "Google-Read-Aloud" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Google-Read-Aloud user-agent, so confirm the source before acting on a match:

Google-Read-Aloud: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Google-Read-Aloud request with caution.

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.