Guide : Speakable Schema

TL;DR — Speakable schema is a bit of code que points at the spécifique sentences on une page — pas the whole article — que a machine devrait lire aloud, comme a smart speaker answering a news question. In 2026 it’s encore a petit, test-only Google fonctionnalité: it seulement fonctionne pour personnes in the U.S. with Google Home devices définir to English. And despite ce que a lot of SEO articles claim, it fait pas aider vous montrer up in Google’s AI Overviews.

Ce que Speakable schema is

La plupart données structurées étiquettes ce que a chose is — “this is the price,” “ce is the author.” Speakable fait something différent: it points at the parts of une page que are meilleur to lire out loud. Imagine asking a smart speaker pour the news — it can’t lire a whole article to vous, so Speakable schema indique it qui two or three sentences to speak.

Vous ajouter it as a petit piece of code (usually JSON-LD) que noms the sentences by leur emplacement on lune page — soit by a CSS class or by an XPath. Vous pick un of ceux two méthodes, pas les deux. Google recommends marking up à propos de 20–30 seconds of audio, or roughly two to three sentences — a concise headline and summary que faire sense on leur propre.

Who peut en réalité utiliser it

Ce is the partie la plupart articles skip. Speakable has been a beta fonctionnalité since 2018, and Google’s propre page — mis à jour as recently as December 2025 — encore dit it seulement fonctionne pour:

• utilisateurs in the United States,
• on Google Home devices,
• définir to English, and
• pour publishers who publish in English.

It’s pas simplement an inferred pattern, soit — Google’s propre setup instructions dire it outright: “Pour votre news content to be eligible as réponses to topical news requêtes, follow ces steps.” News content is a stated requirement, pas a convention. Si you’re pas a US, English-language news site, it was jamais really aimed at vous.

The chose la plupart personnes obtenir incorrect

You’ll voir 2026 SEO articles claim Speakable now helps vous obtenir cited in Google’s AI Overviews or AI Mode. There’s aucun evidence pour que — Google has jamais said it, and it isn’t listed anywhere in Google’s AI documentation. Speakable was construit pour un chose: reading news aloud on Google Home speakers. Ajout it ne va pas obtenir votre page picked as an AI réponse.

It’s aussi pas deprecated — lune page is live and encore maintained. It’s simplement narrow and quiet. Vouloir the complet picture, notamment the JSON-LD, pourquoi the whole feature’s future is genuinely uncertain, and si it’s worth votre temps? Switch to the Avancé tab.

TL;DR — Speakable is the speakable property (valeur: a SpeakableSpecification object) on Article/WebPage — pas a standalone type. It marks the 2–3 sentences (~20–30s) meilleur lire aloud by TTS, located by un of cssSelector or xPath. It’s been explicitly BETA since July 2018 and, per the doc mis à jour December 2025, is encore limited to US, English, Google Home utilisateurs. It survived Google’s January 2026 structured-data cleanup and wasn’t mentioned at I/O 2026 — so it’s dormant, pas deprecated. Two accuracy spines: (1) aucun 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 pour Home, and nobody has said si Gemini pour Home encore consumes Speakable. Treat it as a US-news-publisher relic, pas an AI-search lever.

Ce que Speakable en réalité is

Google’s framing is precise: “The speakable property identifies sections dans an article or webpage que are meilleur suited pour audio playback en utilisant text-to-speech (TTS).” (Recherche Google Central) The important structural point: it n’est pas its propre schema type. It’s the speakable property, whose valeur is a SpeakableSpecification object, and vous attach it to an Article or a WebPage (a NewsArticle fonctionne aussi, by schema.org inheritance from Article).

And vous don’t mark up the whole page. Vous point at the 2–3 sentences — the headline and a concise summary — que stand on leur propre quand lire out of visual context to a listener. Que “sections, not the whole article” distinction is the entier design intent.

Locating the speakable content: cssSelector vs xPath

Vous pick exactly un of two locator méthodes — jamais les deux on the même markup:

• cssSelector — “Addresses content in the annotated pages (tel as class attribute).” Vous target elements by class or CSS chemin (e.g. .headline, .summary).
• xPath — “Addresses content en utilisant xPaths (assuming an XML view of the content).” Vous target elements by leur XPath (e.g. /html/head/title).

cssSelector is the plus maintainable choice pour la plupart sites parce que it survives markup reshuffles meilleur que a brittle absolute XPath — but les deux are valid.

