🔎
Google Search for beginners
Home
  • Introduction
  • Google Search Essentials
    • Overview
    • Google Search Technical Requirements
    • Spam Policies
  • SEO Basics
    • SEO Beginner's Guide
    • How Google Search Works
    • Creating Helpful, Reliable Content
    • Do You Need an SEO Expert?
    • Maintaining Your Website’s SEO
    • Developer's Guide to Google Search
    • How to Get Your Website Listed on Google
  • crawling and indexing
    • Overview
    • File formats Google can index
    • URL structure
    • Links
    • Sitemaps
      • Create and submit a sitemap
      • Manage your sitemaps
      • Image-specific sitemaps
      • News-oriented sitemaps
      • Video sitemaps and alternatives
      • Combining different sitemap types
    • Managing Google Crawlers
      • Reducing the crawl rate of Googlebot
      • Verifying the Googlebot and other Google crawlers
      • Managing Crawl Budget for Large Sites
      • HTTP Status Codes, Network, and DNS Errors
      • Types of Google Crawlers
      • Googlebot Explained
      • Google Read Aloud Service
      • Google API
      • Understanding Feedfetcher
    • Robots.txt
      • Creating and Submitting Robots.txt
      • Updating Robots.txt
      • Google's Interpretation of Robots.txt
    • Canonicalization
      • Specifying Canonicals Using rel="canonical" and Other Methods
      • Resolving Canonicalization Issues
    • Canonicalization for Mobile Sites and Mobile-First Indexing
    • AMP (Accelerated Mobile Pages)
      • Understanding How AMP Works in Search Results
      • Enhancing Your AMP Content
      • Validating AMP Content
      • Removing AMP Content
    • JavaScript
      • Fixing Search-Related JavaScript Issues
      • Resolving Issues with Lazy-Loaded Content
      • Using Dynamic Rendering as a Workaround
    • Page and Content Metadata
      • Meta Tags
      • Using Robots Meta Tag, data-nosnippet, and X-Robots-Tag noindex
      • noindex Explained
      • rel Attributes
    • Removals
      • Removing Pages from Search Results
      • Removing Images from Search Results
      • Handling Redacted Information
    • Redirects and Google Search
      • Switching Website Hosting Services
      • Handling URL Changes During Site Moves
      • A/B Testing for Sites
      • Pause or Disable a Website
Powered by GitBook
On this page
  1. crawling and indexing
  2. Managing Google Crawlers

Google Read Aloud Service

Google Read Aloud User Agent: A Technical Guide

This document provides a technical overview of the Google Read Aloud user agent and how it interacts with your website. Understanding its functionality can help you optimize your content for accessibility and user experience.

What is Google Read Aloud?

Google-Read-Aloud is the user agent used by Google's text-to-speech (TTS) service. This service enables users to listen to web pages instead of reading them, enhancing accessibility for individuals with reading disabilities or preferences for auditory learning.

Here are some examples of services and apps that utilize the Google Read Aloud engine:

  • Google Assistant: When you ask Google Assistant to "read this article," it utilizes Google Read Aloud to process and vocalize the webpage content.

  • Google Chrome (Read Aloud feature): The built-in "Read Aloud" feature in the Chrome browser relies on Google Read Aloud to convert text on webpages into spoken audio.

  • Third-Party Accessibility Tools: Numerous accessibility extensions and applications integrate with Google Read Aloud to provide text-to-speech capabilities.

How Does Google Read Aloud Work?

Google Read Aloud is triggered by explicit user requests, meaning it doesn't automatically crawl and process every webpage on the internet. Here's how it typically functions:

  1. User Initiates Request: A user triggers the Google Read Aloud service through one of the supported methods (e.g., clicking the "Read Aloud" button in Chrome, using a voice command with Google Assistant).

  2. Request Sent to Google: The user's request, including the URL of the webpage, is sent to Google's servers.

  3. Page Content Fetched (If Necessary): If the webpage content is not already cached by Google, it will be fetched from the server.

  4. Text-to-Speech Conversion: Google Read Aloud analyzes the webpage content, identifies the relevant text to read, and converts it into spoken audio using advanced text-to-speech algorithms.

  5. Audio Streamed to User: The generated audio is then streamed back to the user's device, allowing them to listen to the webpage content.

Crawl Frequency and Behavior

  • User-Driven: Google Read Aloud is not a traditional web crawler; it only accesses pages when a user specifically requests them. It does not proactively explore websites or follow links independently.

  • Caching for Efficiency: To conserve bandwidth and improve response times, Google Read Aloud caches webpage results. This means you might see multiple requests for the same page within a short period if several users access it using the service.

Preventing Google Read Aloud Access

Since Google Read Aloud acts upon user requests, preventing access differs from managing traditional web crawlers:

  • Robots.txt Ineffective: robots.txt files are not applicable here because Google Read Aloud doesn't operate as a conventional crawler.

  • "nopagereadaloud" Meta Tag: To completely disable Google Read Aloud for your webpage, implement the following meta tag in the <head> section of your HTML:

    <meta name="googlebot" content="nopagereadaloud"> 
  • Structured Data for Paywalled Content: If you have subscription-based or paywalled content, you can prevent unauthorized access using structured data:

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "NewsArticle",
      "isAccessibleForFree": "False",
      "paywallOffer": {
        "@type": "Offer",
        "name": "Subscription Offer",
        "url": "https://www.example.com/subscribe" 
      }
    }
    </script>

    Replace "https://www.example.com/subscribe" with your actual subscription page URL.

The "google-speakr" Agent: Deprecated

The user agent previously identified as google-speakr is outdated and deprecated. The current and accurate user agent name for Google's text-to-speech service is Google-Read-Aloud. Ensure you are referencing the correct user agent in your analytics and server configurations.

PreviousGooglebot ExplainedNextGoogle API

Last updated 11 months ago