The short answer
Speakable is still a beta feature, restricted to English-language news content, for users in the United States, on Google Home devices. Those limits are Google’s own, and they have not changed since the feature was introduced in 2018.
If you are not a news publisher targeting US smart-speaker users, speakable markup will do nothing for you. It will not help you get cited by ChatGPT, Perplexity, Claude or Google’s AI Overviews, because none of them use it.
Speakable comes up constantly in answer-engine-optimization advice, usually in a list of “schema types you need for AI search”. It is a strange survivor. A 2018 beta aimed at smart speakers has been quietly rebranded as an AI-search tactic, mostly by people repeating each other.
So before the tutorial, the eligibility check. It rules out almost everyone.
What Google actually says
| Constraint | Google’s stated position |
|---|---|
| Status | “This feature is in beta and subject to change.” |
| Country | Users in the U.S. only |
| Language | English only, for publishers publishing in English |
| Device | Google Home devices set to English |
| Content type | Article and WebPage, used for “topical news queries” |
| Guarantee | “Google does not guarantee that features that consume structured data will show up in search results.” |
Source: Google Search Central, Speakable structured data. Retrieved July 2026. Google adds that it hopes “to launch in other countries and languages as soon as sufficient number of publishers have implemented speakable“, wording that has stood for years.
Myth
Speakable schema helps you get quoted by AI answer engines.
Speakable is consumed by the Google Assistant for news queries on smart speakers. No large language model provider has stated that speakable markup influences citation. Marking up a SaaS landing page with speakable does nothing, in any engine.
Should you implement it? A 15-second decision
Not sure which of your pages are actually hard for an engine to extract? The free Content Gap Scanner grades every post. Download it free.
If you passed all three, here is the markup
Speakable takes CSS selectors or XPath pointing at the parts of the page suitable for audio playback. Google recommends the headline and a short summary, not the full article.
{
"@context": "https://schema.org",
"@type": "NewsArticle",
"headline": "Council approves the riverside development",
"speakable": {
"@type": "SpeakableSpecification",
// Point at the headline and a one or two sentence summary only
"cssSelector": [".article-headline", ".article-summary"]
}
}Pro tip
Whatever you select gets read aloud by a synthetic voice. Test it by reading it out yourself. Anything with a bracketed aside, a stray “click here”, or a sentence over about 25 words will sound broken. Selecting your whole intro paragraph is the most common mistake.
Where that effort is better spent
The instinct behind searching for speakable is usually sound: you want your content to be the bit that gets read out or quoted. That instinct is right. Speakable is just the wrong lever.
These do the same job, and unlike speakable they work regardless of country, language or device.
A direct answer in the first 60 words
Answer the question in full sentences immediately under the heading, with no dependence on earlier context. This is the block an extractor is most likely to lift.
Question-shaped headings
A heading that matches the question, with the answer directly beneath it, gives a retriever a clean unit to pull. It also reads well for humans, which speakable never did.
Self-contained paragraphs
A paragraph that starts “This is why it matters” is useless out of context. One that names its subject can be quoted anywhere.
FAQPage schema
Unlike speakable, it is not restricted by country or device, and the question-and-answer pairing maps directly onto how answers get assembled.
The honest version
No structured data type has been shown to make a language model cite you. What structure does is make your content easy to extract cleanly, so that when a model has already decided to use your page, it can lift a coherent passage rather than a fragment. That is a real benefit. It is just a smaller and more specific one than “add schema, get cited”.
Is speakable being deprecated?
Google has not announced deprecation. It also has not moved it out of beta, expanded it beyond the US, or added a language in the years since launch. Treat it as stable but frozen: harmless to keep if you already have it, not worth adding if you do not.
If you already implemented it and want to know whether it is doing anything, the honest test is whether you receive Google Assistant traffic from smart speakers at all. For almost every site, that number is zero, and no amount of markup changes it.
Find the pages that are hard to extract
The Content Gap Scanner grades every post and shows what is missing, so you can fix structure rather than chase markup that no engine reads.
- Per-post AEO grade
- Spot missing summaries and schema
- Free, no account, no card
Keep reading
Schema validator: check your markup and understand what the errors mean
Valid, eligible and shown are three different things. Plus the errors nobody explains.
Answer engine optimization for WordPress: the complete setup
Access, structure and measurement. Ordered by how much the evidence supports each step.
Person schema and E-E-A-T for AEO: the setup that actually validates
Google says E-E-A-T is not a ranking factor. Here is what Person schema really does.
Frequently asked questions
Is speakable schema still supported in 2026?
Yes, but it remains a beta feature. Google’s documentation still describes it as “in beta and subject to change”, still limits it to users in the United States on Google Home devices set to English, and still limits it to English-language publishers.
Does speakable schema help with AI search or getting cited by ChatGPT?
No. Speakable is consumed by the Google Assistant for topical news queries on smart speakers. No language model provider has stated that speakable markup influences whether a page is cited.
Which schema types support speakable?
Google documents speakable support for the Article and WebPage types, with news content as the primary use case.
Should a non-news website add speakable markup?
No. The feature is aimed at topical news queries for US smart-speaker users. On a non-news site it has no documented effect. Effort is better spent on direct answers, question-shaped headings and self-contained paragraphs.
What should I use instead of speakable?
Write a direct answer in the first 60 words under each heading, use question-shaped headings, keep paragraphs self-contained so they survive being quoted out of context, and add FAQPage schema where genuine questions exist. None of these are restricted by country, language or device.