Skip to content

Podcast/news/article page without Speakable schema

Speakable schema is structured data that marks specific parts of a page, usually a headline and summary, as suitable for a voice assistant to read aloud. This check found a podcast, news or article-type page on this site without that markup, meaning nothing on the page tells voice systems which text is the safe, readable summary to use. Without Speakable schema, this content is invisible to Google Assistant's text-to-speech feature and to the wider voice-AI tools, such as ElevenLabs Reader and Pocket Casts AI, that read from the same markup. That's a free audio distribution channel going entirely unused, on top of whatever existing readers or listeners the content already has. Your developer should add a SpeakableSpecification block inside the page's existing WebPage structured data, pointing a cssSelector, a reference to specific elements on the page, at the headline and summary. This takes about 30 minutes per page template, so it only needs doing once per content type, not once per individual article.

Why this matters

Without Speakable schema, this content is invisible to Google Assistant's text-to-speech feature and to the wider voice-AI tools, such as ElevenLabs Reader and Pocket Casts AI, that read from the same markup. That's a free audio distribution channel going entirely unused, on top of whatever existing readers or listeners the content already has.

How to fix it

Your developer should add a SpeakableSpecification block inside the page's existing WebPage structured data, pointing a cssSelector, a reference to specific elements on the page, at the headline and summary. This takes about 30 minutes per page template, so it only needs doing once per content type, not once per individual article.