What is Google-Read-Aloud?

Google-Read-Aloud fetches web content to provide text-to-speech functionality, enabling users to have web pages read aloud through Google's accessibility services. Agent Analytics can track when it visits your website.

Category

Fetcher
Retrieves web page metadata to power app features like link previews or feeds

Expected Behavior

Google-Read-Aloud shows up within seconds of someone sharing one of your URLs, grabs the title, description, and preview image, and leaves. Expect one hit per share, no link following, and volume that tracks how much your content circulates. A widely shared link can mean thousands of fetches in an hour.

Overview

Operated By Google
Expected To Follow Robots.txt No
Insights Last Updated July 7, 2026

Robots.txt Blocked Percentage

1%
1% of top websites are blocking Google-Read-Aloud
Learn How →

Country of Origin

United States
Google-Read-Aloud normally visits From the United States

Robots.txt Blocking Trend

As of July 7, 2026, 1% of top websites block Google-Read-Aloud in their robots.txt files.

Overall Fetcher Traffic

As of July 7, 2026, 3.7% of all web traffic came from fetchers.

Top Visited Website Categories

Autos and Vehicles
Finance
Internet and Telecom
Home and Garden
Travel and Transportation
Track Fetchers Visiting Your Website
Use Agent Analytics to get realtime visibility into visits from every crawler, scraper, and AI agent.

This data reflects agent visits measured across thousands of websites using Agent Analytics, combined with daily scans of the world's top 1000 websites and their robots.txt files.

Google-Read-Aloud's User Agent

User Agent Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Mobile Safari/537.36 (compatible; Google-Read-Aloud; +https://support.google.com/webmasters/answer/1061943)

Access other known user agents and IP addresses using the Enterprise API.

How To Block Google-Read-Aloud

Add this rule to your robots.txt file to request that Google-Read-Aloud not access your website. You can customize which pages are blocked by swapping out / for a different path.

User-agent: Google-Read-Aloud # https://knownagents.com/agents/google-read-aloud
Disallow: /
Block Every Fetcher
⚠️ Manually adding individual robots.txt rules is not scalable. Instead, use Automatic Robots.txt.

Frequently Asked Questions

Should I Block Google-Read-Aloud?

No. Google-Read-Aloud builds the link preview that appears when someone shares your page in a chat or social feed. Blocking it turns those shares into bare links with no title or image, which fewer people click. Its traffic normally follows sharing activity rather than a crawl schedule, so if it ever starts crawling at volume, rate limit it instead of blocking it. For comparison, 1% of the top websites we track already have robots.txt rules for Google-Read-Aloud.

Does Google-Read-Aloud Respect Robots.txt?

No. Google-Read-Aloud is not expected to honor robots.txt, so a disallow rule only states your preference. Enforce the block with firewall or server rules, then confirm in Agent Analytics that its requests actually stop.

Does Google-Read-Aloud Access Private Content?

It cannot. Google-Read-Aloud loads only the exact URL someone shared, reads the title, description, and preview image, and leaves. It has no credentials and does not follow links to other pages.

Why Is Google-Read-Aloud Visiting My Website?

Someone shared a link to your page. Google-Read-Aloud fetched it once to build the preview card, and every new share can trigger another fetch, so spikes mean your content is spreading.

How Can I Tell if Google-Read-Aloud Is Visiting My Website?

Agent Analytics tracks Google-Read-Aloud visits in real time alongside every other known AI agent, crawler, and scraper. You can also check your server logs for requests whose user agent string contains "Google-Read-Aloud". Look for hits on single pages moments after someone shares a link, with no crawling afterward. Keep in mind that Google-Read-Aloud doesn't publish a verification method, so any client can claim its user agent string and a log match is a hint rather than proof.

References