SpeakableSpecification is one of those schema types everyone agrees matters for voice search and AI citation, and almost nobody ships. The reason is boring: writing the CSS selectors by hand is tedious, the Google spec is narrow, and the verification flow (Rich Results Test) is clunky enough to make you close the tab.
The Speakable Schema Generator shortcuts all of that. Paste a URL. It reads your rendered HTML, finds every H1/H2/H3 and the first paragraph that follows each heading, and suggests which combinations would make sensible Speakable targets. You check the ones you want, click generate, paste the block into your <head>.
What "answer-shaped" means
The tool pre-selects candidates based on two heuristics. First, your H1. That's almost always worth marking. Second, any H2 or H3 followed by a paragraph between 60 and 320 characters. That range is the sweet spot: long enough to answer a question, short enough that Google Assistant can actually read it aloud.
Everything else stays visible but unchecked. You can include or exclude any candidate manually.
What the output looks like
A WebPage envelope with a speakable array of cssSelector strings. Each selector points at one heading or paragraph on the page. The tool prefers #id selectors when available, class selectors when not, and sibling-combinator fallbacks when it has to.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Why Local SEO Still Wins in 2026",
"url": "https://example.com/local-seo/",
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": ["#what-is-local-seo", "#what-is-local-seo + p", "#gbp-optimization"]
}
}
</script>
Where it fits
Speakable is one of the more reliable AI-citation levers, alongside FAQPage and direct-answer paragraphs. The AI Citation Readiness tool scores whether your content has Speakable at all. This tool builds the block for you.
The methodology behind when to use it. Which pages are worth marking, which aren't. Is in Chapter 16 of The $100 Network, LLM-Optimized Content. Short answer: mark your pillar pages and your top ten articles by traffic. Don't bother with landing pages; voice assistants won't read a sales page.