Un spelling gotcha worth knowing avant vous copy an exemple from the incorrect placer: schema.org’s propre vocabulary page spells the underlying property lowercase, xpath, pendant que Google’s Speakable doc and every JSON-LD exemple on it utiliser camelCase, xPath. Since it’s Google Assistant consuming ce markup, follow Google’s xPath casing in votre JSON-LD — the schema.org page defines the broader vocabulary, pas the property nom Google’s parser expects.

Content guidelines que encore hold up

Même outside Speakable’s propre eligibility, its content rules are bon TTS advice:

• Length. Google: “Pour optimal audio utilisateur experiences, we recommend autour 20-30 seconds of content per section of speakable données structurées, or roughly two to three sentences.” (Recherche Google Central)
• Éviter context-dependent text. Google: “Don’t ajouter speakable données structurées to content que may sound confusing in voice-only and voice-forward situations, comme datelines (emplacement où the story was reported), photo captions, or source attributions.” (Recherche Google Central)
• Écrire concise, self-contained summaries. Google: “Content indicated by speakable données structurées doit have concise headlines and/or summaries que provide utilisateurs with comprehensible and utile information.” (Recherche Google Central)

Who peut en réalité utiliser it — encore narrow in 2026

Here’s où honesty matters. The fonctionnalité is encore explicitly BETA — Google: “This feature is in beta and subject to change.” (Recherche Google Central) That’s pas a stale doc I’m quoting: lune page footer reads “Dernier mis à jour 2025-12-10 UTC,” so Google is encore touching it — it simplement hasn’t modifié the scope.

And the scope is exactly ce que it was at the 2018 launch. Google: “The speakable property fonctionne pour utilisateurs in the U.S. que have Google Home devices définir to English, and publishers que publish content in English.” (Recherche Google Central) Google adds it hopes to launch in autre countries and languages “as soon as sufficient number of publishers have implemented speakable” — a promise premier made in 2018 que, as of the December 2025 doc, is encore unfulfilled seven-plus années plus tard. Quand I voir a “we hope to expand soon” line que has sat unchanged pour seven années, I lire it as a promise que quietly expired, pas a roadmap.

Que US/English/Google Home line is seulement half the eligibility bar. The doc’s propre “Getting started” section states the autre half directement: “Pour votre news content to be eligible as réponses to topical news requêtes, follow ces steps.” (Recherche Google Central) News content isn’t a genre I’m inferring from context — it’s the explicit subject of the section que indique vous how to become eligible.

Ce que it feeds is equally spécifique: “The Google Assistant uses speakable données structurées to réponse topical news requêtes on smart speaker devices.” (Recherche Google Central) Remarque ce que que is pas: it jamais produced a visible SERP rich result the façon Examiner stars or Breadcrumbs did. Its entier output surface was audio on a Google Home device.

Is it dead? Aucun — but lire the signals carefully

Three checkable facts, none of qui dire “deprecated”:

• It survived the January 2026 cleanup. Google’s late-2025/early-2026 structured-data pruning supprimé prise en charge pour a batch of rich-result types (Moteur de recherche Land coverage). Speakable was pas on que liste — neither killed nor reaffirmed. Simplement untouched.
• It wasn’t mentioned at I/O 2026. I went via Google’s I/O 2026 Search recap and the roundups — aucun Speakable mention in quelconque Search announcement. Consistent with a fonctionnalité Google maintains but ne … plus promotes.
• Adoption is réel 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 suivant to Article- or Organization-scale types.

None of ceux three facts is a Google statement à propos de Speakable’s lifecycle — Google hasn’t appelé it dormant, active, or anything sinon. “Dormant and narrow” is my lire of the pattern ceux facts formulaire, pas something Google has confirmed soit façon. So: dormant and narrow is my inference from que pattern; deprecated is pas — Google hasn’t said soit. John Mueller’s framing during the January 2026 removals discussion is the correct lens pour tout schema of ce kind — “Comprendre que markup types come and go, but a precious few vous devez hold on to (comme title, and meta robots).” (Moteur de recherche Roundtable) Speakable is squarely in the “come and go” bucket, pas the “hold on to” un. Mueller’s Reddit remark is relayed via Moteur de recherche Roundtable; the original page blocked direct verification ce session, so treat it as secondary-sourced.

The elephant in the room: Assistant → Gemini pour Home

Here’s the genuinely current, under-covered partie. Speakable’s entier consumer is the Google Assistant reading news on Google Home. And throughout 2026 Google is replacing the Google Assistant with Gemini pour Home — the premier purpose-built device, the Google Home Speaker, shipped in June 2026, and Gemini pour Home is expanding to plus third-party speakers ce année.

