Speakable schema identifies the sections of a page best suited to be read aloud by text-to-speech, intended to help voice assistants answer with your content — but it has remained a limited, news-focused beta rather than a broadly available feature. It is the type most likely to be over-implemented on false hope. This reference is about setting expectations correctly: what Speakable is meant to do, its real status, and whether it is worth your time.
What Speakable Is Meant to Do
It marks specific sections — by CSS selector or XPath — as the parts of a page a voice assistant should read aloud, so a device like Google Assistant could speak a concise answer sourced from your content.
The intent is sound: give assistants a clean, short passage to voice rather than guessing. In practice, adoption and support have stayed narrow, which is the crucial context this reference exists to provide.
Its Real Status
Speakable has long been a beta limited to news publishers in select regions and languages, and it is not a widely available rich result — most sites will see no effect from adding it.
This is the same status-honesty the cluster applies to FAQ and HowTo: the type exists and validates, but the feature is restricted. Unless you are an eligible news publisher, treat Speakable as experimental rather than a reliable channel.
How It Is Structured
Speakable is a property (usually on Article or WebPage) whose value points to page sections via cssSelector or xpath, telling assistants which elements hold the speakable summary.
The selectors must target genuinely concise, self-contained passages — typically a headline and a one or two sentence summary. Pointing it at long or navigational content defeats the purpose.
Is It Worth Adding?
For eligible news publishers, it is worth a lightweight implementation; for everyone else, it is optional and low-priority — the broader route to voice and AI answers is concise, well-structured content, not this markup.
The same clear-summary content that helps AI Overviews and assistants, covered in the GEO & AEO pillar, does more for voice visibility than Speakable markup does for most sites. Prioritize accordingly.
Example Markup
Speakable on a WebPage (shown as code):
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebPage",
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": [".headline", ".summary"]
}
}
</script>
See JSON-LD vs Microdata for the format.
- Speakable marks page sections for text-to-speech so voice assistants can read a concise answer.
- It has stayed a beta limited to news publishers in select regions/languages — not a broad rich result.
- Structured as a property pointing to sections via cssSelector or xpath.
- Worth a light implementation for eligible news publishers; optional and low-priority otherwise.
- For most sites, concise well-structured content does more for voice/AI than Speakable markup.
Frequently Asked Questions
Does Speakable schema work for all sites?
No — it has been limited to news publishers in select regions and languages as a beta. Most sites will see no effect from adding it, so set expectations accordingly rather than treating it as a reliable feature.
How does Speakable choose what to read?
You point it at page sections using cssSelector or xpath. Those selectors should target a concise, self-contained passage — usually a headline plus a short summary — that makes sense read aloud out of context.
Should I prioritize Speakable for voice SEO?
Not for most sites. Clear, concise, well-structured content does more for voice and AI answers than Speakable markup, which remains narrowly supported. Eligible news publishers can add it lightly; others should focus elsewhere.
The Bottom Line
Speakable is a good idea with limited reach: valuable to mark up if you are an eligible news publisher, largely inert for everyone else. Add it lightly where eligible, do not over-invest, and put your voice-visibility effort into concise content — the realistic, status-aware stance the schema cluster takes on every restricted type.
Further reading & sources
- Speakable structured data — Google Search Central
- speakable — Schema.org
See how your site actually shows up in AI search. An AI visibility audit maps where you’re cited, where you’re invisible, and what to fix first — in plain English.
Get your AI visibility auditTry the free SEO tools →
Prefer self-serve? The interactive checklists turn guides like this one into a working to-do list.
Keep reading in Schema Markup
Get one email when something genuinely changes
AI search moves fast and most of it is noise. We send one short email when a real shift is worth your time. Unsubscribe anytime.
Published by Plain Intelligence — practical AI SEO, GEO, and technical SEO, documented in plain English. About Plain Intelligence →
↑ Back to Schema Markup · Explore all articles · Free tools & resources · Glossary