{"id":286,"date":"2026-09-17T00:34:50","date_gmt":"2026-09-16T15:34:50","guid":{"rendered":"https:\/\/www.studio-jt.co.kr\/seo-glossary\/speakable\/"},"modified":"2026-11-15T18:46:52","modified_gmt":"2026-11-15T09:46:52","slug":"speakable","status":"publish","type":"seo_glossary","link":"https:\/\/www.studio-jt.co.kr\/en\/seo-glossary\/speakable\/","title":{"rendered":"Speakable structured data"},"content":{"rendered":"<h2 class=\"wp-block-heading\">A Property That Tells Voice Assistants &#8220;Read This Part&#8221;<\/h2>\n<p class=\"wp-block-paragraph\">Speakable is a schema.org property that marks the sections of an article or web page best suited to be read aloud with text-to-speech (TTS, technology that turns text into sound).&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> With this markup, search engines and other apps can identify the content to read aloud on devices with Google Assistant.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> It&#8217;s a lot like highlighting just two or three sentences in a newspaper article and saying, &#8220;Just read this part.&#8221;<\/p>\n<p class=\"wp-block-paragraph\">schema.org defines it the same way: it indicates sections of a web page that are particularly highlighted as suitable for reading aloud. Other sections may also be read depending on the situation, but the property is meant to mark the parts that will generally be most useful.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/schema.org\/speakable\" target=\"_blank\" rel=\"noopener\">schema.org<\/a> The one actually using it is Google Assistant. When a user asks a smart speaker for the latest news on a topic, Assistant picks up to three articles from the web, reads the sections marked speakable, attributes the source, and sends the full article URL to the Assistant app on the user&#8217;s phone.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<h2 class=\"wp-block-heading\">There Are Only Two Ways to Mark It: Selectors<\/h2>\n<p class=\"wp-block-paragraph\">Attach the property to an Article or WebPage type, and point to the sections to read with either a CSS selector (cssSelector) or an XPath expression (xPath). You don&#8217;t use both together.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> The schema.org definition includes a third method that references an element&#8217;s id by URL, but Google&#8217;s documentation lists only the first two as supported.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/schema.org\/speakable\" target=\"_blank\" rel=\"noopener\">schema.org<\/a> The example in Google&#8217;s documentation uses XPath to point to the page title and meta description.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<pre class=\"wp-block-code\"><code>{\n  \"@context\": \"https:\/\/schema.org\/\",\n  \"@type\": \"WebPage\",\n  \"name\": \"Quick Brown Fox\",\n  \"speakable\": {\n    \"@type\": \"SpeakableSpecification\",\n    \"xPath\": [\n      \"\/html\/head\/title\",\n      \"\/html\/head\/meta[@name='description']\/@content\"\n    ]\n  },\n  \"url\": \"https:\/\/www.example.com\/quick-brown-fox\"\n}<\/code><\/pre>\n<p class=\"wp-block-paragraph\">There&#8217;s one difference in spelling. The official schema.org property name is lowercase xpath, but Google&#8217;s documentation writes xPath in both its example and its property table.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/schema.org\/SpeakableSpecification\" target=\"_blank\" rel=\"noopener\">schema.org<\/a> If you&#8217;re targeting Google Assistant, it&#8217;s safer to follow Google&#8217;s spelling. Google&#8217;s documentation also gives cssSelector examples that point to classes, such as .headline and .summary.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> In practice, adding classes to the headline and summary paragraph and pointing to them this way is easier to manage than XPath.<\/p>\n<h2 class=\"wp-block-heading\">Google&#8217;s Requirements for Read-Aloud Sections<\/h2>\n<p class=\"wp-block-paragraph\">Google&#8217;s guidelines on what to mark are short and specific.<\/p>\n<ul class=\"wp-block-list\"><li>The marked sections should be concise headlines or summaries that give listeners useful, understandable information.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Don&#8217;t mark up the whole article; focus on the key points so the reading isn&#8217;t cut off midway and listeners don&#8217;t miss important content.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>If you include the top of the article, Google recommends rewriting the information into separate sentences so it reads clearly as speech.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>It recommends 20 to 30 seconds per section, roughly two or three sentences.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><li>Don&#8217;t mark parts that are confusing when only heard, such as datelines, photo captions and source attributions.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/li><\/ul>\n<h2 class=\"wp-block-heading\">In Beta from 2018 to Today<\/h2>\n<p class=\"wp-block-paragraph\">The vocabulary for this property predates Google&#8217;s announcement. schema.org added the SpeakableSpecification type, the cssSelector and xpath properties, and WebPage&#8217;s speakable property as newly proposed terms in version 3.2 in March 2017, and promoted them to the official core vocabulary in version 3.5 in April 2019.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/schema.org\/docs\/releases.html\" target=\"_blank\" rel=\"noopener\">schema.org<\/a> On July 24, 2018, Google announced the speakable specification, developed with schema.org, on the Search Central Blog, explaining that it lets eligible publishers mark the sections of news articles most suitable for Assistant to read aloud.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/blog\/2018\/07\/hey-google-whats-latest-news\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> It opened first to English-speaking users in the US, and said it would expand to other languages and countries once enough publishers had implemented it.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/blog\/2018\/07\/hey-google-whats-latest-news\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">The documentation at the time, as quoted by an industry outlet the day after the announcement, carried a notice that the feature was in beta and its requirements could change.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/google-speakable-annotations-google-assistant-26100.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> The current documentation, updated in September 2026, still has the same notice and the (BETA) label.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">There has been sporadic news since then. In December 2019, Danny Sullivan said speakable was no longer limited to news content, but added that putting this markup on any site doesn&#8217;t guarantee Assistant will always use it, and that it was still in beta.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/speakable-markup-google-news-beyond-28677.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> In September 2020, after an email from a Google team was made public and a rumor spread that it had been deprecated, John Mueller corrected it, saying it was not deprecated and the markup was still useful.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/google-speakable-markup-is-not-obsolete-30086.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> When Google announced in June 2025 that it was ending support in search results for seven types of structured data, speakable was not on the list.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/blog\/2025\/06\/simplifying-search-results\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> It is still listed as a news item in Google&#8217;s structured data feature gallery.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/search-gallery\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">But being alive on paper is not the same as being used. Despite what Sullivan said in 2019, the current documentation&#8217;s getting-started guidance and guidelines are still written around news content and news results.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> schema.org shows usage, counted from Google&#8217;s index, only as a range of between 100,000 and 1 million domains.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/schema.org\/speakable\" target=\"_blank\" rel=\"noopener\">schema.org<\/a> Ahrefs&#8217; voice search guide never mentions speakable.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/ahrefs.com\/blog\/voice-search\/\" target=\"_blank\" rel=\"noopener\">Ahrefs<\/a> Neither does Semrush&#8217;s Google voice search guide.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.semrush.com\/blog\/google-voice-search\/\" target=\"_blank\" rel=\"noopener\">Semrush<\/a> Even within the industry, it&#8217;s a fringe property.<\/p>\n<h2 class=\"wp-block-heading\">It Doesn&#8217;t Work on Korean-Language Sites<\/h2>\n<p class=\"wp-block-paragraph\">The most important fact is its scope. The country and language section of Google&#8217;s documentation states firmly that the speakable property works for users in the US who have Google Home devices set to English, and for publishers that publish content in English.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> The condition for expanding to other countries and languages is that enough publishers implement it, and this wording is virtually the same in the 2018 announcement and the 2026 documentation.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> That means the condition hasn&#8217;t changed in eight years.<\/p>\n<p class=\"wp-block-paragraph\">So even if a Korean-language site adds speakable now, Google Assistant won&#8217;t read it aloud. There&#8217;s no harm in adding it either. In April 2025, John Mueller said structured data doesn&#8217;t raise a site&#8217;s rankings, and that using schema.org items not on Google&#8217;s feature list won&#8217;t cause problems but will make almost no visible difference in search.&nbsp;<a class=\"jt-src jt-src--data\" href=\"https:\/\/www.seroundtable.com\/google-structured-data-ranking-39232.html\" target=\"_blank\" rel=\"noopener\">Search Engine Roundtable<\/a> Your time is better spent on the <a href=\"\/en\/seo-glossary\/json-ld\/\">structured data<\/a> Google actually displays, such as types for articles, products and organization information.<\/p>\n<h2 class=\"wp-block-heading\">It Has Nothing to Do with Rankings<\/h2>\n<p class=\"wp-block-paragraph\">The claim that adding speakable raises your search rankings is not true. Google&#8217;s general structured data guidelines state that even accurate markup that passes the Rich Results Test is not guaranteed to appear in search results; structured data makes a feature possible but does not guarantee it will appear.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/sd-policies\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> The troubleshooting section of the speakable documentation also notes that even with markup, selection is decided by algorithmic ranking, and Assistant reads at most three articles from different publishers.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> Markup makes you eligible; being eligible and being picked are two different things. This is in line with the answer optimization that <a href=\"\/en\/seo-glossary\/aeo\/\">AEO<\/a> talks about. A page with well-organized answers comes first, and markup comes after.<\/p>\n<h2 class=\"wp-block-heading\">Gemini Is Taking Over the Speaker<\/h2>\n<p class=\"wp-block-paragraph\">The devices speakable targeted were speakers with Google Assistant. But in March 2025, Google announced it would replace the existing Assistant on phones with Gemini, making Assistant unavailable on most devices, and previewed bringing a Gemini-powered experience to home devices such as speakers, displays and TVs.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/blog.google\/products-and-platforms\/products\/gemini\/google-assistant-gemini-mobile\/\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> In October 2025, it announced that the Gemini for Home voice assistant would upgrade and replace Assistant on speakers and smart displays.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/blog.google\/products-and-platforms\/devices\/google-nest\/gemini-for-home-launch\/\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> It plans to start with early access in the US and expand to other countries in 2026.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/blog.google\/products-and-platforms\/devices\/google-nest\/gemini-for-home-things-to-try\/\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a><\/p>\n<p class=\"wp-block-paragraph\">There is no official word yet that Gemini for Home reads speakable markup. The speakable documentation, updated in September 2026, still mentions only Google Assistant.&nbsp;<a class=\"jt-src jt-src--official\" href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Google (official)<\/a> So the accurate reading is that this property is alive in the documentation, its devices are changing, and it was never opened to Korean in the first place. The broader trend of voice and AI reading our content aloud is a <a href=\"\/en\/seo-glossary\/geo\/\">GEO<\/a> question, and the answer is not a line of markup but short, accurate paragraphs.<\/p>\n<h2 class=\"wp-block-heading\">References<\/h2>\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/speakable\" target=\"_blank\" rel=\"noopener\">Speakable (Article, WebPage) structured data (BETA) &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/blog\/2018\/07\/hey-google-whats-latest-news\" target=\"_blank\" rel=\"noopener\">Hey Google, what&#8217;s the latest news? The 2018 speakable announcement &#8211; Google Search Central Blog<\/a><\/li><li><a href=\"https:\/\/schema.org\/speakable\" target=\"_blank\" rel=\"noopener\">speakable property definition &#8211; Schema.org<\/a><\/li><li><a href=\"https:\/\/schema.org\/SpeakableSpecification\" target=\"_blank\" rel=\"noopener\">SpeakableSpecification type definition &#8211; Schema.org<\/a><\/li><li><a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/sd-policies\" target=\"_blank\" rel=\"noopener\">General structured data guidelines &#8211; Google Search Central<\/a><\/li><li><a href=\"https:\/\/www.seroundtable.com\/speakable-markup-google-news-beyond-28677.html\" target=\"_blank\" rel=\"noopener\">Google: Speakable Markup Works Outside Of News Content &#8211; Search Engine Roundtable<\/a><\/li><li><a href=\"https:\/\/www.seroundtable.com\/google-speakable-markup-is-not-obsolete-30086.html\" target=\"_blank\" rel=\"noopener\">Google Speakable Markup Is Not Obsolete &#8211; Search Engine Roundtable<\/a><\/li><li><a href=\"https:\/\/blog.google\/products-and-platforms\/devices\/google-nest\/gemini-for-home-launch\/\" target=\"_blank\" rel=\"noopener\">Gemini for Home: The helpful home gets an AI upgrade &#8211; Google The Keyword<\/a><\/li><\/ul>","protected":false},"excerpt":{"rendered":"<p>Speakable is a structured data property that marks the parts of an article or web page best suited for a voice assistant to read aloud. When Google Assistant speakers answer questions about current news, they use this markup to read articles from up to three publishers. It launched in beta in 2018, is still in beta today and works only for English-language content in the US, so it offers no immediate benefit for Korean-language sites.<\/p>\n","protected":false},"template":"","glossary_categories":[21],"class_list":["post-286","seo_glossary","type-seo_glossary","status-publish","hentry","glossary_categories-technical"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/286","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary"}],"about":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/types\/seo_glossary"}],"version-history":[{"count":1,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/286\/revisions"}],"predecessor-version":[{"id":2371,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/seo_glossary\/286\/revisions\/2371"}],"wp:attachment":[{"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/media?parent=286"}],"wp:term":[{"taxonomy":"glossary_categories","embeddable":true,"href":"https:\/\/www.studio-jt.co.kr\/en\/wp-json\/wp\/v2\/glossary_categories?post=286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}