I added three lines of schema markup to 52 websites last month. Within two weeks, I started seeing those exact sentences show up in AI-generated answers. Not paraphrased. Quoted.
The markup is called SpeakableSpecification, and it is one of the most underused schema types in existence. While everyone obsesses over FAQ schema and HowTo markup, SpeakableSpecification quietly tells machines: "This is the part worth reading out loud."
And in 2026, "reading out loud" does not just mean voice assistants. It means AI citations.
What Is SpeakableSpecification?
SpeakableSpecification is a Schema.org property that identifies sections of a web page that are especially suitable for text-to-speech and audio playback. Google introduced support for it as part of their news and voice search initiatives, but its value has expanded dramatically as AI systems have started consuming web content.
When you add SpeakableSpecification to your page, you are using CSS selectors to point at specific elements and saying: "These paragraphs contain the most concise, quotable, authoritative statements on this page."
Voice assistants like Google Assistant use this to decide what to read aloud. AI systems like Google's AI Overviews, ChatGPT, and Perplexity use similar signals to decide what to cite. You are curating your own pull quotes for machines.
Why It Matters for AI Citations
AI-generated search results have a citation problem. When an AI system summarizes information from multiple sources, it has to decide which source to quote and which specific text to extract. Without guidance, the AI guesses. It might pull a sentence from your third paragraph, or it might skip your page entirely because nothing stood out as a clean, quotable statement.
SpeakableSpecification solves this by giving the AI a shortlist. You are saying: if you are going to cite this page, cite these specific sentences.
In our testing across the 52-site network, pages with SpeakableSpecification markup showed higher rates of verbatim citation in AI Overviews compared to pages without the markup covering similar topics. The AI is not required to use your speakable sections, but it has a clear preference for content that has been explicitly flagged as quotable.
How to Implement SpeakableSpecification
The implementation uses JSON-LD structured data in your page's <head>. Here is a complete example:
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Why Every Website Needs an AI Agent Card",
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": [
".article-summary",
".key-takeaway",
"h2",
".speakable"
]
},
"url": "https://yoursite.com/blog/ai-agent-cards/"
}
The cssSelector array points to the HTML elements that contain your most quotable content. Here is what works best:
Option 1: Use a dedicated class. Add a speakable class to 2-4 paragraphs that contain your strongest, most concise statements. This gives you surgical control.
<p class="speakable">An AI agent card is a JSON file at /.well-known/agent-card.json that gives autonomous AI systems a structured description of your site, services, and interaction preferences.</p>
Option 2: Use existing semantic elements. Point at your h2 headings and first paragraph to let the AI grab your structure and introduction.
Option 3: Use a summary block. Create an .article-summary div at the top of each post with 2-3 sentences that summarize the entire piece. This is your "designed to be quoted" block.
Best Practices for Speakable Content
The content you mark as speakable should follow specific guidelines to maximize citation quality:
Keep sentences under 25 words. Long, complex sentences get truncated or paraphrased by AI. Short, declarative sentences get quoted verbatim.
Lead with the fact, not the opinion. "Server-side analytics capture 40% more visitors than client-side scripts" is more citable than "I believe server-side analytics are better." Data gets quoted. Opinions get skipped.
Include one number per speakable block. AI systems love citing statistics. A speakable sentence with a specific data point. A percentage, a dollar amount, a timeframe. Gets cited at a significantly higher rate than one without.
Avoid jargon in speakable sections. These sections need to be understandable when read in isolation, without the surrounding context. Write them as if they will be the only sentence someone hears.
Implementation Across a Multi-Site Network
When we deployed SpeakableSpecification across 52 sites, we used a template-level approach. Rather than adding markup to every individual post, we added the JSON-LD block to our base post template with dynamic CSS selectors:
- Every blog post template automatically includes SpeakableSpecification pointing at
h2elements and the first paragraph - Authors can add the
.speakableclass to any additional paragraphs they want flagged - The
urlandnamefields are populated dynamically from each page's metadata
This means every new post published across any of the 52 sites automatically gets SpeakableSpecification without any manual markup. The author just writes, and the template handles the schema.
SpeakableSpecification vs. Other Schema Types
FAQ Schema tells Google "here are questions and answers" and can generate rich results. SpeakableSpecification tells machines "here is the text worth quoting." They serve different purposes and can coexist on the same page.
HowTo Schema structures step-by-step instructions. SpeakableSpecification flags the most important sentences. Again, complementary.
Article Schema describes the article's metadata (author, date, headline). SpeakableSpecification goes deeper by identifying specific content within the article that should be prioritized for quotation.
The combination of all four. Article + FAQ + HowTo + Speakable. Gives AI systems a complete understanding of your page: what it is, what it answers, how to follow its instructions, and what to quote.
Add This to Your Next Site Audit
SpeakableSpecification takes 10 minutes to add to a page template and zero ongoing effort after that. The checklist:
- Add JSON-LD SpeakableSpecification to your blog post template
- Define CSS selectors that target your most quotable content
- Review your top 10 posts and add the
.speakableclass to 2-3 key sentences each - Validate with Google's Rich Results Test
- Monitor AI citation patterns over the next 30 days
Voice search is growing. AI citations are growing faster. The sites that tell machines what to quote will get quoted. The sites that leave it to chance will get paraphrased. Or ignored.
This strategy is covered in more depth in The $20 Dollar Agency. Including the full schema markup stack for small business websites and how to implement it without hiring a developer. Buy The $20 Dollar Agency on Amazon.
Related reading
The methodology behind this piece is covered in depth in:
- The $20 Dollar Agency, Single-site audit + schema + E-E-A-T playbook, the agency-for-one methodology.
- The $100 Network, Monoclone architecture, IndexNow, and multi-site scaling, how to run a network of sites.
