speakableschema.org 속성은 TTS(텍스트 음성 변환)를 사용한 오디오 재생에 적합한 기사 또는 웹페이지의 섹션을 식별합니다. 마크업을 추가하면 검색엔진 및 기타 애플리케이션이 TTS를 사용하여 Google 어시스턴트 지원 기기에서 소리내어 읽을 수 있는 콘텐츠를 식별합니다. 구조화된 speakable 데이터가 있는 웹페이지는 Google 어시스턴트를 사용하여 새로운 채널을 통해 콘텐츠를 배포하고 더 넓은 사용자층에 도달할 수 있습니다.
Google 어시스턴트는 구조화된 speakable 데이터를 사용하여 스마트 스피커 기기에서 주제별 뉴스 쿼리에 응답합니다. 사용자가 특정 주제에 관한 뉴스를 요청하면 Google 어시스턴트가 웹에서 최대 3개의 기사를 표시하고 구조화된 speakable 데이터가 있는 기사의 섹션에 TTS를 사용하여 오디오 재생을 지원합니다. Google 어시스턴트가 speakable 섹션을 소리내어 읽으면 출처를 확인하고 Google 어시스턴트 앱을 통해 사용자의 휴대기기에 전체 기사 URL을 전송합니다.
예
다음은 JSON-LD 코드를 사용하는 구조화된 speakable 데이터와 xPath content-locator 값의 예입니다.
<html>
<head>
<title>Speakable markup example</title>
<meta name="description" content="This page is all about the quick brown fox" />
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "WebPage",
"name": "Quick Brown Fox",
"speakable":
{
"@type": "SpeakableSpecification",
"xPath": [
"/html/head/title",
"/html/head/meta[@name='description']/@content"
]
},
"url": "https://www.example.com/quick-brown-fox"
}
</script>
</head>
<body>
</body>
</html>
사용 가능한 국가 및 언어
speakable 속성은 영어로 설정된 Google Home 기기가 있는 미국 사용자와 영어로 콘텐츠를 게시하는 게시자가 사용할 수 있습니다. 충분한 수의 게시자가 speakable을 구현하는 대로 다른 국가와 언어로도 출시할 계획입니다.
error문제: Google 어시스턴트에서 TTS 오디오를 사용하여 콘텐츠를 실행할 수 없습니다.
done문제 해결
다음 음성 명령을 사용해 보세요.
"$topic에 관한 최신 뉴스는?"
"$topic에 관한 최신 소식은?"
"$topic에 관한 뉴스 재생해 줘."
여전히 문제가 발생하는 경우 순위가 알고리즘 방식으로 결정되었기 때문일 수 있습니다.
Google 어시스턴트는 TTS 오디오 재생을 통해 다른 뉴스 게시자로부터 최대 3개의 기사를 제공합니다. Google의 기사 순위 작성 방식에 관해 자세히 알아보려면 검색 원리를 참고하세요.
추가 오디오 솔루션
구조화된 speakable 데이터 외에 맞춤 애플리케이션용 고급 Google 어시스턴트 통합과 같은 기타 Google 어시스턴트 오디오 솔루션을 뉴스 콘텐츠에 사용할 수 있습니다. 예를 들어 사용자가 Google 어시스턴트를 통해 앱과 소통할 수 있도록 할 수 있습니다. 자세히 알아보려면 Actions on Google 개발자 가이드를 참조하세요.
[null,null,["최종 업데이트: 2025-08-04(UTC)"],[[["\u003cp\u003eSpeakable structured data enables Google Assistant to read aloud sections of your web page or article using text-to-speech (TTS).\u003c/p\u003e\n"],["\u003cp\u003eThis feature is currently in beta and is available for English content in the U.S. on Google Home devices.\u003c/p\u003e\n"],["\u003cp\u003eBy implementing speakable structured data, you can reach a wider audience and make your content accessible through voice search.\u003c/p\u003e\n"],["\u003cp\u003eYou need to follow technical and content guidelines to ensure your content is eligible for this feature and provides an optimal user experience.\u003c/p\u003e\n"],["\u003cp\u003eContent marked as speakable should be concise, focus on key points, and ideally contain around 20-30 seconds of audio per section.\u003c/p\u003e\n"]]],["The `speakable` property, currently in beta, identifies sections of web pages or articles suitable for text-to-speech (TTS) playback. Publishers should add this structured data to enable Google Assistant to read aloud specific content sections, especially for topical news queries. Key actions include following technical and content guidelines, marking up content with either `cssSelector` or `xPath` properties, and focusing on concise, clear headlines and summaries. Content should be 20-30 seconds per section for optimal TTS experience.\n"],null,["# Speakable (BETA) Schema Markup | Google Search Central\n\nSpeakable (`Article`, `WebPage`) structured data (BETA)\n=======================================================\n\n| This feature is in beta and subject to change. We're currently developing this feature and you may see changes in requirements or guidelines.\n\nThe `speakable` [schema.org](https://schema.org/) property\nidentifies sections within an article or webpage that are best suited for audio playback using\ntext-to-speech (TTS). Adding markup allows search engines and other applications to identify content\nto read aloud on Google Assistant-enabled devices using TTS. Web pages with `speakable`\nstructured data can use the Google Assistant to distribute the content through new channels and\nreach a wider base of users.\n\nThe Google Assistant uses `speakable` structured data to answer topical news queries\non smart speaker devices. When users ask for news about a specific topic, the\nGoogle Assistant returns up to three articles from around the web and supports audio playback using\nTTS for sections in the article with `speakable` structured data. When the\nGoogle Assistant reads aloud a `speakable` section, it attributes the source and sends\nthe full article URL to the user's mobile device through the Google Assistant app.\n\nExample\n-------\n\nThe following is an example of `speakable` structured data using JSON-LD code and the\nxPath `content-locator` value: \n\n```text\n\u003chtml\u003e\n \u003chead\u003e\n \u003ctitle\u003eSpeakable markup example\u003c/title\u003e\n \u003cmeta name=\"description\" content=\"This page is all about the quick brown fox\" /\u003e\n \u003cscript type=\"application/ld+json\"\u003e\n {\n \"@context\": \"https://schema.org/\",\n \"@type\": \"WebPage\",\n \"name\": \"Quick Brown Fox\",\n \"speakable\":\n {\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 }\n \u003c/script\u003e\n \u003c/head\u003e\n \u003cbody\u003e\n \u003c/body\u003e\n\u003c/html\u003e\n```\n\nCountry and language availability\n---------------------------------\n\nThe `speakable` property works for users in the U.S. that have Google Home devices\nset to English, and publishers that publish content in English. We hope to launch in other\ncountries and languages as soon as sufficient number of publishers have implemented\n`speakable`.\n\n\nGetting started\n---------------\n\nFor your news content to be eligible as answers to topical news queries, follow these steps:\n\n1. Make sure that you follow [our guidelines](#guidelines).\n2. Add [`speakable` structured data](#structured-data-type-definitions) to your web page.\n\nGuidelines\n----------\n\nYou must follow these guidelines for `speakable` content to be eligible to appear\nin news results.\n\n- [Technical guidelines](#technical-guidelines)\n- [Content guidelines](#content-guidelines)\n- [Search Essentials](/search/docs/essentials)\n- [Structured data general guidelines](/search/docs/appearance/structured-data/sd-policies)\n\n### Technical guidelines\n\nFollow these guidelines when implementing `speakable` markup for Google Assistant.\n\n- Don't add `speakable` structured data to content that may sound confusing in voice-only and voice-forward situations, like datelines (location where the story was reported), photo captions, or source attributions.\n- Rather than highlighting an entire article with `speakable` structured data, focus on key points. This allows listeners to get an idea of the story and not have the TTS readout cut off important details.\n\n### Content guidelines\n\nFollow these guidelines when writing content that you intend to mark up with\n`speakable` structured data.\n\n- Content indicated by `speakable` structured data must have concise headlines and/or summaries that provide users with comprehensible and useful information.\n- If you include the top of the story in `speakable` structured data, we suggest that you rewrite the top of the story to break up information into individual sentences so that it reads more clearly for TTS.\n- For optimal audio user experiences, we recommend around 20-30 seconds of content per section of `speakable` structured data, or roughly two to three sentences.\n\nStructured data type definitions\n--------------------------------\n\n[Speakable](https://pending.schema.org/speakable) is used by the\n[`Article`](https://pending.schema.org/Article) or\n[`Webpage`](https://pending.schema.org/WebPage) object.\nThe full definition of `speakable` is available at\n[schema.org/speakable](https://schema.org/speakable). You must\ninclude the required properties for your content to be eligible for this feature.\n\nThe `speakable` property can be repeated an arbitrary number of times, with two\nkinds of possible `content-locator` values: CSS selectors and xPaths. Use one of\nthe following properties:\n\n| Required properties ||\n|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `cssSelector` | [Text](https://schema.org/Text) Addresses content in the annotated pages (such as class attribute). Use either `cssSelector` or `xPath`; don't use both. For example: ```carbon \"speakable\": { \"@type\": \"SpeakableSpecification\", \"cssSelector\": [ \".headline\", \".summary\" ] } ``` |\n| `xPath` | [Text](https://schema.org/Text) Addresses content using xPaths (assuming an XML view of the content). Use either `cssSelector` or `xPath`; don't use both. For example: ```carbon \"speakable\": { \"@type\": \"SpeakableSpecification\", \"xPath\": [ \"/html/head/title\", \"/html/head/meta[@name='description']/@content\" ] } ``` |\n\nTroubleshooting\n---------------\n\n\nIf you're having trouble implementing or debugging structured data, here are some resources that\nmay help you.\n\n- If you're using a content management system (CMS) or someone else is taking care of your site, ask them to help you. Make sure to forward any Search Console message that details the issue to them.\n- Google does not guarantee that features that consume structured data will show up in search results. For a list of common reasons why Google may not show your content in a rich result, see the [General Structured Data Guidelines](/search/docs/appearance/structured-data/sd-policies).\n- You might have an error in your structured data. Check the [list of structured data errors](https://support.google.com/webmasters/answer/7552505#error_list) and the [Unparsable structured data report](https://support.google.com/webmasters/answer/9166415).\n- If you received a structured data manual action against your page, the structured data on the page will be ignored (although the page can still appear in Google Search results). To fix [structured data issues](https://support.google.com/webmasters/answer/9044175#zippy=%2Cstructured-data-issue), use the [Manual Actions report](https://support.google.com/webmasters/answer/9044175).\n- Review the [guidelines](#guidelines) again to identify if your content isn't compliant with the guidelines. The problem can be caused by either spammy content or spammy markup usage. However, the issue may not be a syntax issue, and so the Rich Results Test won't be able to identify these issues.\n- [Troubleshoot missing rich results / drop in total rich results](https://support.google.com/webmasters/answer/7552505#missing-jobs).\n- Allow time for re-crawling and re-indexing. Remember that it may take several days after publishing a page for Google to find and crawl it. For general questions about crawling and indexing, check the [Google Search crawling and indexing FAQ](/search/help/crawling-index-faq).\n- Post a question in the [Google Search Central forum](https://support.google.com/webmasters/community).\n\n### Can't trigger content\n\n*error* **Problem**: You can't trigger your content\nthrough the Google Assistant using TTS audio.\n\n*done* **Fix the issue**\n\n1. Try the following voice commands:\n - \"What's the latest news about $topic?\"\n - \"What's the latest on $topic?\"\n - \"Play news about $topic.\"\n2. If you're still having trouble, it may be because ranking is determined algorithmically. The Google Assistant provides up to three articles from different news publications through TTS audio playback. For more information about how Google ranks articles, see [How Search works](https://www.google.com/search/howsearchworks/).\n\nMore audio solutions\n--------------------\n\nIn addition to `speakable` structured data, you can use other Google Assistant\naudio solutions for your news content, such as advanced integration of Google Assistant for\nyour own custom applications. For example, allowing users to interact with the app through\nGoogle Assistant. For more information, see the [Actions on Google developer\nguide](/actions)."]]
