Speakable Schema for Voice AI: The Next AEO Frontier

Of all the tags in the SEO stack, Speakable might be the strangest. Google launched it in July 2018 for news publishers, to feed the News Briefing feature in Google Assistant ("Hey Google, what's the latest news on..."). Eight years on, Google's Search Central page for Speakable still says "(BETA)." The tag made it through the June 2025 rich-result cleanup that killed off a bunch of other markup types, and nobody has ever spelled out what graduating from Beta would look like for it.

The way I read it, Speakable is a small tag stuck in schema limbo, and only one product ever formally consumed it: Google Assistant News Briefings. That product is being folded into Gemini for Home. Meanwhile Alexa+, ChatGPT's GPT-Live, Perplexity Voice and Siri AI don't mention it anywhere in their public docs.

That's the bad news. The good news is that the writing Speakable pushes you toward (short answer passages that stand on their own, natural spoken phrasing, no acronyms or long numbers) is exactly what every LLM cites, whether the answer ends up read aloud or shown as text. So it's still worth doing, just for different reasons than the ones voice-search advocates were selling in 2019.

What Speakable actually is

In Schema.org terms, Speakable is a SpeakableSpecification type. It tells whatever is rendering the page, whether that's a voice assistant, a screen reader or a text-to-speech engine, which parts are worth reading aloud. By Schema.org's count it appears on somewhere between 100K and 1M domains, mostly because WordPress plugins add it automatically.

There are only two fields, cssSelector and xpath, and you use one of them. The property goes inside an Article, NewsArticle or WebPage block, and an array of selectors lets you mark several regions on the same page. A minimum working version looks like this:

{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".headline", ".summary"]
  }
}

Google's guidance is to aim for 20-30 seconds of read-aloud per section, about two to three sentences at a typical TTS pace. Mark the concise headline and the story summary or TL;DR, plus a key-fact answer paragraph if the page has one. Datelines and photo captions stay out, as do bylines and ads, and you should never mark the whole article or the navigation and footers.

On WordPress, Rank Math Pro ships a Speakable module and AIOSEO has one as well, while Yoast has no confirmed native support in its free version. On a custom stack, hand-coding the JSON-LD takes about five minutes per template.

The voice AI stack in 2026

Every major voice AI platform has been rebuilt in the last 18 months. Here's where Speakable stands on each of them, which is mostly nowhere:

Line them up like that and the pattern is hard to miss. Google's stack is the only one that ever formally supported Speakable, and even that support is quietly being transitioned. Everyone else does their own retrieval and their own summarization, and the tag doesn't enter into it.

Google is also changing how voice and AI answers fit together. Glenn Gabe caught it 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, 2025

Voice-triggered queries are being routed toward audio-first responses, pause controls included, which is a content-side signal even though it doesn't lean on Speakable directly. Barry Schwartz had 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, shipped in October 2025, matches spoken queries directly to results with no transcription-to-text step in between. That changes what voice-optimized content has to be. It now needs to be extractable phrase by phrase, where keyword-level matching used to be enough.

The real adoption numbers

Voice search advocates have been announcing a revolution since 2019, and it never came. It's worth getting the honest numbers straight before deciding how much time voice deserves.

In the US, smart-speaker ownership has been flat for four straight years at 35% of Americans aged 12 and up, about 101M people with 2.6 devices per household, according to NPR/Edison Research. That's a plateau. The same source puts the UK 10 points ahead at 45% of adults 16+.

Worldwide, smart-speaker shipments came to about 156M units in 2025, up 4% on the year. On mobile, the figure everyone quotes comes from GWI: 27% of internet users have used voice search on mobile in the past month. Voice's share of mobile search, meanwhile, has stabilized around 20% globally for the last two years. None of this looks like the exponential curve marketers predicted, even though voice AI is clearly real.

There is real appetite for a better home assistant, though. In September 2025 an r/ChatGPT thread asking why no ChatGPT-branded home device exists collected 600 upvotes and 150 comments in short order:

The top-voted reply called it "mind boggling" that real-time voice chat is basically perfected while Alexa still has no official ChatGPT support, and other users pointed to Alexa+ as the LLM-powered stopgap. So the demand exists, and the delivery surface is still consolidating. For content strategy that makes voice AI a growing but modest surface, a long way from the majority delivery mode, which puts Speakable in the low-investment hygiene column rather than the growth column.

