What Speakable schema is and what it signals

Speakable schema identifies parts of a page suited to text-to-speech. Google's documented beta uses it for topical news responses on supported smart speakers.

How AI systems use Speakable markup

Google says no special structured data is needed for AI Overviews or AI Mode. Do not assume Speakable markup determines which passages an AI service uses or cites.

Which Shopify page sections to mark as Speakable

For Google's documented news use, choose concise, meaningful headlines or summaries that make sense when read aloud. Check that each selector matches the intended visible content.

Check the use case first. Google’s Speakable documentation describes a beta feature for topical news on Google Assistant smart speakers. It specifies publishers of English-language content and users in the US with Google Home devices set to English. Google says no special schema is needed for AI Overviews or AI Mode. A store seeking AI search visibility does not need Speakable markup for that purpose.

What Speakable schema means

SpeakableSpecification is a schema.org type for identifying parts of a page suited to text-to-speech. Google’s documented implementation places a speakable property on an Article or WebPage and uses either cssSelector or xPath to identify the content.

A CSS selector identifies elements by their HTML attributes or structure. An XPath expression identifies nodes in the page structure. For Google’s feature, use one method or the other, not both in the same specification. Neither method is a promise that a passage will be read aloud.

Google’s guidance concerns topical news, not a general recommendation to mark product descriptions or shopping guides for AI citations. Check the current documentation and your own use case before making changes.

Choosing content and selectors

For the documented news feature, Google recommends concise headlines or summaries that make sense when spoken. Avoid material that could be confusing without the visual page, such as photo captions or source attributions. Do not mark an entire article.

Inspect the rendered page and identify the actual class or ID of the text you want to mark. A selector such as .news-summary is only suitable if that class exists on the intended visible content. Theme classes and page structures can change, so check them again after theme updates.

Example for a Shopify article

This illustrative snippet describes an article with a visible element using the class news-summary. Replace that selector with one from your own theme. Use it only on an appropriate article and review any existing article markup first.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": {{ article.title | json }},
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": [".news-summary"]
  }
}
</script>

Shopify’s json filter produces a JSON value, including quotation marks, so do not add another pair around the Liquid output. The example illustrates the property; it does not establish eligibility for a Google feature. Keep any other structured data accurate and consistent with the visible page.

Adding the markup in Shopify

  1. In Shopify admin, open Online Store > Themes and use the code editor on a copy of your theme. Shopify explains the code editor.
  2. Find the article template or section responsible for the relevant content. Inspect any existing structured data before adding another block.
  3. Add the adapted JSON-LD to the relevant Liquid file, outside any section’s {% schema %} settings block. Alternatively, put it in a snippet and render that snippet from the relevant Liquid file. Shopify documents snippets and the render tag.
  4. Preview the affected article and confirm that the script appears on the intended page and that its selector matches the visible text. Check other page types to make sure the markup has not appeared where it does not apply.
  5. Validate and review the output before publishing the theme changes.

Theme structures differ. If your template is JSON, identify its associated Liquid section rather than inserting Liquid code into the JSON template itself. If you are unsure where the markup belongs, ask your theme developer.

Checking the output

  • Use the Schema Markup Validator to inspect schema.org markup. Google recommends it for generic schema validation; it is not a Google feature eligibility test.
  • Inspect the rendered HTML. In your browser’s developer console, document.querySelectorAll('.news-summary') can show which elements match that example selector. Replace it with your actual selector and confirm the matches are the intended content.
  • Use URL Inspection in Search Console to check Google’s indexed information and test a live URL after publication. A live test is not proof that the page is indexed or that a feature will appear.

Valid markup and a matching selector do not guarantee Google will use the content. Recheck both after changes to the theme or page content.

Speakable and FAQ markup

FAQPage is a structured data type for questions and answers; speakable is a property that identifies content suited to speech. They serve different purposes. Adding both does not establish that an AI service will select or cite the page.

Google states that FAQ rich results are no longer shown in Google Search. Write questions and answers when they help customers, and keep any structured data consistent with the visible content.

Where to focus instead

For Google AI features, start with the same fundamentals Google recommends for Search: make useful content available as text, make pages accessible to crawlers, and use internal links to help people find them. Google says a page must be indexed and eligible to appear with a snippet to be eligible as a supporting link in its AI features. Google also says the site must be included in Search generative AI features; inclusion is the default, although a property may inherit its parent’s setting. Meeting these conditions does not guarantee an appearance. Meeting those conditions does not guarantee inclusion.

For another service, consult that service’s own documentation instead of assuming it treats Speakable the same way. There is no basis in the sources used here to promise a Perplexity citation from Speakable markup.

Quick answer

Make product and collection information clear and useful to shoppers. Follow search engine guidance on accessible content and structured data.

What you will do

  • Clarify what the store sells and who it serves.
  • Improve content that supports brand, category and product understanding.
  • Create a repeatable AI visibility monitoring process.

What to check first

  • Search Console for query evidence.
  • Search and competitor research tools for entity evidence.
  • Manual AI answer checks with logged prompts and dates.
  • Structured data validators for product and article output.

Work through it in this order

  1. List the brand, product categories, use cases, materials, audience and location signals that matter.
  2. Check whether collection and product pages state those facts clearly.
  3. Add evidence: specifications, comparisons, FAQs, delivery/returns detail, reviews and trust information.
  4. Use internal links to connect guides, collections and products around the same entity.
  5. Track how the brand and competitors appear in search results, AI answers and citation-like mentions.

Real-world notes

  • Make ecommerce pages useful and clear for shoppers before deciding how to assess AI visibility.
  • Give collection pages clear descriptions of the products and information shoppers need to choose.
  • Do not optimise for AI answers at the expense of conversion. The page still has to sell.

Final checks

  • Core entities listed.
  • Collection pages explain category fit.
  • Product pages include evidence.
  • Trust details are visible.
  • Internal links connect related pages.
  • AI visibility checks are logged.

Watch-outs

  • If a category has regulatory or safety implications, keep claims conservative and source-backed.
  • If an AI answer confuses your brand with another, review the accuracy and clarity of your site information and check the answer again later.
  • If pages are thin, do not jump to schema first. Fix the visible content.
Next action

Use AI visibility tracking after the core Shopify SEO pages are already clear and useful.

Field questions

Does Speakable schema actually help with Google AI Overviews?

Google says no special schema.org markup is required for AI Overviews or AI Mode. Its Speakable documentation describes a separate text-to-speech use for topical news.

Is Speakable schema supported by Shopify themes?

Check your theme's existing structured data and documentation. If you decide to add Speakable markup, the approach depends on your theme and page template.

What CSS selector should I use in Speakable schema for Shopify?

Use a selector that matches the actual visible headline or summary you intend to mark. Inspect the rendered page and test the selector; class names vary by theme.

Does Speakable schema affect traditional SEO ranking?

Google's Speakable documentation describes a text-to-speech feature, not a ranking benefit. Adding structured data does not guarantee a search appearance.