Now connecter the dots: aucun source — pas Google’s Speakable doc, pas the Gemini pour Home launch material, pas quelconque SEO commentary I pourrait trouver — dit si Gemini pour Home encore consumes Speakable markup the façon the Assistant did. The doc talks à propos de “the Google Assistant”; the Assistant is being sunset; and the two pages jamais mention chaque autre. That’s pas me predicting doom — it’s an ouvrir, unresolved status question que I’d treat as the unique biggest raison to be cautious ici. Frame it as an ouvrir question, pas a fact in soit direction.

Fait Speakable aider with AI Overviews or AI Mode? Pas a documented lever.

Ce is the autre accuracy spine, and it’s où a lot of 2026 content is simply incorrect. A wave of “GEO”/AI-search posts assert que Speakable now signals “citation-worthy passages” to AI Overviews or AI Mode. Aucun Google-official source supports que. Google’s propre AI-features doc is direct à propos de the general point: “There’s also no special schema.org structured data that you need to add” to apparaître in AI Overviews or AI Mode. (Recherche Google Central) That’s Google ruling out a “special markup” requirement in general — it isn’t a Speakable-specific statement, so I’m careful pas to stretch it into “Google dit Speakable has zero effect.” The un industry analysis que vérifié the Speakable-specific claim (SEO Strategy Ltd, Sept 2025) states it plainly: “Speakable ne fait pas influence AI Overviews. Google ne fait pas utiliser speakable selectors quand deciding ce que to inclure in its AI-generated summaries.” Absence of documentation isn’t proof of zero effect — but there’s aussi aucun evidence of a positive un, and the honest étiquette is “not a documented lever or requirement,” pas a hedge-free “it does nothing.” SEO Strategy Ltd is industry analysis, pas a Google statement — but it’s the un source que directement testé the claim plutôt que repeating it.

The broader evidence points the même façon. Ahrefs tracked 1 885 pages ajout schema (JSON-LD ajouté Aug 2025–Mar 2026, mesuré contre AI Overviews, AI Mode, and ChatGPT citations) and trouvé aucun meaningful citation uplift from ajout schema broadly. Que study isn’t Speakable-specific, but it’s directement relevant to the “add Speakable and get cited by AI” pitch: the general lever ceux posts assume doesn’t montrer up in the données. Si you’ve lire the structured-data hub, ce is the même story as every autre “schema for AI citations” claim — schema is entity infrastructure, pas a citation cheat code.

Devrait vous implement it in 2026?

• Maybe worth it: you’re a US, English-language news publisher déjà invested in Google Home audio, the marginal cost is low, and vous vouloir to cover the un narrow surface it feeds. Même alors, weigh the Gemini-for-Home uncertainty.
• Very probable wasted effort: you’re outside US/English, you’re pas a news publisher, or — la plupart commonly — you’re ajout it parce que a listicle told vous it helps AI search. It doesn’t. Spend que effort on Organization/Person entity markup with correct sameAs valeurs à la place, qui is the schema que en réalité helps machines resolve who vous are.

Où ce sits

Speakable belongs to the même practitioner grouping as page-level metadata-trust markup — a type whose un flagship utiliser cas (ici, Google Home news readback) went quiet pendant que the underlying schema.org type itself was jamais deprecated. It’s a sibling deep-dive off the Données structurées pour le SEO hub, alongside balisage de données structurées, JSON-LD, and résultats enrichis. Comme the WebSite/sitelinks- searchbox pattern, it’s a utile cas study in reading a schema type honestly: pas dead, but pas the chose the hype dit it is.

AI summary

A condensed prendre on the Avancé version:

