Pro Feature
Script the voice answer, don’t leave it to chance
Google Assistant answers 2 billion voice queries a month. Speakable markup tells Google exactly which sentences you want read aloud, so when Google reads your page, it knows which words you chose.
Your content isn’t one of those 2 billion answers
When someone asks “Hey Google, what’s happening with inflation?” or “What are the latest AI regulations?”, Google needs to pick a source. It needs to find a section of a page that sounds natural when read aloud. Without speakable markup, Google makes its own guess about what to read. With it, you tell Google exactly which sentences to use.
That’s the difference between being the source and being invisible to voice search.
Who this is for, and who can skip it
Speakable helps news publishers get voice answers on smart speakers. The setup activates the markup automatically for news sites. You need this if:
- You’re a news publisher enrolled in Google News.
- Your audience is US-based and English-speaking. That’s the current scope of Google’s programme.
- You publish timely, factual content. News, analysis, market updates.
- You want the voice answer slot on Google Home and smart speakers.
You can skip it if you run a blog, e-commerce store or SaaS site, your site isn’t enrolled in Google News, your audience is outside the US, or your content isn’t time-sensitive.
What you’re missing without it
Right now, if a voice assistant pulls from your article, it picks whatever text it finds first. That might be your byline. Your cookie notice. A photo caption. The wrong paragraph entirely.
Speakable markup solves this. You mark exactly which sections should be read aloud, and eligible voice assistants use that markup. Your headline. Your opening summary. The key fact. You choose.
Without speakable, you’re leaving the voice answer to chance. With it, you’re scripting it.
The work a developer would hand-code on every page
- Automatic schema markup. Every page on your site gets a valid SpeakableSpecification injected into the head. No code, no per-page configuration. Toggle it on and it works across your entire site.
- CSS selector control. You pick which HTML elements are speakable. Default: your H2 headings and first paragraph. Want your summary box instead? Change the selector in Schema Engine and it applies everywhere instantly.
- AI summary generation (Pro). Sometimes your existing content isn’t written for voice. The AI reads your article and generates a 2-3 sentence summary that sounds natural when spoken aloud. One click, saved to your post, ready for schema output.
- Smart gap scanner. The content gap scanner only flags speakable issues when it makes sense: speakable is enabled, the post is 500+ words, and it’s actually a content post, not a landing page or product. If speakable is off, the scanner ignores it completely.
The output Google actually sees
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Fed Holds Interest Rates Steady at 5.5%",
"url": "https://example.com/fed-rate-decision-march-2026",
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": [
".entry-content h2",
".entry-content p:first-of-type"
]
}
}This tells Google: “Read the H2 and the first paragraph if a voice assistant needs to answer a question about this page.” The plugin generates this on every page load. You never touch the code.
Google’s requirements vs what we handle
| What Google Requires | What AEO God Mode Does |
|---|---|
| Article or WebPage schema type | Auto-outputs WebPage with SpeakableSpecification |
| CSS selectors pointing to speakable content | Configurable editor with smart defaults |
| Concise sections (20-30 seconds of audio) | Default selectors target naturally short elements |
| No captions, datelines, or attribution text | Selectors target content only, not metadata |
| Conversational, TTS-friendly language | AI summary generator writes for spoken delivery |
| Valid structured data | Schema tested against Google Rich Results spec |
The honest truth about speakable in 2026
Google’s speakable feature is still in beta. It works for US-based English news publishers enrolled in Google News, on Google Home devices and Google Assistant. That’s the current scope.
For non-news sites, the markup is valid schema that won’t cause errors or penalties. But Google won’t activate voice features for your site until they expand the beta. That’s why AEO God Mode defaults it to off and labels it clearly as a beta feature.
If you’re a news publisher, this is an open lane. Most of your competitors haven’t implemented speakable markup. That means the voice answer slot is up for grabs on every query your site covers. Same effort as everyone else, but you’re the one Google reads aloud.
If you’re not a news publisher, focus on FAQ schema, strong headings, llms.txt and direct answer structures. Those move the needle for AI visibility right now. When Google opens speakable to all sites, AEO God Mode will be ready. One toggle.
Speakable Schema questions
No. Google’s speakable feature currently works for US-based English news publishers enrolled in Google News. If that’s not you, focus on FAQ schema, strong headings and direct answer structures instead. The markup is harmless to keep, but it won’t activate voice features until Google expands the beta.
Yes. As of 2026 Google’s speakable feature is in beta, limited to US-based English news publishers in Google News, on Google Home devices and Google Assistant. AEO God Mode defaults it to off and labels it clearly as a beta feature.
Whichever elements your CSS selectors point at. The default targets your H2 headings and first paragraph, which are naturally short and read well aloud. You can change the selectors in Schema Engine, for example to a summary box, and the change applies across your whole site instantly.
Sometimes existing content isn’t written for voice. The AI reads your article and generates a 2-3 sentence summary that sounds natural when spoken aloud. One click, saved to your post, ready for schema output. It’s a Pro feature.
No. The plugin outputs valid WebPage schema with a SpeakableSpecification, tested against the Google Rich Results spec. It won’t cause errors or penalties. Google simply won’t activate voice features for your site until the beta expands beyond news publishers.
Be the answer Google reads aloud
Turn on Speakable Schema and script the voice answer instead of leaving it to chance.