Speakable schema is one of the strangest tags in the SEO stack. Google launched it for news publishers in July 2018 (Search Engine Land coverage linked in Key Takeaways below), specifically to power Google Assistant's News Briefing feature ("Hey Google, what's the latest news on..."). Eight years later, Google's Search Central page for Speakable still carries the "(BETA)" tag. It survived the June 2025 rich-result cleanup that killed a bunch of other markup types. But nobody has ever quite said what "graduating from Beta" would look like for it.
The honest read: Speakable is a small tag, in schema limbo, that only one product (Google Assistant News Briefings) ever formally consumed. That product is being folded into Gemini for Home, and neither Alexa+ nor ChatGPT GPT-Live nor Perplexity Voice nor Siri AI reference it in their public docs. That's the bad news. The good news is that the writing patterns Speakable forces you to adopt (short standalone answer passages, natural spoken phrasing, no acronyms or long numbers) are the exact patterns every LLM cites, whether the delivery surface is voice or text. So it's still worth doing, just for different reasons than voice search advocates were selling in 2019.
Key Takeaways
- Speakable has been Beta at Google for eight years since its July 2018 launch and appears on somewhere between 100K and 1M domains per Schema.org, mostly via WordPress plugins that auto-add it.
- US smart-speaker ownership plateaued at 35% of Americans age 12+ (~101M people, ~2.6 devices per household), flat for four years per NPR/Edison Research. Voice AI is real but not the exponential curve marketers predicted.
- Google shipped a new Speech-to-Retrieval (S2R) model in October 2025, matching spoken queries directly to results without a text-transcription step. Alexa+, GPT-Live, Perplexity Voice, and Siri AI all use their own voice retrieval pipelines.
- Optimal Speakable passage: 20-30 seconds of read-aloud, roughly 50-75 words, two to three sentences. Google explicitly recommends marking a lead paragraph or summary block, not the whole article.
- The content patterns win, not the tag. 40-60 word answer paragraphs under question-shaped H2s, natural phrasing, no acronyms, one clear TL;DR per page. These patterns feed both Speakable and every LLM's extractive retrieval.
What Speakable Actually Is
Speakable is a SpeakableSpecification type in Schema.org that tells a rendering system (voice assistant, screen reader, text-to-speech engine) which portions of a page are worth reading aloud. It has two fields, cssSelector and xpath, and you pick one. The property lives inside an Article, NewsArticle, or WebPage block, and you can pass an array of selectors to mark multiple regions on the same page.
The minimum viable implementation looks like this:
{
"@context": "https://schema.org",
"@type": "NewsArticle",
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": [".headline", ".summary"]
}
}
Google's guidance says to target 20-30 seconds of read-aloud per section, which works out to roughly two to three sentences at typical TTS pace. Mark the concise headline. Mark the story summary or TL;DR. Mark a key-fact answer paragraph if the page has one. Don't mark datelines, photo captions, bylines, or ads. Don't mark the whole article, and don't mark navigation or footers.
Rank Math Pro ships a Speakable module for WordPress. AIOSEO has one too. Yoast has no confirmed native support in the free version. If you're on a custom stack, hand-coded JSON-LD takes about five minutes per template.
The Voice AI Stack in 2026
Every major voice AI platform got refreshed in the last 18 months. Here's the state of play and where Speakable fits (or doesn't).
Google Assistant → Gemini for Home. Google shipped the Google Home Speaker on June 25, 2026, the first purpose-built Gemini for Home device. Legacy Assistant is being rolled into the same platform. News Briefings still exist and still (per Google's docs) reference Speakable-flagged content. Whether Gemini for Home continues to consume Speakable markup is not publicly documented.
Alexa+. Amazon launched Alexa+ on February 26, 2025, using Amazon Nova + Anthropic models. Uses partner integrations (Angi, Expedia, Yelp, OpenTable, Fodor's, Ticketmaster) for structured data, not Speakable schema.
ChatGPT GPT-Live. OpenAI retired Advanced Voice Mode on July 8, 2026 and replaced it with GPT-Live, a full-duplex voice architecture. Uses GPT-5.5 with web search behind the scenes. No Speakable reference.
Perplexity Voice. Uses OpenAI's Realtime API plus Perplexity's citation-first RAG. First spoken response under one second. Uses the same sources as text-mode Perplexity.
Siri + Apple Intelligence. WWDC 2026 unveiled "Siri AI" using Apple Intelligence on-device + Google Gemini for advanced web queries. No public Speakable commitment.
The pattern is clear. Only Google's stack ever formally supported Speakable, and even that support is quietly being transitioned. Every other major voice AI does its own retrieval and its own summarization, ignoring the tag.
Glenn Gabe surfaced a related shift in how Google itself is fusing voice search with AI Overview responses:
Another twist with the audio icon in AIOs. If you use voice search, you have a greater chance at seeing the audio option (at least based on my testing). That makes sense since you are going to get an audio response so Google is adding the audio icon -- with the ability to pause
Glenn Gabe@glenngabeDec 29, 2025Google is routing voice-triggered queries toward audio-first responses, complete with pause controls. That's a content-side signal even if it doesn't lean on Speakable directly. Barry Schwartz flagged the deeper architectural change earlier:
ICYMI: Google Voice Search updated to Speech-to-Retrieval (S2R) https://t.co/a9E6QkxQ7M https://t.co/oGCCfLVAFb
Barry Schwartz@rustybrickOct 10, 2025
Google's Speech-to-Retrieval (S2R) model matches spoken queries directly to results without transcribing to text first. Which changes what "voice-optimized content" needs to look like: it needs to be extractable at the phrase level, and no longer only at the keyword level.
The Real Adoption Numbers
Voice search advocates have been predicting a revolution since 2019. The revolution didn't come, and the honest numbers matter for calibrating how much time to invest.
US smart-speaker ownership: 35% of Americans age 12+ (~101M people), 2.6 devices per household, per NPR/Edison Research linked in the Key Takeaways above. Flat for four straight years. Plateau, not growth.
UK ownership: 45% of adults 16+ (10 points ahead of US), same source.
Global smart-speaker shipments: ~156M units in 2025, +4% year over year.
Voice share of mobile search: Widely-cited "27% of internet users have used voice search on mobile in the past month" figure, from GWI. Stabilized around 20% globally for the last two years.
There's real consumer appetite for a better home voice AI experience, though. An r/ChatGPT thread from September 2025 asking why no ChatGPT-branded home device exists collected 600 upvotes and 150 comments in short order:
Why is there no ChatGPT home device like Alexa?
I’m thinking of setting up an old iPad with ChatGPT running in the background.
The top-voted reply called it "mind boggling" that real-time voice chat is basically perfected but Alexa still has no official ChatGPT support. Users flagged Alexa+ as the LLM-powered stopgap. The pent-up demand is real; the delivery surface is still consolidating.
For content strategy, the takeaway is that voice AI is a growing but modest surface, not a majority delivery mode. Which means Speakable is a low-investment hygiene move, not a growth channel.
See your first AI citation report in under 5 minutes.
No setup calls. No onboarding meetings. Connect your domain and see where AI mentions your brand right now.
The Content Patterns That Actually Win
This is where the Speakable playbook stops being about the tag and starts being about the writing. The patterns that Google's docs describe as "voice-optimized" are the exact patterns LLM extractive retrieval leans on for text answers too. So writing to Speakable's rules pays off even if no voice engine ever reads your markup.
Question-shaped H2s. "What is X?", "How do I Y?", "Why does Z happen?". Voice queries are phrased as questions two to five times more often than typed queries, but the LLM retrieval layer also lifts these because the H2 matches the query surface.
A 40-60 word answer paragraph immediately under each H2. This is the passage a voice assistant would read aloud, and it's also the passage ChatGPT and Perplexity extract as citations. Google's voice responses average about 29 words spoken; your answer paragraph should be short enough that a TTS engine can read it in under 30 seconds and complete enough that it stands alone when quoted.
Natural conversational phrasing. "You can add a webhook by clicking Settings" beats "Webhook configuration is accessed via the Settings interface." Voice-optimized prose is also LLM-friendly prose, because both surfaces are optimizing for extraction.
No acronyms unless expanded first. TTS engines spell them out awkwardly; LLM extractors skip passages full of unresolved abbreviations. "Speakable schema (a SpeakableSpecification schema.org type)" is the pattern. Never "SS type" cold.
Avoid long numbers and ID codes in the speakable region. Unreadable aloud, and they don't help extraction.
Use the brand name correctly. Add phonetic guidance in the surrounding prose if your product name is easily mispronounced.
One clear TL;DR block per page. Whether or not you mark it speakable, an explicit summary at the top gets cited disproportionately by every AI engine because it's the passage most likely to answer a question in isolation.
Ship these patterns, mark the top summary block with Speakable in your Article schema, and you've done everything reasonable for voice AI in about an hour. The rest is content quality.
Your competitors are building backlinks while you read this.
Organic outreach, social mentions, exchanges, and done-for-you link building. Four ways to grow your domain authority on autopilot.
What NOT to Mark Speakable
Google's docs are explicit about several categories that don't belong in speakable markup.
- Datelines (where the story was reported).
- Photo captions.
- Bylines and source attributions (that's what author schema is for).
- Navigation and footer copy.
- Cookie banners and legal boilerplate.
- Ads and promotional interruptions.
- Content behind paywalls (Google's general structured-data policy requires the content to be crawlable and visible).
The over-marking failure mode is: someone wraps <article> in a Speakable selector and calls it done. The whole article isn't speakable. A single lead paragraph is. Fix the selector to target the summary, not the entire body.
And a bigger issue: Speakable eligibility is tied to News content in Google's official guidance. Marking Speakable on service pages, landing pages, or evergreen SaaS content does not produce a rich result and is not eligible for Google Assistant News Briefings. The tag doesn't hurt anything, but it's not doing what news publishers do with it either.
The Practical Playbook
Three-step implementation, about an hour of work.
Step 1: Audit your top 20 pages. Do they have a 40-60 word answer paragraph immediately under an H2? Question-shaped H2 titles? A visible summary at the top? If not, rewriting them for voice patterns is the bigger win. Speakable schema is downstream of that.
Step 2: Add Speakable to news-adjacent content. If you publish any newsroom-style posts (product updates, industry analysis, breaking news), add Speakable to the summary or lead paragraph via Rank Math Pro, AIOSEO, or hand-coded JSON-LD. cssSelector targeting .summary or .tldr classes. Don't add it to evergreen guides or landing pages; the tag isn't eligible there.
Step 3: Optimize for voice retrieval independently of the tag. Question-shaped H2s, 40-60 word answers, natural phrasing, no acronyms, TL;DR block. These patterns compound across every AI engine, well beyond Google Assistant alone.
If you want to see whether your voice-optimized content is actually earning citations, our AI visibility tracking samples the exact voice-style prompts your buyers ask across ChatGPT, Perplexity, Google AI Mode, and Gemini so you can see which of your pages are getting pulled into voice-shaped answers. Our content engine uses those signals to refresh the 40-60 word answer blocks where the citation rate is highest. And if you're building the broader schema layer that Speakable sits on, our Organization schema playbook covers the entity foundation the answer patterns feed into.
Speakable will probably stay in Beta forever. That's fine. The answer-first content patterns it forces you to write are the actual AEO move. The tag is a five-minute add-on that costs nothing to ship. Ship it, then focus on the writing.
You're getting AI traffic. But are you capturing the leads?
RankControl tracks every visitor from ChatGPT, Perplexity, and Claude. Full source attribution, intent scoring, and A/B tested lead capture.
