Speakable Schema

TL;DR — Speakable schema is a bit of code that points at the specific sentences on a page — not the whole article — that a machine should read aloud, like a smart speaker answering a news question. In 2026 it’s still a small, test-only Google feature: it only works for people in the U.S. with Google Home devices set to English. And despite what a lot of SEO articles claim, it does not help you show up in Google’s AI Overviews.

What Speakable schema is

Most structured data labels what a thing is — “this is the price,” “this is the author.” Speakable does something different: it points at the parts of a page that are best to read out loud. Imagine asking a smart speaker for the news — it can’t read a whole article to you, so Speakable schema tells it which two or three sentences to speak.

You add it as a small piece of code (usually JSON-LD) that names the sentences by their location on the page — either by a CSS class or by an XPath. You pick one of those two methods, not both. Google recommends marking up about 20–30 seconds of audio, or roughly two to three sentences — a concise headline and summary that make sense on their own.

Who can actually use it

This is the part most articles skip. Speakable has been a beta feature since 2018, and Google’s own page — updated as recently as December 2025 — still says it only works for:

• users in the United States,
• on Google Home devices,
• set to English, and
• for publishers who publish in English.

It’s not just an inferred pattern, either — Google’s own setup instructions say it outright: “For your news content to be eligible as answers to topical news queries, follow these steps.” News content is a stated requirement, not a convention. If you’re not a US, English-language news site, it was never really aimed at you.

The thing most people get wrong

You’ll see 2026 SEO articles claim Speakable now helps you get cited in Google’s AI Overviews or AI Mode. There’s no evidence for that — Google has never said it, and it isn’t listed anywhere in Google’s AI documentation. Speakable was built for one thing: reading news aloud on Google Home speakers. Adding it will not get your page picked as an AI answer.

It’s also not deprecated — the page is live and still maintained. It’s just narrow and quiet. Want the full picture, including the JSON-LD, why the whole feature’s future is genuinely uncertain, and whether it’s worth your time? Switch to the Advanced tab.

TL;DR — Speakable is the speakable property (value: a SpeakableSpecification object) on Article/WebPage — not a standalone type. It marks the 2–3 sentences (~20–30s) best read aloud by TTS, located by one of cssSelector or xPath. It’s been explicitly BETA since July 2018 and, per the doc updated December 2025, is still limited to US, English, Google Home users. It survived Google’s January 2026 structured-data cleanup and wasn’t mentioned at I/O 2026 — so it’s dormant, not deprecated. Two accuracy spines: (1) no Google-official source connects Speakable to AI Overviews / AI Mode — that’s a repeated-but-unsourced 2026 myth; and (2) the Google Assistant it feeds is being replaced by Gemini for Home, and nobody has said whether Gemini for Home still consumes Speakable. Treat it as a US-news-publisher relic, not an AI-search lever.

What Speakable actually is

Google’s framing is precise: “The speakable property identifies sections within an article or webpage that are best suited for audio playback using text-to-speech (TTS).” (Google Search Central) The important structural point: it is not its own schema type. It’s the speakable property, whose value is a SpeakableSpecification object, and you attach it to an Article or a WebPage (a NewsArticle works too, by schema.org inheritance from Article).

And you don’t mark up the whole page. You point at the 2–3 sentences — the headline and a concise summary — that stand on their own when read out of visual context to a listener. That “sections, not the whole article” distinction is the entire design intent.

Locating the speakable content: cssSelector vs xPath

You pick exactly one of two locator methods — never both on the same markup:

• cssSelector — “Addresses content in the annotated pages (such as class attribute).” You target elements by class or CSS path (e.g. .headline, .summary).
• xPath — “Addresses content using xPaths (assuming an XML view of the content).” You target elements by their XPath (e.g. /html/head/title).

cssSelector is the more maintainable choice for most sites because it survives markup reshuffles better than a brittle absolute XPath — but both are valid.

One spelling gotcha worth knowing before you copy an example from the wrong place: schema.org’s own vocabulary page spells the underlying property lowercase, xpath, while Google’s Speakable doc and every JSON-LD example on it use camelCase, xPath. Since it’s Google Assistant consuming this markup, follow Google’s xPath casing in your JSON-LD — the schema.org page defines the broader vocabulary, not the property name Google’s parser expects.

