aeo
How to fix: Speakable schema for voice-engine extraction
Why this matters
Speakable schema (using cssSelector or xpath) tells voice engines exactly which page sections to read aloud. Without it, Google Assistant has to guess — and usually picks the first paragraph of body text, which may not be the most useful answer.
Background
Speakable schema (using cssSelector or xpath) tells voice engines exactly which page sections to read aloud. Without it, Google Assistant has to guess — and usually picks the first paragraph of body text, which may not be the most useful answer for the user's spoken query.
References
Schema.org Speakable · Google Search Central · Speakable specification
How to fix
Code snippet for each stack we cover. Pick the one matching your server / framework.
nginx
No server config — page-template change.
apache
Same — page-template change.
cloudflare
No edge config. Add JSON-LD via your CMS.
wordpress
Add custom JSON-LD via the Schema App plugin OR a child-theme functions.php — Yoast/RankMath don't emit Speakable by default.
flask
Add 'speakable':{'@type':'SpeakableSpecification','cssSelector':['.summary','.tldr']} to your Article schema block.
express
Same.
rails
Same — extend the existing Article schema helper.
Verify it's working
Validator.schema.org should report a SpeakableSpecification with valid selectors.
Want to know if your site has this issue?
Run a free 53-check audit — security, GDPR, NIS2, and technical SEO.
Audit my site →