{"id":25536,"date":"2026-09-05T02:45:07","date_gmt":"2026-09-04T23:45:07","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/speakable-article-webpage-structured-data-beta\/"},"modified":"2026-09-05T02:45:07","modified_gmt":"2026-09-04T23:45:07","slug":"speakable-article-webpage-structured-data-beta","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/speakable-article-webpage-structured-data-beta\/","title":{"rendered":"Speakable (Article, WebPage) structured data (BETA)"},"content":{"rendered":"<aside class=\"note\">This feature is in beta and subject to change. We&#8217;re currently developing this<br \/>\n  feature and you may see changes in requirements or guidelines.<\/aside>\n<p>The <code>speakable<\/code> <a href=\"https:\/\/schema.org\/\" class=\"external-link\">schema.org<\/a> property<br \/>\n  identifies sections within an article or webpage that are best suited for audio playback using<br \/>\n  text-to-speech (TTS). Adding markup allows search engines and other applications to identify content<br \/>\n  to read aloud on Google Assistant-enabled devices using TTS. Web pages with <code>speakable<\/code><br \/>\n  structured data can use the Google Assistant to distribute the content through new channels and<br \/>\n  reach a wider base of users.<\/p>\n<p>The Google Assistant uses <code>speakable<\/code> structured data to answer topical news queries<br \/>\n  on smart speaker devices. When users ask for news about a specific topic, the<br \/>\n  Google Assistant returns up to three articles from around the web and supports audio playback using<br \/>\n  TTS for sections in the article with <code>speakable<\/code> structured data. When the<br \/>\n  Google Assistant reads aloud a <code>speakable<\/code> section, it attributes the source and sends<br \/>\n  the full article URL to the user&#8217;s mobile device through the Google Assistant app.<\/p>\n<h2 id=\"example\" tabindex=\"-1\">Example<\/h2>\n<p>The following is an example of <code>speakable<\/code> structured data using JSON-LD code and the<br \/>\nxPath <code>content-locator<\/code> value:<\/p>\n<div><\/div>\n<h2 id=\"country-availability\" tabindex=\"-1\">Country and language availability<\/h2>\n<p>The <code>speakable<\/code> property works for users in the U.S. that have Google Home devices<br \/>\n      set to English, and publishers that publish content in English. We hope to launch in other<br \/>\n      countries and languages as soon as sufficient number of publishers have implemented<br \/>\n      <code>speakable<\/code>.<\/p>\n<p><h2 id=\"getting-started\" tabindex=\"-1\">Getting started<\/h2>\n<p>For your news content to be eligible as answers to topical news queries, follow these steps:<\/p>\n<ol>\n<li>Make sure that you follow <a href=\"#guidelines\">our guidelines<\/a>.<\/li>\n<li>Add <a href=\"#structured-data-type-definitions\"><code>speakable<\/code> structured data<\/a><br \/>\n        to your web page.<\/li>\n<\/ol>\n<h2 id=\"guidelines\" tabindex=\"-1\">Guidelines<\/h2>\n<p>You must follow these guidelines for <code>speakable<\/code> content to be eligible to appear<br \/>\n      in news results.<\/p>\n<ul>\n<li><a href=\"#technical-guidelines\">Technical guidelines<\/a><\/li>\n<li><a href=\"#content-guidelines\">Content guidelines<\/a><\/li>\n<li><a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/search-essentials-overview\/\">Search Essentials<\/a><\/li>\n<li><a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/structured-data-guidelines\/\">Structured data general guidelines<\/a><\/li>\n<\/ul>\n<h3 id=\"technical-guidelines\" tabindex=\"-1\">Technical guidelines<\/h3>\n<p>Follow these guidelines when implementing <code>speakable<\/code> markup for Google Assistant.<\/p>\n<ul>\n<li>Don&#8217;t add <code>speakable<\/code> structured data to content that may sound confusing in<br \/>\n        voice-only and voice-forward situations, like datelines (location where the story was reported),<br \/>\n        photo captions, or source attributions.<\/li>\n<li>Rather than highlighting an entire article with <code>speakable<\/code> structured data,<br \/>\n        focus on key points. This allows listeners to get an idea of the story and not have the TTS<br \/>\n        readout cut off important details.<\/li>\n<\/ul>\n<h3 id=\"content-guidelines\" tabindex=\"-1\">Content guidelines<\/h3>\n<p>Follow these guidelines when writing content that you intend to mark up with<br \/>\n      <code>speakable<\/code> structured data.<\/p>\n<ul>\n<li>Content indicated by <code>speakable<\/code> structured data must have concise headlines<br \/>\n        and\/or summaries that provide users with comprehensible and useful information.<\/li>\n<li>If you include the top of the story in <code>speakable<\/code> structured data, we suggest<br \/>\n        that you rewrite the top of the story to break up information into individual sentences so<br \/>\n        that it reads more clearly for TTS.<\/li>\n<li>For optimal audio user experiences, we recommend around 20-30 seconds of content per<br \/>\n        section of <code>speakable<\/code> structured data, or roughly two to three sentences.<\/li>\n<\/ul>\n<h2 id=\"structured-data-type-definitions\" tabindex=\"-1\">Structured data type definitions<\/h2>\n<p><a href=\"https:\/\/pending.schema.org\/speakable\" class=\"external-link\"><span>Speakable<\/span><\/a> is used by the<br \/>\n      <a href=\"https:\/\/pending.schema.org\/Article\" class=\"external-link\"><code>Art\u00edculo<\/code><\/a> o<br \/>\n      <a href=\"https:\/\/pending.schema.org\/WebPage\" class=\"external-link\"><code>Webpage<\/code><\/a> object.<br \/>\n      The full definition of <code>speakable<\/code> is available at<br \/>\n      <a href=\"https:\/\/schema.org\/speakable\" class=\"external-link\">schema.org\/speakable<\/a>. You must<br \/>\n      include the required properties for your content to be eligible for this feature.<\/p>\n<p>The <code>speakable<\/code> property can be repeated an arbitrary number of times, with two<br \/>\n      kinds of possible <code>content-locator<\/code> values: CSS selectors and xPaths. Use one of<br \/>\n      the following properties:<\/p>\n<table class=\"responsive fixed\">\n<colgroup>\n<col width=\"20%\"><\/colgroup>\n<thead>\n<tr>\n<th colspan=\"2\">Required properties<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>cssSelector<\/code><\/td>\n<td>\n<p><code><a href=\"https:\/\/schema.org\/Text\" class=\"external-link\">Text<\/a><\/code><\/p>\n<p>Addresses content in the annotated pages (such as class attribute). Use either<br \/>\n            <code>cssSelector<\/code> o <code>xPath<\/code>; don&#8217;t use both. For example:<\/p>\n<div><\/div>\n<\/td>\n<\/tr>\n<tr>\n<td><code>xPath<\/code><\/td>\n<td>\n<p><code><a href=\"https:\/\/schema.org\/Text\" class=\"external-link\">Text<\/a><\/code><\/p>\n<p>Addresses content using xPaths (assuming an XML view of the content). Use either<br \/>\n               <code>cssSelector<\/code> o <code>xPath<\/code>; don&#8217;t use both. For example:<\/p>\n<div><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"troubleshooting\" tabindex=\"-1\">Troubleshooting<\/h2>\n<p>\n    If you&#8217;re having trouble implementing or debugging structured data, here are some resources that<br \/>\n    may help you.\n  <\/p>\n<ul>\n<li>If you&#8217;re using a content management system (CMS) or someone else is taking care of your site,<br \/>\n      ask them to help you. Make sure to forward any Search Console message that details the issue to them.<\/li>\n<li>Google does not guarantee that features that consume structured data will show up in search results.<br \/>\n      For a list of common reasons why Google may not show your content in a rich result, see the<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/structured-data-guidelines\/\">General Structured Data Guidelines<\/a>.<\/li>\n<li>You might have an error in your structured data. Check the<br \/>\n      <a href=\"https:\/\/support.google.com\/webmasters\/answer\/13300873\" class=\"external-link\">list of structured data errors<\/a><br \/>\n      and the <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9166415\" class=\"external-link\">Unparsable structured data report<\/a>.<\/li>\n<li>If you received a structured data manual action against your page, the structured data on<br \/>\n      the page will be ignored (although the page can still appear in Google Search results). To fix<br \/>\n      <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9044175#zippy=%2Cstructured-data-issue\" class=\"external-link\">structured data issues<\/a>, use the <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9044175\" class=\"external-link\">Manual Actions report<\/a>.\n    <\/li>\n<li>Review the <a href=\"#guidelines\">guidelines<\/a> again to identify if your content isn&#8217;t compliant<br \/>\n      with the guidelines. The problem can be caused by either spammy content or spammy markup usage.<br \/>\n        However, the issue may not be a syntax issue, and so the Rich Results Test won&#8217;t be able to<br \/>\n        identify these issues.\n    <\/li>\n<li><a href=\"https:\/\/support.google.com\/webmasters\/answer\/13300208\" class=\"external-link\">Troubleshoot missing rich results \/ drop in total rich results<\/a>.<\/li>\n<li>Allow time for re-crawling and re-indexing. Remember that it may take several days after<br \/>\n      publishing a page for Google to find and crawl it. For general questions about crawling and indexing, check the<br \/>\n      <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/google-search-crawling-and-indexing-faq\/\" class=\"external-link\">Google Search crawling and indexing FAQ<\/a>.\n    <\/li>\n<li>Post a question in the <a href=\"https:\/\/support.google.com\/webmasters\/community\" class=\"external-link\">Google Search Central forum<\/a>.<\/li>\n<\/ul>\n<h3 id=\"trigger-content\" tabindex=\"-1\">Can&#8217;t trigger content<\/h3>\n<p><i class=\"material-icons\" aria-hidden=\"true\">error<\/i> <b>Problem<\/b>: You can&#8217;t trigger your content<br \/>\n      through the Google Assistant using TTS audio.<\/p>\n<p><i class=\"material-icons\" aria-hidden=\"true\">done<\/i> <b>Fix the issue<\/b><\/p>\n<ol>\n<li>Try the following voice commands:\n<ul>\n<li>&#8220;What&#8217;s the latest news about $topic?&#8221;<\/li>\n<li>&#8220;What&#8217;s the latest on $topic?&#8221;<\/li>\n<li>&#8220;Play news about $topic.&#8221;<\/li>\n<\/ul>\n<\/li>\n<li>If you&#8217;re still having trouble, it may be because ranking is determined algorithmically.<br \/>\n          The Google Assistant provides up to three articles from different news publications through<br \/>\n          TTS audio playback. For more information about how Google ranks articles, see<br \/>\n          <a href=\"https:\/\/www.google.com\/search\/howsearchworks\/\" class=\"external-link\">How Search works<\/a>.\n        <\/li>\n<\/ol>\n<h2 id=\"more-audio-solutions\" tabindex=\"-1\">More audio solutions<\/h2>\n<p>In addition to <code>speakable<\/code> structured data, you can use other Google Assistant<br \/>\n      audio solutions for your news content, such as advanced integration of Google Assistant for<br \/>\n      your own custom applications. For example, allowing users to interact with the app through<br \/>\n      Google Assistant. For more information, see the <a href=\"https:\/\/developers.google.com\/actions\" class=\"external-link\">Actions on Google developer<br \/>\n      guide<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Speakable schema markup can be used to identify content that is best suited for audio playback. Learn about SEO for voice search with this guide.<\/p>\n","protected":false},"menu_order":110,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[679],"ar_kb_etiket":[],"class_list":["post-25536","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-feature-guides"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25536","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25536\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27566"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=25536"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=25536"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=25536"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}