Content guidelines that still hold up

Even outside Speakable’s own eligibility, its content rules are good TTS advice:

• Length. Google: “For optimal audio user experiences, we recommend around 20-30 seconds of content per section of speakable structured data, or roughly two to three sentences.” (Google Search Central)
• Avoid context-dependent text. Google: “Don’t add speakable structured data to content that may sound confusing in voice-only and voice-forward situations, like datelines (location where the story was reported), photo captions, or source attributions.” (Google Search Central)
• Write concise, self-contained summaries. Google: “Content indicated by speakable structured data must have concise headlines and/or summaries that provide users with comprehensible and useful information.” (Google Search Central)

Who can actually use it — still narrow in 2026

Here’s where honesty matters. The feature is still explicitly BETA — Google: “This feature is in beta and subject to change.” (Google Search Central) That’s not a stale doc I’m quoting: the page footer reads “Last updated 2025-12-10 UTC,” so Google is still touching it — it just hasn’t changed the scope.

And the scope is exactly what it was at the 2018 launch. Google: “The speakable property works for users in the U.S. that have Google Home devices set to English, and publishers that publish content in English.” (Google Search Central) Google adds it hopes to launch in other countries and languages “as soon as sufficient number of publishers have implemented speakable” — a promise first made in 2018 that, as of the December 2025 doc, is still unfulfilled seven-plus years later. When I see a “we hope to expand soon” line that has sat unchanged for seven years, I read it as a promise that quietly expired, not a roadmap.

That US/English/Google Home line is only half the eligibility bar. The doc’s own “Getting started” section states the other half directly: “For your news content to be eligible as answers to topical news queries, follow these steps.” (Google Search Central) News content isn’t a genre I’m inferring from context — it’s the explicit subject of the section that tells you how to become eligible.

What it feeds is equally specific: “The Google Assistant uses speakable structured data to answer topical news queries on smart speaker devices.” (Google Search Central) Note what that is not: it never produced a visible SERP rich result the way Review stars or Breadcrumbs did. Its entire output surface was audio on a Google Home device.

Is it dead? No — but read the signals carefully

Three checkable facts, none of which say “deprecated”:

• It survived the January 2026 cleanup. Google’s late-2025/early-2026 structured-data pruning removed support for a batch of rich-result types (Search Engine Land coverage). Speakable was not on that list — neither killed nor reaffirmed. Just untouched.
• It wasn’t mentioned at I/O 2026. I went through Google’s I/O 2026 Search recap and the roundups — no Speakable mention in any Search announcement. Consistent with a feature Google maintains but no longer promotes.
• Adoption is real but tiny. schema.org’s SpeakableSpecification page reports usage in the “100K–1M domains” band (attributed to Google, May 2026) — genuine adoption, but a rounding error next to Article- or Organization-scale types.

None of those three facts is a Google statement about Speakable’s lifecycle — Google hasn’t called it dormant, active, or anything else. “Dormant and narrow” is my read of the pattern those facts form, not something Google has confirmed either way. So: dormant and narrow is my inference from that pattern; deprecated is not — Google hasn’t said either. John Mueller’s framing during the January 2026 removals discussion is the right lens for all schema of this kind — “Understand that markup types come and go, but a precious few you should hold on to (like title, and meta robots).” (Search Engine Roundtable) Speakable is squarely in the “come and go” bucket, not the “hold on to” one. Mueller’s Reddit remark is relayed via Search Engine Roundtable; the original page blocked direct verification this session, so treat it as secondary-sourced.

The elephant in the room: Assistant → Gemini for Home

Here’s the genuinely current, under-covered part. Speakable’s entire consumer is the Google Assistant reading news on Google Home. And throughout 2026 Google is replacing the Google Assistant with Gemini for Home — the first purpose-built device, the Google Home Speaker, shipped in June 2026, and Gemini for Home is expanding to more third-party speakers this year.

