Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Data terstruktur Speakable (Article, WebPage) (BETA)
Properti speakableschema.org
mengidentifikasi bagian dalam artikel atau halaman web yang paling cocok untuk pemutaran audio menggunakan
text-to-speech (TTS). Penambahan markup memungkinkan mesin telusur dan aplikasi lain mengidentifikasi konten
yang akan dibacakan menggunakan TTS melalui perangkat yang dilengkapi dengan Asisten Google. Halaman web dengan data terstruktur speakable
dapat menggunakan Asisten Google untuk mendistribusikan konten melalui saluran baru dan
menjangkau basis pengguna yang lebih luas.
Asisten Google menggunakan data terstruktur speakable untuk menjawab kueri berita berdasarkan topik
melalui perangkat smart speaker. Saat pengguna meminta berita tentang topik tertentu,
Asisten Google akan menampilkan hingga tiga artikel dari berbagai sumber di web dan mendukung pemutaran audio menggunakan
TTS untuk bagian-bagian di dalam artikel yang menggunakan data terstruktur speakable. Saat
membacakan bagian speakable, Asisten Google akan mengatribusikan sumbernya dan mengirimkan
URL artikel lengkap ke perangkat seluler pengguna melalui aplikasi Asisten Google.
Contoh
Berikut adalah contoh data terstruktur speakable yang menggunakan kode JSON-LD dan
nilai content-locator xPath:
<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>
Negara dan bahasa yang tersedia
Properti speakable tersedia bagi pengguna di AS yang memiliki perangkat Google Home
yang disetel ke bahasa Inggris, dan penerbit yang memublikasikan konten dalam bahasa Inggris. Kami berharap dapat meluncurkan properti ini di
negara dan dalam bahasa lain setelah jumlah penerbit yang menerapkan speakable
sudah memadai.
Memulai
Agar konten berita memenuhi syarat untuk ditampilkan sebagai jawaban atas kueri berita berdasarkan topik, ikuti langkah-langkah berikut:
Ikuti panduan ini saat menerapkan markup speakable untuk Asisten Google.
Jangan tambahkan data terstruktur speakable ke konten yang dapat terdengar membingungkan dalam
situasi suara-saja dan yang mengutamakan suara, seperti informasi tanggal dan waktu (lokasi tempat berita dilaporkan),
teks foto, atau atribusi sumber.
Fokuskan pada poin-poin penting dalam artikel,
bukan menyorot seluruh artikel dengan data terstruktur speakable. Dengan begitu, pemroses dapat menangkap ide berita dan TTS
tidak akan memenggal detail yang penting.
Pedoman konten
Ikuti panduan ini saat menulis konten yang ingin Anda markup dengan
data terstruktur speakable.
Konten yang ditunjukkan oleh data terstruktur speakable harus memiliki judul
dan/atau ringkasan singkat yang memberikan informasi yang mudah dipahami dan berguna kepada pengguna.
Jika Anda menyertakan bagian paling atas berita dalam data terstruktur speakable, sebaiknya
tulis ulang bagian tersebut untuk memecah informasi menjadi kalimat-kalimat
yang dapat dibaca lebih jelas oleh TTS.
Agar pengguna mendapatkan pengalaman audio yang optimal, kami merekomendasikan sekitar 20-30 detik konten per
bagian data terstruktur speakable, atau sekitar dua hingga tiga kalimat.
Definisi jenis data terstruktur
Speakable digunakan oleh objek
Article atau
Webpage.
Definisi lengkap speakable tersedia di
schema.org/speakable. Anda harus
menyertakan properti wajib agar konten Anda memenuhi syarat untuk menggunakan fitur ini.
Properti speakable dapat diulang sebanyak yang diinginkan, dengan dua
jenis nilai content-locator yang dimungkinkan: pemilih CSS dan XPath. Gunakan salah satu
properti berikut:
Jika Anda mengalami masalah saat menerapkan atau mendebug data terstruktur, berikut beberapa referensi yang
dapat membantu Anda.
Jika Anda menggunakan sistem pengelolaan konten (CMS) atau ada orang lain yang menangani situs Anda,
minta mereka untuk membantu Anda. Pastikan untuk meneruskan pesan Search Console yang menjelaskan masalah tersebut kepada mereka.
Google tidak menjamin bahwa fitur yang menggunakan data terstruktur akan muncul dalam hasil penelusuran.
Untuk mengetahui daftar alasan umum mengapa Google tidak dapat menampilkan konten Anda dalam hasil kaya, lihat
Panduan Umum terkait Data Terstruktur.
Jika halaman Anda dikenai tindakan manual data terstruktur, data terstruktur pada
halaman itu akan diabaikan (meskipun halaman masih bisa muncul di hasil Google Penelusuran). Untuk memperbaiki
masalah data terstruktur, gunakan laporan Tindakan Manual.
Tinjau pedoman lagi untuk mengidentifikasi apakah konten Anda tidak mematuhi
pedoman. Masalah itu mungkin disebabkan oleh konten yang berisi spam atau penggunaan markup yang berisi spam.
Namun, masalahnya mungkin bukan pada sintaksis, sehingga Pengujian Hasil Kaya tidak akan dapat
mengidentifikasi masalah tersebut.
Tunggu hingga crawling ulang dan pengindeksan ulang selesai. Perlu diingat bahwa Google mungkin memerlukan waktu beberapa hari
untuk mencari dan meng-crawl halaman setelah Anda memublikasikannya. Untuk pertanyaan umum terkait crawling dan pengindeksan, lihat
FAQ crawling dan pengindeksan Google Penelusuran.
errorMasalah: Anda tidak dapat memicu konten
melalui Asisten Google menggunakan audio TTS.
donePerbaiki masalahnya
Coba perintah suara berikut:
"Apa berita terbaru tentang $topic?"
"Bagaimana kabar terbaru tentang $topic?
"Putar berita tentang $topic".
Jika Anda masih mengalami masalah, mungkin penyebabnya karena peringkat ditetapkan menggunakan algoritme.
Asisten Google menyediakan hingga tiga artikel dari publikasi berita berbeda melalui
pemutaran audio TTS. Untuk informasi selengkapnya tentang cara Google menentukan peringkat artikel, lihat
Cara kerja Penelusuran.
Solusi audio lainnya
Selain data terstruktur speakable, Anda dapat menggunakan solusi audio
Asisten Google lainnya untuk konten berita, seperti integrasi lanjutan Asisten Google untuk
aplikasi kustom Anda sendiri. Misalnya, mengizinkan pengguna untuk berinteraksi dengan aplikasi melalui
Asisten Google. Untuk informasi selengkapnya, lihat panduan
developer Actions on Google.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 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)."]]
