How to Fix: Speakable schema

Speakable schema is an important SEO check in the News & Publishing category. This is a lower-priority optimization. Address it after handling more critical issues.

What this check is really about

Speakable schema is a schema.org markup that points a voice assistant at the specific parts of an article worth reading aloud — usually the headline and a tight summary. It exists for one job: when someone asks a smart speaker “what’s the news on X”, the assistant needs to know which sentences to speak, not the whole article, not the cookie notice, not the byline. Speakable tells it where to look.

Be honest with yourself about scope before you spend time here. This is a News & Publishing feature, it has always been a limited beta, and it earns you nothing on a page nobody would ever ask an assistant to read. That is exactly why the check sits at lower priority. If you run a genuine news operation, it is worth doing well. If you run a plumbing supply store, this is not your bottleneck, and I would leave it for later without a second thought.

Why it matters for SEO

The upside is a surface most of your competitors ignore: voice. For a publisher, being the source a smart speaker reads when a user asks about a breaking story is a genuine distribution channel, and it is one you cannot buy — you earn it with clean markup and authoritative content.

• It makes your articles eligible to be read aloud by voice assistants
• It forces you to write a genuinely speakable summary, which sharpens the article for everyone
• It signals to search engines a clear, machine-readable article structure
• It opens a distribution surface most publishers have not bothered to claim

How to check whether you have this problem

View the page source and search for speakable inside your JSON-LD, or run the URL through a structured-data validator and look for a SpeakableSpecification on the Article. If it is absent, the check fails. Read one candidate sentence out loud while you are there — if it does not stand on its own without the surrounding paragraph, it is not speakable content yet, whatever the markup says.

How to fix this in WordPress

Difficulty Level: MEDIUM – This fix requires some technical knowledge or familiarity with WordPress settings and plugins.

Estimated Time: 20 min

Step 1: Decide what should be spoken

For a news article the answer is almost always the headline plus the opening summary sentence or two — the classic news lede that answers who, what, where in one breath. Write that lede so it survives being read without context. This is the real work; the markup is trivial once the content is right.

Step 2: Mark the region with a stable selector

Speakable uses CSS selectors or XPath to point at the spoken region. Give your headline and summary elements stable, purpose-named classes in your article template — something like a speakable-summary wrapper — so the selector does not break the next time the theme changes. Reference those selectors in the SpeakableSpecification rather than pointing at brittle auto-generated class names.

Step 3: Emit the schema

Add the speakable property to your existing Article JSON-LD. Rank Math and Yoast SEO can output NewsArticle schema; extend it with a speakable block through their schema tools or a small filter rather than hand-rolling a second, competing JSON-LD block on the page.

Step 4: Verify

1. Validate the JSON-LD and confirm the SpeakableSpecification parses cleanly
2. Confirm the selectors actually resolve to the headline and summary on the rendered page
3. Clear your cache so the updated markup is served
4. Re-run the SEO Roadmap audit to confirm the check passes

Recommended Tools & Plugins

These tools can help you fix and prevent this issue:

• Yoast SEO – Comprehensive SEO plugin with built-in checks
• Rank Math – Feature-rich SEO plugin with detailed analysis
• Google Search Console – Free tool to monitor your site’s search presence
• SEO Roadmap – Complete SEO audit and action plan tool

What I would not do

• Do not add speakable markup to non-news pages where it will never fire; it is noise
• Do not point the selector at auto-generated class names that break on every theme update
• Do not mark a whole article as speakable — the point is a short, self-contained summary
• Do not prioritise this over Core Web Vitals or indexing problems; it is a finishing touch, not a foundation

This guide is part of the SEO Roadmap knowledge base – your complete resource for WordPress SEO optimization.