Now connect the dots: no source — not Google’s Speakable doc, not the Gemini for Home launch material, not any SEO commentary I could find — says whether Gemini for Home still consumes Speakable markup the way the Assistant did. The doc talks about “the Google Assistant”; the Assistant is being sunset; and the two pages never mention each other. That’s not me predicting doom — it’s an open, unresolved status question that I’d treat as the single biggest reason to be cautious here. Frame it as an open question, not a fact in either direction.

Does Speakable help with AI Overviews or AI Mode? Not a documented lever.

This is the other accuracy spine, and it’s where a lot of 2026 content is simply wrong. A wave of “GEO”/AI-search posts assert that Speakable now signals “citation-worthy passages” to AI Overviews or AI Mode. No Google-official source supports that. Google’s own AI-features doc is direct about the general point: “There’s also no special schema.org structured data that you need to add” to appear in AI Overviews or AI Mode. (Google Search Central) That’s Google ruling out a “special markup” requirement in general — it isn’t a Speakable-specific statement, so I’m careful not to stretch it into “Google says Speakable has zero effect.” The one industry analysis that checked the Speakable-specific claim (SEO Strategy Ltd, Sept 2025) states it plainly: “Speakable does not influence AI Overviews. Google does not use speakable selectors when deciding what to include in its AI-generated summaries.” Absence of documentation isn’t proof of zero effect — but there’s also no evidence of a positive one, and the honest label is “not a documented lever or requirement,” not a hedge-free “it does nothing.” SEO Strategy Ltd is industry analysis, not a Google statement — but it’s the one source that directly tested the claim rather than repeating it.

The broader evidence points the same way. Ahrefs tracked 1,885 pages adding schema (JSON-LD added Aug 2025–Mar 2026, measured against AI Overviews, AI Mode, and ChatGPT citations) and found no meaningful citation uplift from adding schema broadly. That study isn’t Speakable-specific, but it’s directly relevant to the “add Speakable and get cited by AI” pitch: the general lever those posts assume doesn’t show up in the data. If you’ve read the structured-data hub, this is the same story as every other “schema for AI citations” claim — schema is entity infrastructure, not a citation cheat code.

Should you implement it in 2026?

• Maybe worth it: you’re a US, English-language news publisher already invested in Google Home audio, the marginal cost is low, and you want to cover the one narrow surface it feeds. Even then, weigh the Gemini-for-Home uncertainty.
• Very likely wasted effort: you’re outside US/English, you’re not a news publisher, or — most commonly — you’re adding it because a listicle told you it helps AI search. It doesn’t. Spend that effort on Organization/Person entity markup with correct sameAs values instead, which is the schema that actually helps machines resolve who you are.

Where this sits

Speakable belongs to the same practitioner grouping as page-level metadata-trust markup — a type whose one flagship use case (here, Google Home news readback) went quiet while the underlying schema.org type itself was never deprecated. It’s a sibling deep-dive off the Structured Data for SEO hub, alongside schema markup, JSON-LD, and rich results. Like the WebSite/sitelinks- searchbox pattern, it’s a useful case study in reading a schema type honestly: not dead, but not the thing the hype says it is.

AI summary

A condensed take on the Advanced version:

• What it is. Speakable is the speakable property (value: a SpeakableSpecification object) on Article/WebPage — not a standalone type. It marks the 2–3 sentences (~20–30s) best read aloud by text-to-speech, not the whole article.
• How you point at content. Exactly one locator: cssSelector or xPath, never both. Google recommends concise, self-contained headlines/summaries and says to avoid datelines, captions, and source attributions.
• Who can use it — still narrow. Explicitly BETA since July 2018; per the doc updated Dec 2025, limited to US, English, Google Home users, English publishers, and — stated directly in Google’s own setup steps — news content. It never produced a visible SERP rich result — its only output was audio on Google Home.
• Not dead, just dormant (my read of the pattern, not a Google statement). It survived Google’s January 2026 structured-data cleanup and wasn’t mentioned at I/O 2026. schema.org usage sits at 100K–1M domains (Google, May 2026) — real but tiny.
• Accuracy spine #1 — not a documented AI-Overviews lever. No Google source ties Speakable to AI Overviews / AI Mode citation, and Google’s AI-features doc says outright there’s “no special schema.org structured data” needed for those features. SEO Strategy Ltd states Google doesn’t use speakable selectors for AI summaries; an Ahrefs 1,885-page study found no citation lift from adding schema broadly. Absence of evidence isn’t proof of zero effect, but the “Speakable feeds AI citations” claim has no documented support.
• Accuracy spine #2 — the Assistant is being replaced. Google is swapping the Google Assistant (Speakable’s only consumer) for Gemini for Home in 2026 (Google Home Speaker shipped June 2026). No source says whether Gemini for Home still reads Speakable — treat it as an open question.
• Should you bother? Maybe, if you’re a US/English news publisher on Google Home. Otherwise it’s very likely wasted effort — especially if you’re adding it “for AI search.” Do Organization/Person + sameAs entity markup instead.

