What Speakable Schema Actually Is
When someone asks a voice assistant a question, the assistant has to pick a sentence — or a few sentences — to read aloud. It can't recite your whole page. So it makes a judgment call: which part of this content sounds most like a direct answer?
Speakable schema is how you take that judgment call away from the algorithm and make it yourself.
Formally, speakable is a property on the Schema.org Article type that accepts either CSS selectors or XPath expressions pointing to specific sections of your page. When a voice assistant or AI search engine encounters that markup, it knows: these are the sentences the publisher considers most suitable for audio playback.
Google introduced support for speakable in 2018 for news publishers, but its relevance has expanded considerably as AI-generated answers — in Google's AI Overviews, Perplexity, and smart-speaker responses — increasingly draw from structured data rather than raw HTML parsing.
Why It Matters More Now Than It Did in 2018
In 2018, speakable schema was mostly a news-publisher tool. Google used it to feed content to Google Assistant on smart speakers. Most small-business owners had no reason to care.
That's changed for a few reasons:
Voice search volume has matured. Roughly 27% of the global online population uses voice search on mobile, and smart-speaker households routinely ask local questions — hours, directions, availability, pricing — that your business page should be answering.
AI search engines parse structured data first. Systems like Google's AI Overviews and Perplexity don't just scrape text; they weight content that has been explicitly labeled. A page with speakable markup signals to those systems: this section was written to be a direct answer. That signal matters.
The gap between a good page and a spoken answer has widened. You can have excellent content that ranks well in blue-link results and still get skipped entirely in voice results, because voice engines need a clean, self-contained sentence — not a well-structured paragraph. Speakable markup bridges that gap by pre-selecting your best sentences.
As the broader shift toward AI-driven search answers continues, the pages that have done the work of labeling their most answer-ready content will have a structural advantage over those that haven't.
What Content Should Be Marked Speakable
Not everything on your page deserves to be read aloud. Voice assistants have roughly 20–30 seconds of listener patience before attention drops. That means your speakable-tagged content needs to be short, self-contained, and factually complete.
Good candidates:
- Definitions and direct answers — "Our cancellation policy requires 24 hours' notice."
- Business hours and location details — "We're open Monday through Saturday, 9 a.m. to 6 p.m."
- FAQ-style responses — The answer sentence in a Q&A block, not the surrounding context.
- Key claims or summaries — The first sentence of a section that could stand alone as an answer.
- Pricing or service details — "Haircuts start at $35 for adults."
Bad candidates:
- Long paragraphs that require context to make sense
- Sentences with pronouns that reference earlier content ("It works by...")
- Calls to action ("Click here to book")
- Navigation text, headers, or boilerplate
The test: if someone heard only that sentence with no context, would it answer a reasonable question completely? If yes, it's speakable. If it needs setup, it isn't.
The Technical Mechanics
Speakable schema is implemented in JSON-LD, the same format used for FAQ, HowTo, and LocalBusiness schema. It lives in a <script type="application/ld+json"> block in your page's <head> or just before </body>.
Here's the basic structure:
{
"@context": "https://schema.org",
"@type": "Article",
"name": "Your Page Title",
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": [".speakable-intro", ".faq-answer", "#hours-summary"]
},
"url": "https://yourdomain.com/your-page"
}
The cssSelector array points to elements on your page by their CSS class or ID. When Google's crawler or a voice assistant hits your page, it looks for those elements and treats their text content as your speakable passages.
Alternatively, you can use xpath instead of cssSelector if your CMS generates predictable XPath structures — but CSS selectors are easier to maintain for most owner-operators.
One important note: your CSS selectors have to actually match elements that exist on the rendered page. If you tag .faq-answer but your CMS renders FAQ answers as .faq__body, the markup will point at nothing. Always verify with Google's Rich Results Test after implementation.
Speakable Schema vs. Other Schema Types
Speakable doesn't replace your other structured data — it works alongside it. Here's how the types relate:
- FAQPage schema tells search engines you have a Q&A block and surfaces the Q&A in rich results. Speakable tells voice assistants which of those answers to read aloud.
- LocalBusiness schema provides your NAP (name, address, phone), hours, and service area. Speakable complements it by flagging the human-readable summary of that information.
- HowTo schema structures step-by-step content. Speakable can tag the intro sentence of each step if it reads cleanly in isolation.
- DefinedTerm schema labels definitions. If you have a definition that also qualifies as speakable, you can implement both.
Think of speakable as the audio layer on top of your existing structured data strategy. It doesn't replace any of the other types — it adds a voice-specific signal that the others don't provide.
For a broader look at how website content structure affects AI search engines, the principles overlap: both reward content that is organized, labeled, and self-contained at the sentence level.
How Speakable Fits Into AEO (Answer Engine Optimization)
Answer Engine Optimization is the practice of structuring content so that AI systems — not just human readers — can extract and surface accurate answers. Speakable schema is one of the most direct AEO tools available because it's the only schema type that explicitly addresses the audio output use case.
Most AEO work focuses on making content machine-readable: clear headers, short paragraphs, FAQ blocks, schema markup. Speakable takes that one step further by saying: among all the machine-readable content on this page, these specific sentences are optimized for being spoken aloud.
For local businesses, this is particularly high-value. Voice queries skew heavily local and transactional — "what time does [business] close," "does [business] take walk-ins," "how much does [service] cost." These are exactly the kinds of short, factual answers that speakable markup is designed to surface.
Voice engines don't read your page — they pick a sentence. Speakable schema lets you choose which one.
Common Implementation Mistakes
Tagging too much. If you mark 15 different elements as speakable, you've given the voice assistant no real guidance. Prioritize 2–4 elements per page.
Using selectors that don't exist. Always verify your CSS selectors against the actual rendered HTML. CMS themes often add prefixes or modify class names.
Tagging content that requires context. "As mentioned above, this approach works best when..." is not speakable. It needs context to make sense.
Forgetting to include the url property. Google's implementation requires the url property on the Article object to associate the speakable content with the correct page.
Not testing after CMS updates. If your theme updates or your CMS changes how it renders elements, your selectors may break silently. Schedule a quarterly check with the Rich Results Test.
Who Should Prioritize This
Speakable schema delivers the most value for:
- Local service businesses (salons, restaurants, clinics, auto shops) where customers ask voice assistants about hours, location, and availability
- Content publishers with FAQ-heavy or definition-heavy pages
- E-commerce stores with product pages that answer common questions (sizing, materials, shipping times)
- Professional services (lawyers, accountants, consultants) where clients ask qualifying questions before calling
If your site already has structured data for local business and you're investing in AEO, speakable is the logical next layer. It takes less than an hour to implement on a page and doesn't require any changes to your visible content or site design.
