SpeakableSpecification schema — what it does & how to ship it
Speakable marks the CSS selectors of passages that voice assistants and LLM readers should extract — the highest-leverage schema for voice answers and Google Assistant.
What it does
SpeakableSpecification nests inside a WebPage node and carries cssSelector or xpath pointing to the exact HTML elements to read aloud. Typically point at H1, TL;DR block, and key takeaway sections.
SERP / AI benefit
Google Assistant voice-reading eligibility, preferential extraction by LLM retrievers, and higher probability of being cited in Google AI Overviews.
Where to use it
H1, TL;DR block, key takeaway sections — on every post, answer, and pillar page.
JSON-LD example
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "What is GEO?",
"speakable": { "@type": "SpeakableSpecification", "cssSelector": ["h1", ".speakable-short"] }
}Copy, edit for your site, and drop into your page head inside a<script type="application/ld+json">block. Validate with Google's Rich Results Test.
In WBP Omni SEO Pro
Emitted on every /answers/*, blog post and pillar with cssSelector pointing at h1 and the TL;DR block.
Ship SpeakableSpecification without touching codeFrequently asked
Does Speakable schema affect SEO rankings?›
Indirectly — it doesn't boost classic rank but does increase voice-answer and AI-Overview citation rate.
How many selectors should I mark speakable?›
1-3 short, high-signal blocks. Marking the entire page defeats the purpose.