🎙️ Speakable Schema Guide

Optimize your content for voice assistants with speakable structured data markup for Google Assistant, Alexa, and more.

Voice Search Growth

50%

Voice Searches

Of all online searches are expected to be voice-based.

4.2B

Voice Assistants

Digital voice assistants in use worldwide.

71%

Prefer Voice

Of consumers prefer voice to typing for searches.

27%

Daily Users

Of global population uses voice search on mobile.

What is Speakable Schema?

Speakable schema markup identifies sections of your content that are best suited for audio playback using text-to-speech (TTS). It helps voice assistants understand which parts of your page to read aloud in response to voice queries.

When implemented correctly, Google Assistant and other voice platforms can use this structured data to deliver your content directly to users through smart speakers, phones, and other voice-enabled devices.

💡 Key Benefit

Speakable schema helps you control exactly what voice assistants read from your content, ensuring users get the most relevant, concise information.

🎙️

"Hey Google, what's the latest news about..."

Voice assistants read your marked-up speakable content directly to users, providing quick, hands-free access to your information.

Implementation Examples

// JSON-LD with speakable using cssSelector
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "Article Title",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [
      ".article-headline",
      ".article-summary",
      ".key-points"
    ]
  },
  "url": "https://example.com/article"
}
📌 Important Note

Speakable schema is currently supported for news content in English in the US, UK, and Australia. Google recommends using cssSelector over xpath for ease of maintenance.

Content Requirements

📝

Content Length

Speakable content should be concise enough to be read aloud comfortably.

20-30 seconds of audio maximum
2-3 short sentences ideal
Under 120 words recommended
Focus on key information only
🎯

Content Quality

Content must be clear, accurate, and suitable for audio consumption.

Complete, standalone sentences
No abbreviations or jargon
Numbers spelled out when helpful
Clear pronunciation of terms
⚙️

Technical Setup

Proper technical implementation is essential for recognition.

Valid JSON-LD structured data
Correct CSS selectors or XPath
Elements must exist on page
HTTPS required

Ideal Content Types

📰

News Articles

Breaking news and timely updates are ideal for voice delivery. Headlines and key points work perfectly.

✓ Ideal for Speakable
📊

Weather & Sports

Quick facts, scores, and forecasts translate well to voice format.

✓ Ideal for Speakable
📚

How-To Summaries

Short summaries and key takeaways from guides work well when concise.

Good Candidate
❓

FAQ Answers

Direct answers to common questions are perfect for voice responses.

Good Candidate
📅

Event Information

Event dates, times, and key details can be marked as speakable.

Good Candidate
📖

Long-Form Content

Full articles and detailed guides need summaries for voice; full content is too long.

Needs Summary

Best Practices

✍️

Writing for Voice

Content written for voice should sound natural when read aloud. Avoid complex sentence structures.

Use active voice over passive
Keep sentences short and direct
Avoid parenthetical statements
Read content aloud to test flow
🏷️

Selector Strategy

Choose stable, semantic selectors that won't break with design changes.

Use meaningful class names
Prefer IDs for unique elements
Avoid deep nested selectors
Test selectors after site updates
📐

Content Structure

Structure your page with clearly defined sections that can be easily targeted.

Create dedicated summary sections
Use semantic HTML elements
Separate key points into lists
Include clear headline elements
🔄

Ongoing Maintenance

Regularly verify that your speakable markup remains functional and effective.

Test after template changes
Validate with Rich Results Test
Monitor Search Console reports
Update content for freshness

Voice Platforms

🔵

Google Assistant

Primary platform for speakable schema. Powers Google Home and Android devices.

🔷

Amazon Alexa

Uses different Flash Briefing skills but benefits from structured content.

⚫

Apple Siri

Doesn't use speakable schema but may leverage structured data for answers.

🟡

Samsung Bixby

Growing platform that benefits from well-structured content.

Testing Your Implementation

1

Rich Results Test

Use Google's Rich Results Test to validate your speakable structured data and check for errors.

2

Schema Validator

Test your JSON-LD with Schema.org's validator to ensure proper syntax and structure.

3

Read Aloud Test

Read your speakable content out loud to ensure it sounds natural and complete.

4

Selector Check

Verify your CSS selectors or XPath expressions actually match elements on the page.

5

Search Console

Monitor the Enhancements report in Google Search Console for speakable issues.

6

Voice Test

Test with actual voice assistants to see how your content is delivered in practice.

Implementation Checklist

📝 Content Prep

⚙️ Technical Setup

🚀 Monitoring