How speakable schema works
Speakable is a property inside Article markup rather than a type of its own. You nominate the parts of the page that make sense spoken aloud — in practice the headline and a short opening summary — by giving either a CSS selector or an XPath that points at those elements. A voice assistant reading a bulletin then has the publisher’s own choice of what to say, instead of guessing from the top of the page.
The constraint that shapes everything else is that spoken text has no screen behind it. There is no subheading to glance at, no image, no way to skim back. So the sections you nominate have to make sense on their own: full sentences, names spelled out rather than abbreviated, no phrases like “as shown below” that only work when something is visible.
Why speakable schema matters
Honestly, for most sites it does not. Google documents speakable for news content and has kept it a limited feature rather than opening it to every publisher, so adding it to a service page or a product listing produces nothing. Anyone selling it as a general voice-search technique is selling you something Google has not offered.
Where it earns its place is on genuine news and editorial publishing, where an assistant may read a headline and summary aloud and the wording is the whole product. Even there, the value is less in the markup than in the discipline it forces: writing an opening that stands alone. That same opening is what tends to get pulled into a featured snippet or quoted by an AI answer, which are far larger prizes than the assistant read-out.
Where speakable schema goes wrong
The most common error is scope. Marking a whole article as speakable defeats the point, because nobody wants a long piece read at them from the top; the property exists to select a small, self-contained part. The second is fragility. A CSS selector points at the theme’s markup, and a redesign that renames a class breaks the reference silently — the structured data still validates, it just aims at nothing.
The third is expectation. Voice results are not a ranking surface you can enter by adding a tag, and speakable does not influence normal search results at all. If a proposal ties a voice search strategy to this one property, the strategy is thin.
What to do about it
If you are not publishing news, skip the markup and take the lesson instead: make the first sentence of every important page answer the question in the title, in plain words, without depending on anything around it. That helps a reader, an assistant and an AI summary equally, and it costs nothing to maintain.
If you are a news publisher, keep the nominated sections short, use selectors that belong to stable template elements rather than to styling classes, and recheck them after any theme change. Fold it into the rest of your structured data work so it is validated on the same schedule as everything else, not treated as a one-off experiment.