Official documentation

Primary-source documentation and the underlying vocabulary.

Google

• Speakable (BETA) Schema Markup — the core doc: definition, the US/English/Google Home eligibility, the cssSelector vs xPath methods, content guidelines, and the “in beta and subject to change” label (last updated 2025-12-10 UTC).
• Intro to How Structured Data Markup Works — where Speakable sits among the formats and the broader rich-result picture.
• AI Features and Your Website — Google’s statement that there’s “no special schema.org structured data that you need to add” for AI features (context for the AI-Overviews myth-bust).
• Google Home Speaker, built for Gemini — the Gemini-for-Home launch that never mentions Speakable, and the flip side of the Assistant transition.

schema.org

• SpeakableSpecification — the underlying type: “sections of a document that are highlighted as particularly speakable,” its cssSelector/xpath properties, and the usage stat (100K–1M domains).
• speakable — the property itself, as used on Article and WebPage.

Bing / Microsoft

• No dedicated Bing documentation for Speakable exists. Bing’s general structured-data help doesn’t mention it — Speakable appears to be a Google-only, Google Assistant/Google Home mechanism. Treat any “Bing supports Speakable” claim as unverified.

Quotes from the source

On-the-record statements. Each Google-doc link is a deep link that jumps to the quoted passage on the live page (the core Speakable doc was fetched and verified directly this session).

Google — what Speakable is and does

• “The speakable property identifies sections within an article or webpage that are best suited for audio playback using text-to-speech (TTS).” — Google Search Central. Jump to quote
• “The Google Assistant uses speakable structured data to answer topical news queries on smart speaker devices.” Jump to quote

Google — still BETA, still narrow

• “This feature is in beta and subject to change. We’re currently developing this feature and you may see changes in requirements or guidelines.” Jump to quote
• “The speakable property works for users in the U.S. that have Google Home devices set to English, and publishers that publish content in English.” Jump to quote

Google — content guidelines

• “For optimal audio user experiences, we recommend around 20-30 seconds of content per section of speakable structured data, or roughly two to three sentences.” Jump to quote
• “Don’t add speakable structured data to content that may sound confusing in voice-only and voice-forward situations, like datelines (location where the story was reported), photo captions, or source attributions.” Jump to quote
• “Content indicated by speakable structured data must have concise headlines and/or summaries that provide users with comprehensible and useful information.” Jump to quote

Industry — Speakable does not feed AI Overviews

• “Speakable does not influence AI Overviews. Google does not use speakable selectors when deciding what to include in its AI-generated summaries.” — SEO Strategy Ltd (Sean Mullins), Sept 2025. Read the analysis

Industry — schema types “come and go”

• “Understand that markup types come and go, but a precious few you should hold on to (like title, and meta robots).” — John Mueller, Google, on the January 2026 structured-data removals. Coverage

Should I implement Speakable schema?

Walk it top to bottom:

1. Are you a news publisher (or news-style content)?

• No → Speakable was built to answer topical news queries. It isn’t aimed at you. Skip it — spend the effort on Organization/Person + sameAs entity markup instead. Done.
• Yes → continue.

2. Is your primary audience in the U.S., in English?

• No → the feature only works for US, English, Google Home users, and Google’s “we’ll expand soon” promise has sat unfulfilled since 2018. Skip it for now.
• Yes → continue.

3. Are you doing this to appear in AI Overviews / AI Mode?