RANKCONTROL

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.

Get started→

The content patterns that actually win

Here the playbook stops being about the tag and turns into a writing guide. The patterns Google's docs describe as "voice-optimized" are the same ones LLM extractive retrieval leans on for text answers, so writing to Speakable's rules pays off even if no voice engine ever reads your markup.

Start with the headings and phrase your H2s as questions: "What is X?", "How do I Y?", "Why does Z happen?". Voice queries come in as questions two to five times more often than typed ones, and the LLM retrieval layer lifts question-shaped H2s too, because the heading matches the surface of the query.

Right under each H2, put a 40-60 word answer paragraph. It's the passage a voice assistant would read aloud, and it's also the passage ChatGPT and Perplexity extract as a citation. Google's spoken voice responses average about 29 words, so write something a TTS engine can get through in under 30 seconds that is still complete enough to stand alone when quoted.

Write the way people talk. "You can add a webhook by clicking Settings" beats "Webhook configuration is accessed via the Settings interface," and prose that works for voice works for LLMs as well, since both surfaces are optimizing for extraction.

Acronyms need expanding before you lean on them. TTS engines spell them out awkwardly, and LLM extractors skip passages full of unresolved abbreviations, so write "Speakable schema (a SpeakableSpecification schema.org type)" and never hit a reader with "SS type" cold. Long numbers and ID codes don't belong in the speakable region either, since they're unreadable aloud and do nothing for extraction. If your product name is easy to mispronounce, use the brand name correctly and add phonetic guidance in the surrounding prose.

Last, give every page one clear TL;DR block. 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 those 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 comes down to content quality.

RANKCONTROL

Your competitors are building backlinks while you read this.

Organic outreach, social mentions, and link exchanges, with managed backlinks available as an add-on. Grow your domain authority without running the campaign yourself.

Start building links→

What not to mark speakable

Google's docs are explicit about what stays out of speakable markup. Datelines (where the story was reported) and photo captions don't belong, and neither do bylines and source attributions, which are what author schema is for. Navigation and footer copy are out, as are cookie banners and legal boilerplate. Ads and promotional interruptions don't qualify, and nor does content behind a paywall, because Google's general structured-data policy requires marked content to be crawlable and visible.

The classic over-marking mistake is wrapping <article> in a Speakable selector and calling it done. A whole article isn't speakable, but a single lead paragraph is, so point the selector at the summary instead of the entire body.

The bigger catch is that Google's official guidance ties Speakable eligibility to news content. On service pages, landing pages or evergreen SaaS content, the tag produces no rich result and isn't eligible for Google Assistant News Briefings. It won't hurt anything there, but it isn't doing what it does for news publishers either.

The practical playbook

The implementation comes down to three steps and about an hour of work.

1. Audit your top 20 pages. Look for a 40-60 word answer paragraph immediately under an H2, question-shaped H2 titles and a visible summary at the top. Where those are missing, rewriting for voice patterns is the bigger win, and Speakable schema comes after it.
2. Add Speakable to news-adjacent content. If you publish newsroom-style posts such as product updates, industry analysis or breaking news, mark the summary or lead paragraph through Rank Math Pro, AIOSEO or hand-coded JSON-LD, with a cssSelector targeting .summary or .tldr classes. Leave evergreen guides and landing pages alone, since the tag isn't eligible there.
3. Optimize for voice retrieval whether or not the tag is present, using the patterns from the section above. They compound across every AI engine, well beyond Google Assistant.

If you want to know whether your voice-optimized content is actually earning citations, our AI visibility tracking runs the buyer questions you choose across six AI engines every week, so you can see which of your pages get cited. Our content engine writes new articles with a short answer paragraph under each question-shaped heading. And for the broader schema layer that Speakable sits on, our Organization schema playbook covers the entity foundation those answer patterns feed into.

I expect Speakable to stay in Beta forever, and that's fine. It's a five-minute add-on that costs nothing to ship, so ship it, then put your real effort into the answer-first writing it forces on you, because that's the actual AEO move.

You're getting AI traffic. But do you know where it comes from?

RankControl credits every visit to the assistant that sent it: ChatGPT, Perplexity, Claude, Gemini, Copilot, or Grok. Full source attribution, next to your Google traffic.

Talk to us→