SEO & GEO
Speakable Schema for Voice Search and AI Assistants
Copy for AI
Speakable schema marks which sections of your page suit being read aloud.
It’s a piece of structured data for search engines and assistants. With a CSS selector or XPath, you literally point out the sentences a voice assistant can return as an answer.
The verdict: speakable schema markup is fine-tuning, not a foundation. The official Google feature is narrow, but the writing discipline behind it pays off in AI answers.
This is one of the least explained schema types, and for good reason: its official use is narrow.
Yet the concept matters for generative engine optimization. It does exactly what AI systems need: point to a clearly bounded, citable answer.
What is speakable schema?
It’s the speakable property from the schema.org vocabulary, which marks sections suitable for text-to-speech on an Article or WebPage.
In practice, you add a SpeakableSpecification to your existing markup. It references specific pieces of text on the page.
An assistant processing the page then knows which passage is meant to be read aloud. It doesn’t have to guess which part is the best answer.
New to the basics? Our guide to schema markup explains how structured data works in general.
Two ways to point at content
You point to content in one of two ways:
- cssSelector: refers to a class or element, such as the summary at the top of an article
- xpath: refers to a node in the document structure
Google says to use either one, not both, in a specification.
The idea is always the same: you isolate the sentences a person would read aloud as the answer to a question.
No visible result in search
Unlike many other schema types, speakable produces nothing you can see in the search results.
It’s not a rich snippet and not a star rating. It’s purely an instruction about read-aloud suitability.
Watch out: don’t expect a change in your Search Console reports after adding it.
How does speakable schema work technically?
You add it as JSON-LD, just like other structured data.
You implement speakable in the <head> or body of your page. Within your existing Article object, you add a speakable block with one or more selectors.
The three building blocks
In broad terms, it works like this:
- You define a
WebPageorArticleobject for the page. - Inside it you set
"speakable": { "@type": "SpeakableSpecification", "cssSelector": ["..."] }. - The selector points to the exact sections you want read aloud.
For example, a minimal block with a CSS selector could look like this:
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": [".summary", ".answer-intro"]
}
Here .summary and .answer-intro are example class names. Use the classes your own template puts on the short answer.
How long should a marked section be?
Google’s speakable documentation recommends around 20 to 30 seconds of content per section, or roughly two to three sentences.
The sentence you point to must actually appear on the page and stand on its own.
If you point to a messy block with subheadings, links and lists, the read-aloud result sounds unnatural. It will probably be ignored.
Test what you’ve added
Run the page through a validator after every template change.
Here’s our own English homepage in the Schema Markup Validator:
The Schema Markup Validator on our own English homepage, October 2026: WebSite and FAQPage detected, 0 errors, 0 warnings.
A speakable block would show up inside the detected Article or WebPage item. Our schema markup testing guide walks through the checks.
Markup follows structure
Speakable complements good content architecture. It doesn’t replace it.
The markup makes your structure explicit. But if the text holds no clean, self-contained answers, there’s nothing meaningful to point to.
So write the answers first, then mark them.
Which sections do you mark as speakable?
Only short, self-contained answer sentences that are fully correct when read aloud in isolation.
That’s the whole art.
Good candidates
These sections usually work:
- the opening sentence under a heading that directly answers the question
- a concise definition of a concept or product
- a summarising sentence with the key fact or figure
- a clear outcome or recommendation in one or two sentences
For example, “Speakable schema marks which sections of your page suit being read aloud” works on its own. You don’t need the rest of the page to understand it.
What you don’t mark
Leave these out:
- entire paragraphs full of context
- lists that lose their structure when spoken
- sentences with “as discussed above”
- tables, links and confusing abbreviations
Google adds three more: don’t mark datelines, photo captions or source attributions, because they sound confusing in voice-only settings.
Here’s the split in one picture:
The read-aloud test
A good test is simple. Read the marked sentence aloud without the rest of the page.
Does someone understand the answer right away? Then it’s a good speakable section. Do you need to add context? Then it isn’t.
Why this matches how AI cites
AI assistants look for the shortest passage that fully answers the question.
Whether or not you add speakable markup, self-contained answer sentences are the foundation of answer engine optimization.
We show the pattern in how to write content AI cites.
Does speakable schema really work for voice search and AI assistants?
The official Google feature is narrow today, but the underlying signal is genuinely useful.
Keep the two apart, or you’ll expect a return that isn’t there.
The official feature: beta, English, news
Google’s documentation says the feature “is in beta and subject to change”, and it’s aimed at news content.
It only works for users in the US whose Google Home devices are set to English, and for publishers who publish in English.
For a Belgian or Dutch B2B company publishing in its local language, that news feature delivers little to nothing.
Watch out: anyone who says speakable schema will catapult you into voice search tomorrow is exaggerating.
The broader value: one clear passage
Voice search and AI assistants run on the same mechanism. A system has to extract the shortest, most correct passage to read aloud or cite.
Here’s what that looks like in an AI assistant:
Claude, 17 October 2026, our own test prompt in an incognito chat: one turn, three labelled bullets, about 150 words.
Every bullet stands on its own. That’s the shape speakable asks you to write.
By pointing out which sentence is your core answer, you make that extraction easier. You also reduce the chance that a model picks the wrong passage.
It’s related to how AI decides which source and fragment it trusts, which we dig into in our piece on grounding.
No confirmed AI ranking factor
Whether the major AI assistants use speakable markup as a direct ranking factor today isn’t confirmed, so we won’t make that claim.
For its own AI Overviews and AI Mode, Google states that there’s no special schema.org structured data you need to add.
What is true: the discipline speakable enforces, short self-contained answers, is exactly what increases citability.
So the markup is more of a useful thinking exercise than a magic button.
Markup comes second; the answer comes first.
How does speakable fit into your GEO strategy?
Treat it as fine-tuning, not as a foundation.
Get the basics right first
These deliver the bulk of your AI visibility:
- clear headings that answer questions
- a self-contained opening sentence per section
- correct
ArticleorOrganizationmarkup - FAQPage schema where you really answer questions
Only then does it make sense to mark your strongest answer sentences with speakable.
Not sure how ready your pages are? The free GEO checker gives a first read.
A realistic approach in three steps
- For each important page, write an answer sentence that’s fully correct when read aloud on its own.
- Add that sentence to your existing JSON-LD with a
speakablespecification and a precise selector. - Keep it limited: one or two marked passages per page is enough, because more dilutes the signal.
For example, on a service page you’d mark the one-sentence definition of the service and the sentence that says who it’s for.
Is it worth your time?
For B2B companies where leads and revenue count, speakable schema is rarely your number one priority.
It’s not wasted effort, but the gain lies mainly in the writing discipline around it.
Rule of thumb: if your pages don’t yet answer questions in their first sentence, fix that before touching speakable.
Our generative engine optimization service handles the entire pipeline of being found in AI answers.
That’s where your time pays off most.
Frequently asked questions
Is speakable schema a ranking factor?
Not a confirmed one. Google’s speakable feature is a beta for English news on Google Home in the US, and Google says AI Overviews and AI Mode need no special schema.
Can I use speakable on a B2B service page?
Yes, the property is valid on Article and WebPage. Just don’t expect the Google Home news feature to read it out for non-news content.
Should I use cssSelector or xpath?
Either one, not both. A CSS selector is usually easier to maintain because it follows a class in your template.
How many sections should I mark?
One or two per page. Keep each to around 20 to 30 seconds of speech, roughly two to three sentences.
The short summary
Speakable schema uses a CSS selector or XPath to mark which sections of your page suit being read aloud.
The official Google feature is still beta and limited to English-language news, so the direct benefit for non-English B2B is small today.
The lasting value is the signal: you force yourself to write short, self-contained answer sentences. That’s exactly what AI assistants cite.
Use it as a refinement on top of a solid content structure, not as a starting point.
Want to know which schema and GEO measures deliver the most for your site?
Contact us and we’ll tell you within 24 hours where to start.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.