• Yes → Stop. No Google-official source connects Speakable to AI-answer citation; the one analysis that checked says it doesn’t, and a 1,885-page schema study found no citation lift. You’re chasing a myth. Reconsider the goal.
• No (you want the Google Home news-readback surface) → continue.

4. Can you accept that the consumer is uncertain?

• The Google Assistant that reads Speakable aloud is being replaced by Gemini for Home in 2026, and nobody has confirmed Gemini for Home still reads Speakable.
  • If that uncertainty is a dealbreaker → wait for Google to clarify the Gemini-for-Home behavior before investing.
  • If the marginal cost is low and you’ll cover the surface anyway → implement it (see the Examples tab), pick one locator method, mark up ~20–30 seconds of self-contained summary, and avoid datelines/captions/attributions.

Shortcut: if at any point the honest answer is “a listicle told me to,” the answer is skip.

Speakable mistakes to avoid

The recurring errors, most of them born from 2026 SEO content getting it wrong:

• Adding it “for AI Overviews / AI Mode citations.” The single most common 2026 mistake. No Google source connects Speakable to AI-answer selection; the analysis that checked says it doesn’t, and the broad schema-vs-AI-citation data shows no lift. If this is your reason, you’re solving the wrong problem.
• Assuming it produces a visible rich result. It never did. Speakable’s only output was audio on Google Home — there is no star-rating-style SERP enhancement to “win.” Confusing it with Review/Breadcrumb/FAQ-style markup is a category error.
• Using it when you’re not US/English/news. The eligibility hasn’t budged since 2018. Implementing it for a non-US, non-English, or non-news site marks up content nothing will read.
• Marking up the whole article. Speakable is for the 2–3 sentences that stand on their own — not the body. Over-marking defeats the “read this specific bit aloud” design.
• Speaking datelines, captions, or attributions. Google explicitly says to avoid these — they sound confusing with no visual context (“Reuters, London —” read aloud helps no one).
• Using both cssSelector and xPath on the same markup. Pick one. Mixing the two locator methods is unsupported.
• Brittle absolute XPaths. An xPath tied to a deep, absolute DOM path breaks the moment your template changes. Prefer a stable cssSelector (a class you control).
• Treating “we hope to expand soon” as a roadmap. That line has been in the doc since 2018. Don’t build a plan around an expansion that’s been “coming” for seven years.
• Assuming Gemini for Home inherits it. Nobody has confirmed that. Don’t count on the readback surface still existing after the Assistant → Gemini transition.

Speakable JSON-LD examples

Two working shapes straight from Google’s structure. Use one locator method per markup block.

cssSelector — target elements by class

{
  "@context": "https://schema.org/",
  "@type": "WebPage",
  "name": "Quick Brown Fox",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".headline", ".summary"]
  },
  "url": "https://www.example.com/quick-brown-fox"
}

Here .headline and .summary are classes on the elements holding your concise, self-contained headline and summary. This is the more maintainable option for most sites — a class survives template changes better than an absolute path.

xPath — target elements by their XPath

{
  "@context": "https://schema.org/",
  "@type": "WebPage",
  "name": "Quick Brown Fox",
  "speakable": {
    "@type": "SpeakableSpecification",
    "xPath": [
      "/html/head/title",
      "/html/head/meta[@name='description']/@content"
    ]
  },
  "url": "https://www.example.com/quick-brown-fox"
}

This example pulls the page <title> and the meta description’s content — both already concise and self-contained, which is why they make good speakable targets.

A NewsArticle in context

Because NewsArticle inherits from Article, speakable attaches the same way — this is the realistic case, since news is what the feature was built for:

{
  "@context": "https://schema.org/",
  "@type": "NewsArticle",
  "headline": "City Council Approves New Transit Line",
  "datePublished": "2026-07-02T09:00:00-04:00",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".article-headline", ".article-dek"]
  }
}

Rules baked into these examples

• One locator method per block — cssSelector or xPath, not both.
• Target ~20–30 seconds / 2–3 sentences of self-contained summary.
• Don’t point at datelines, photo captions, or source attributions.
• Render the JSON-LD server-side so it’s in the raw HTML — the same general practice that applies to all structured data.

Speakable schema — cheat sheet

The essentials

Fast facts / myth-busts