• Ce que c’est. Speakable is the speakable property (valeur: a SpeakableSpecification object) on Article/WebPage — pas a standalone type. It marks the 2–3 sentences (~20–30s) meilleur lire aloud by text-to-speech, pas the whole article.
• How vous point at content. Exactly un locator: cssSelector or xPath, jamais les deux. Google recommends concise, self-contained headlines/summaries and dit to éviter datelines, captions, and source attributions.
• Who peut utiliser it — encore narrow. Explicitly BETA since July 2018; per the doc mis à jour Dec 2025, limited to US, English, Google Home utilisateurs, English publishers, and — stated directement in Google’s propre setup steps — news content. It jamais produced a visible SERP rich result — its seulement output was audio on Google Home.
• Pas dead, simplement dormant (my lire of the pattern, pas 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) — réel but tiny.
• Accuracy spine #1 — pas a documented AI-Overviews lever. Aucun Google source ties Speakable to AI Overviews / AI Mode citation, and Google’s AI-features doc dit outright there’s “no special schema.org structured data” nécessaire pour ceux fonctionnalités. SEO Strategy Ltd states Google doesn’t utiliser speakable selectors pour AI summaries; an Ahrefs 1 885-page study trouvé aucun citation lift from ajout schema broadly. Absence of evidence isn’t proof of zero effect, but the “Speakable feeds AI citations” claim has aucun documented prise en charge.
• Accuracy spine #2 — the Assistant is being replaced. Google is swapping the Google Assistant (Speakable’s seulement consumer) pour Gemini pour Home in 2026 (Google Home Speaker shipped June 2026). Aucun source dit si Gemini pour Home encore reads Speakable — treat it as an ouvrir question.
• Devrait vous bother? Maybe, si you’re a US/English news publisher on Google Home. Sinon it’s very probable wasted effort — surtout si you’re ajout it “pour AI search.” Do Organization/Person + sameAs entity markup à la place.

Documentation officielle

Primary-source documentation and the underlying vocabulary.

Google

• Speakable (BETA) Balisage de données structurées — the core doc: definition, the US/English/Google Home eligibility, the cssSelector vs xPath méthodes, content guidelines, and the “in beta and subject to change” étiquette (dernier mis à jour 2025-12-10 UTC).
• Intro to How Données structurées Markup Fonctionne — où Speakable sits among the formats and the broader rich-result picture.
• AI Fonctionnalités and Votre Website — Google’s statement que there’s “no special schema.org structured data that you need to add” pour AI fonctionnalités (context pour the AI-Overviews myth-bust).
• Google Home Speaker, construit pour Gemini — the Gemini-for-Home launch que jamais 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 utilisé on Article and WebPage.

Bing / Microsoft

• Aucun dedicated Bing documentation pour Speakable exists. Bing’s general structured-data aider doesn’t mention it — Speakable apparaît to be a Google-only, Google Assistant/Google Home mechanism. Treat quelconque “Bing supports Speakable” claim as unverified.

Quotes from the source

On-the-record statements. Chaque Google-doc lien is a deep lien que jumps to the quoted passage on the live page (the core Speakable doc was récupéré and verified directement ce session).

Google — ce que Speakable is and fait

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

Google — encore BETA, encore 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 ne fait pas 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. Lire 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

Devrait I implement Speakable schema?

Walk it top to bottom:

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

• Aucun → Speakable was construit to réponse topical news requêtes. It isn’t aimed at vous. Skip it — spend the effort on Organization/Person + sameAs entity markup à la place. Fait.
• Yes → continuer.

2. Is votre principal audience in the U.S., in English?

• Aucun → the fonctionnalité seulement fonctionne pour US, English, Google Home utilisateurs, and Google’s “we’ll expand soon” promise has sat unfulfilled since 2018. Skip it pour now.
• Yes → continuer.

3. Are vous doing ce to apparaître in AI Overviews / AI Mode?

• Yes → Arrêter. Aucun Google-official source connects Speakable to AI-answer citation; the un analysis que vérifié dit it doesn’t, and a 1 885-page schema study trouvé aucun citation lift. You’re chasing a myth. Reconsider the goal.
• Aucun (vous vouloir the Google Home news-readback surface) → continuer.

4. Peut vous accept que the consumer is uncertain?

• The Google Assistant que reads Speakable aloud is being replaced by Gemini pour Home in 2026, and nobody has confirmed Gemini pour Home encore reads Speakable.
  • Si que uncertainty is a dealbreaker → wait pour Google to clarify the Gemini-for-Home behavior avant investing.
  • Si the marginal cost is low and you’ll cover the surface anyway → implement it (voir the Exemples tab), pick un locator méthode, mark up ~20–30 seconds of self-contained summary, and éviter datelines/captions/attributions.

Shortcut: si at quelconque point the honest réponse is “a listicle told me to,” the réponse is skip.

Speakable mistakes to éviter

The recurring errors, la plupart of les born from 2026 SEO content getting it incorrect:

• Ajout it “for AI Overviews / AI Mode citations.” The unique la plupart courant 2026 mistake. Aucun Google source connects Speakable to AI-answer selection; the analysis que vérifié dit it doesn’t, and the broad schema-vs-AI-citation données montre aucun lift. Si ce is votre raison, you’re solving the incorrect problem.
• Assuming it produces a visible rich result. It jamais did. Speakable’s seulement output was audio on Google Home — là is aucun star-rating-style SERP enhancement to “win.” Confusing it with Examiner/Breadcrumb/FAQ-style markup is a category error.
• En utilisant it quand you’re pas US/English/news. The eligibility hasn’t budged since 2018. Implementing it pour a non-US, non-English, or non-news site marks up content nothing va lire.
• Marking up the whole article. Speakable is pour the 2–3 sentences que stand on leur propre — pas the corps. Over-marking defeats the “lire ce spécifique bit aloud” design.
• Speaking datelines, captions, or attributions. Google explicitly dit to éviter ces — ils sound confusing with aucun visual context (“Reuters, London —” lire aloud helps aucun un).
• En utilisant les deux cssSelector and xPath on the même markup. Pick un. Mixing the two locator méthodes is unsupported.
• Brittle absolute XPaths. An xPath tied to a deep, absolute DOM chemin breaks the moment votre template changements. Préférer a stable cssSelector (a class vous contrôler).
• Treating “we hope to expand soon” as a roadmap. Que line has been in the doc since 2018. Don’t construire a plan autour an expansion that’s been “coming” pour seven années.
• Assuming Gemini pour Home inherits it. Nobody has confirmed que. Don’t count on the readback surface encore existing après the Assistant → Gemini transition.

Speakable JSON-LD exemples

Two working shapes straight from Google’s structure. Utiliser un locator méthode 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"
}

Ici .headline and .summary are classes on the elements holding votre concise, self-contained headline and summary. Ce is the plus maintainable option pour la plupart sites — a class survives template changements meilleur que an absolute chemin.

xPath — target elements by leur 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"
}

Ce exemple pulls lune page <title> and the meta description’s content — les deux déjà concise and self-contained, qui is pourquoi ils faire bon speakable targets.

A NewsArticle in context

Parce que NewsArticle inherits from Article, speakable attaches the même façon — ce is the realistic cas, since news is ce que the fonctionnalité was construit pour:

{
  "@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 ces exemples

• Un locator méthode per block — cssSelector or xPath, pas les deux.
• 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 même general pratique que s’applique to tout données structurées.

Speakable schema — cheat sheet

The essentials

Fast facts / myth-busts

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

Do / Don’t

Ressources utiles

My connexe writing

• Données structurées: Ce que c’est and Comment utiliser It — my Ahrefs guide to schema types, implementation, validation, and the sameAs entity-markup fonctionner que en réalité helps machines comprendre vous (the chose to do à la place of Speakable si AI understanding is votre goal).
• The Beginner’s Guide to SEO technique — où données structurées fits into the broader technical picture.

My speaking

• How Search Fonctionne (SlideShare) — my walkthrough of exploration, rendering, indexation, ranking, and où données structurées sits. (My standing disclaimer s’applique: “This is my understanding of systems… not going to be 100% complete or accurate.”)

Official

• Speakable (BETA) Balisage de données structurées — Google’s core doc: eligibility, cssSelector vs xPath, content guidelines, the beta étiquette.
• schema.org — SpeakableSpecification — the underlying type and its usage stat.
• Google — AI Fonctionnalités and Votre Website — “no special schema.org structured data” pour AI fonctionnalités.

From autour the industry

• Google releases speakable markup pour news publishers interested in Google Assistant (Moteur de recherche Land, 2018) — the launch coverage confirming it commencé US/English/Google-Home-only and BETA from day un.
• Analysis of Google’s Nouveau Schema Speakable Markup (Moteur de recherche Journal, Roger Montti, 2018) — the original explainer, with Google’s 2018 launch statement.
• From Speakable Schema to AI Summary Contrôler (SEO Strategy Ltd, Sean Mullins, Sept 2025) — the un industry piece que directement checks and refutes the “Speakable feeds AI Overviews” claim.
• We Tracked 1 885 Pages Ajout Schema. AI Citations Barely Déplacé. (Ahrefs, Louise Linehan & Xibeijia Guan, 2026) — the données behind skepticism à propos de “add schema for AI citations.”
• Google to supprimer plus search fonctionnalités (Moteur de recherche Land) — the January 2026 structured-data cleanup Speakable was pas partie of.
• Meet the nouveau Google Home Speaker, construit pour Gemini (Google, June 2026) — the Assistant → Gemini-for-Home transition que jamais mentions Speakable.
• r/TechSEO — the community pour structured-data debugging.

Testez vos connaissances: Speakable Schema

Five rapide questions on ce que Speakable schema fait — and doesn’t — do in 2026. Pick an réponse pour chaque, alors vérifier.

Journal des modifications