Inferensys

Glossary

Speakable Schema

Speakable schema is a type of structured data markup that identifies sections of a webpage most suitable for text-to-speech conversion by voice assistants and screen readers.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
TEXT-TO-SPEECH STRUCTURED DATA

What is Speakable Schema?

Speakable schema is a type of structured data markup that identifies specific sections of a webpage most suitable for text-to-speech conversion by voice assistants and screen readers.

Speakable schema is a SpeakableSpecification structured data type within Schema.org that explicitly marks content sections—such as headlines and summary paragraphs—as optimal for text-to-speech (TTS) playback. By implementing this markup in JSON-LD or microdata, publishers guide voice assistants like Google Assistant to read aloud only the most relevant, concise portions of a page, filtering out navigation, ads, and tangential content.

This specification uses cssSelector or xpath properties to pinpoint the exact DOM elements containing speakable content. For answer engine optimization, speakable schema is critical because it directly influences how AI-generated voice responses are constructed from web sources, ensuring that zero-click content delivered via smart speakers is coherent, authoritative, and free of extraneous noise.

STRUCTURED DATA FOR VOICE

Key Features of Speakable Schema

Speakable schema markup identifies sections of a webpage most suitable for text-to-speech conversion, enabling voice assistants to deliver clear, concise audio responses.

02

TTS-Optimized Content Selection

Marked content must be concise and conversational. Best practices include:

  • Targeting the article's lede or a dedicated abstract
  • Using short, declarative sentences
  • Avoiding ambiguous pronouns without clear antecedents
  • Omitting complex tables or data visualizations that cannot be read aloud meaningfully
03

Implementation Methods

Speakable can be implemented via JSON-LD, Microdata, or RDFa. JSON-LD is the recommended format by Google. A typical implementation specifies @type: SpeakableSpecification and includes a cssSelector array pointing to the target DOM elements, such as [".article-summary", "#tts-content"].

04

Platform Support & Limitations

Google Assistant is the primary consumer of speakable schema, using it to power News on Assistant and other audio briefings. The feature is currently limited to news content and requires publishers to be approved for the Google News platform. Other voice assistants have not yet widely adopted this specific markup.

05

Relationship to SSML

Speakable schema identifies what to read, while Speech Synthesis Markup Language (SSML) controls how it is read. SSML provides fine-grained control over pronunciation, pitch, rate, and pauses. For advanced voice experiences, speakable content can be paired with SSML to improve prosody and naturalness.

06

SEO & GEO Impact

While not a direct ranking factor, speakable schema enhances Generative Engine Optimization by providing a clean, authoritative signal for voice-based answer engines. It increases the likelihood of being selected as the single definitive source for audio responses, improving brand presence in screenless environments.

SPEAKABLE SCHEMA

Frequently Asked Questions

Clear, concise answers to the most common technical questions about implementing Speakable structured data for voice assistants and text-to-speech engines.

Speakable Schema is a type of SpeakableSpecification structured data markup, defined by Schema.org, that identifies specific sections of a webpage most suitable for text-to-speech (TTS) conversion by voice assistants like Google Assistant. It works by wrapping content in application/ld+json blocks using @type: SpeakableSpecification and xpath or cssSelector properties to point to the exact HTML elements containing the text to be read aloud. When a voice assistant processes a page, it parses this markup to extract only the highlighted passages, ignoring navigation, ads, and other non-essential content, delivering a clean, concise audio summary to the user.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.