• Not an AI-Overviews signal. No Google source connects Speakable to AI Overviews or AI Mode citation. The “it signals citable passages to AI” claim is unsourced.
• Not deprecated. It survived Google’s January 2026 structured-data cleanup and wasn’t mentioned at I/O 2026 — dormant, not dead.
• Not a rich result. It never produced a visible SERP enhancement.
• Not Bing-supported. No Bing documentation covers Speakable.
• Consumer is uncertain. The Google Assistant it feeds is being replaced by Gemini for Home in 2026; nobody has said whether Gemini for Home reads Speakable.

Do / Don’t

Resources worth your time

My related writing

• Structured Data: What It Is and How to Use It — my Ahrefs guide to schema types, implementation, validation, and the sameAs entity-markup work that actually helps machines understand you (the thing to do instead of Speakable if AI understanding is your goal).
• The Beginner’s Guide to Technical SEO — where structured data fits into the broader technical picture.

My speaking

• How Search Works (SlideShare) — my walkthrough of crawling, rendering, indexing, ranking, and where structured data sits. (My standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)

Official

• Speakable (BETA) Schema Markup — Google’s core doc: eligibility, cssSelector vs xPath, content guidelines, the beta label.
• schema.org — SpeakableSpecification — the underlying type and its usage stat.
• Google — AI Features and Your Website — “no special schema.org structured data” for AI features.

From around the industry

• Google releases speakable markup for news publishers interested in Google Assistant (Search Engine Land, 2018) — the launch coverage confirming it started US/English/Google-Home-only and BETA from day one.
• Analysis of Google’s New Schema Speakable Markup (Search Engine Journal, Roger Montti, 2018) — the original explainer, with Google’s 2018 launch statement.
• From Speakable Schema to AI Summary Control (SEO Strategy Ltd, Sean Mullins, Sept 2025) — the one industry piece that directly checks and refutes the “Speakable feeds AI Overviews” claim.
• We Tracked 1,885 Pages Adding Schema. AI Citations Barely Moved. (Ahrefs, Louise Linehan & Xibeijia Guan, 2026) — the data behind skepticism about “add schema for AI citations.”
• Google to remove more search features (Search Engine Land) — the January 2026 structured-data cleanup Speakable was not part of.
• Meet the new Google Home Speaker, built for Gemini (Google, June 2026) — the Assistant → Gemini-for-Home transition that never mentions Speakable.
• r/TechSEO — the community for structured-data debugging.

Test yourself: Speakable Schema

Five quick questions on what Speakable schema does — and doesn’t — do in 2026. Pick an answer for each, then check.

Speakable schema

Speakable schema is structured data (schema.org's SpeakableSpecification, added via the speakable property on Article or WebPage) that marks the specific 2–3 sentences on a page best suited to be read aloud by text-to-speech — not the whole article. In 2026 it remains a real but narrow, still-BETA Google feature limited to US, English, Google Home users, and Google has not connected it to AI Overviews despite widespread claims that it does.

Related: Structured Data, Schema Markup, Rich Results

Speakable schema

Speakable schema is structured data that flags the specific sections of a page — usually two to three sentences, roughly 20–30 seconds of audio — that are best suited to be read aloud by a text-to-speech (TTS) system. It is not a standalone schema type: it’s the speakable property, whose value is a SpeakableSpecification object, attached to an Article or WebPage.

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

You point at the speakable content with one of two locator methods — a cssSelector (class or CSS path) or an xPath — never both on the same markup. Google’s guidance is to mark up concise, self-contained headlines and summaries and to avoid text that sounds confusing out of visual context, such as datelines, photo captions, or source attributions.

The important thing to understand in 2026: Speakable has been in BETA since July 2018, and Google’s documentation — last updated December 2025 — still restricts it to users in the U.S. with Google Home devices set to English, for English-language publishers. It was built to feed the Google Assistant’s news readback on smart speakers. It is not deprecated (it survived Google’s January 2026 structured-data cleanup), but it is dormant and narrow, and — despite what a lot of 2026 SEO content claims — Google has not connected it to AI Overviews or AI Mode citation selection.

Related: Structured Data, Schema Markup, Rich Results

Changelog