Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Memahami cara kerja AMP di hasil penelusuran
Google Penelusuran mengindeks halaman AMP
untuk memberikan pengalaman web yang cepat dan andal. Jika tersedia, halaman AMP dapat
ditampilkan di penelusuran seluler sebagai bagian dari hasil kaya dan carousel. Meskipun AMP itu sendiri bukan merupakan
faktor penentu peringkat,
kecepatan merupakan faktor penentu peringkat
untuk Google Penelusuran. Google Penelusuran menerapkan standar yang sama untuk semua
halaman, apa pun teknologi yang digunakan untuk membuatnya. Untuk mengetahui informasi selengkapnya
tentang manfaat menggunakan AMP, lihat
kisah sukses Project AMP.
Saat pengguna memilih sebuah halaman AMP, Google Penelusuran akan mengambil halaman ini dari
Google AMP Cache, sehingga mengaktifkan berbagai pengoptimalan pemuatan yang sering
membuat halaman tersebut muncul seketika, seperti pra-rendering. Saat ini, halaman AMP di desktop tidak
ditayangkan dari Google AMP Cache/AMP Viewer.
Halaman AMP Kanonis berperilaku
seperti hasil penelusuran standar.
Tampilan awal dalam hasil Penelusuran
Halaman AMP dapat muncul di Google Penelusuran sebagai hasil kaya,
seperti halaman lainnya di web. Agar Google dapat lebih memahami halaman Anda, tambahkan
data terstruktur ke halaman tersebut. Perlu
diperhatikan bahwa Google tidak menjamin penambahan data terstruktur
akan mengaktifkan hasil kaya di hasil Penelusuran. Untuk informasi selengkapnya, lihat
Pedoman Umum Data Terstruktur.
Jika Anda memiliki halaman duplikat untuk konten yang sama, tempatkan data terstruktur yang sama pada semua duplikat halaman, tidak hanya pada halaman kanonis. Untuk informasi selengkapnya tentang penempatan,
lihat Panduan Umum Data
Terstruktur.
Saat pengguna mengklik konten AMP di Google Penelusuran, konten AMP dapat ditampilkan dengan salah satu cara berikut:
Google AMP Viewer: Di bagian atas Google AMP
Viewer, domain konten Anda ditampilkan sehingga pengguna dapat mengetahui siapa yang
menayangkannya.
Signed HTTP Exchange: Teknologi yang memungkinkan browser memperlakukan dokumen
sebagai bagian dari
Asal Anda.
Tentang Google AMP Viewer
Google AMP Viewer adalah lingkungan hybrid yang dapat Anda gunakan untuk mengumpulkan data tentang pengguna di
browser yang mendukung Google AMP Viewer. Google AMP Viewer dapat dirender saat sistem kami
menentukan bahwa fitur ini dapat memberikan pengalaman pengguna yang bermanfaat, terutama saat konten diperkirakan
dapat digeser. Pengumpulan data oleh Google diatur
kebijakan privasi Google. Sebagai penayang halaman AMP
yang kontennya ditampilkan di Google AMP Viewer, pengumpulan data oleh Anda diatur
kebijakan privasi Anda. Sebagai pihak yang menentukan perilaku dan integrasi vendor di halaman AMP Anda, Anda bertanggung jawab untuk memenuhi kewajiban kepatuhan yang timbul akibat penentuan tersebut.
Tentang Signed HTTP Exchange
Dengan Signed HTTP Exchange, Anda dapat menggunakan cookie pihak pertama untuk menyesuaikan konten dan mengukur analisis. Halaman Anda muncul pada URL Anda, bukan URL google.com/amp.
Pada browser yang mendukung Signed HTTP Exchange, Google Penelusuran lebih memprioritaskan penautan ke konten sebagai Signed HTTP Exchange daripada menggunakan Google AMP Viewer. Untuk menampilkan hasil kepada pengguna dalam format ini, Anda harus menayangkan konten AMP sebagai Signed HTTP Exchange, selain dalam format HTML AMP biasa.
Saat ini, Signed HTTP Exchange di Google Penelusuran hanya didukung untuk hasil kaya dan hasil sederhana, tidak untuk carousel. Untuk mempelajari lebih lanjut cara menyiapkan Signed HTTP Exchange untuk halaman AMP, baca Menayangkan AMP menggunakan Signed HTTP Exchange.
[[["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\u003eGoogle Search indexes AMP pages to enhance speed and user experience, potentially featuring them in rich results and carousels, although AMP itself is not a direct ranking factor.\u003c/p\u003e\n"],["\u003cp\u003eWhen users select an AMP page, Google Search often retrieves it from the Google AMP Cache for faster loading, with AMP pages on desktop currently not served from this cache.\u003c/p\u003e\n"],["\u003cp\u003eAMP pages can be enhanced with structured data to potentially appear as rich results, but Google doesn't guarantee this outcome and recommends placing the same structured data on all duplicate pages.\u003c/p\u003e\n"],["\u003cp\u003eAfter clicking AMP content in Google Search, users may view it through the Google AMP Viewer, which displays the content's domain, or via signed exchange, which allows the browser to treat the document as belonging to the publisher's origin.\u003c/p\u003e\n"],["\u003cp\u003eSigned exchange enables the use of first-party cookies and displays the content under the publisher's URL instead of \u003ccode\u003egoogle.com/amp\u003c/code\u003e, with Google Search prioritizing this format over the Google AMP Viewer in supported browsers.\u003c/p\u003e\n"]]],["Google indexes AMP pages for faster mobile web experiences, featuring them in rich results and carousels. While not a direct ranking factor, speed, enhanced by AMP, influences rankings. When selected, AMP pages are often retrieved from the Google AMP Cache for quick loading. AMP pages can include structured data for better search understanding. Content can appear in the Google AMP Viewer or as a signed exchange, which lets publishers use first-party cookies and display their own URL.\n"],null,["# How AMP Works in Google Search | Google Search Central\n\nUnderstand how AMP works in search results\n==========================================\n\nGoogle Search indexes [AMP](/amp)\npages to provide a fast, reliable web experience. When an AMP page is available, it can be\nfeatured on mobile search as part of rich results and carousels. While AMP itself isn't a\nranking factor,\n[speed is a ranking factor](/search/blog/2018/01/using-page-speed-in-mobile-search)\nfor Google Search. Google Search applies the same standard to all\npages, regardless of the technology used to build the page. For more information on the\nbenefits of using AMP, see the\n[AMP Project success stories](https://amp.dev/success-stories/).\n\nWhen users select an AMP page, Google Search retrieves the page from the\n[Google AMP Cache](/amp/cache), enabling a variety of load optimizations that often\nmake these pages appear instantly, such as prerendering. Currently, AMP pages on desktop aren't\nserved from the Google AMP Cache/AMP Viewer.\n[Canonical](/search/docs/crawling-indexing/consolidate-duplicate-urls) AMP Pages behave\nlike standard results.\n\nInitial display in Search results\n---------------------------------\n\n\nAMP pages can appear in Google Search as a [rich result](/search/docs/appearance/structured-data/search-gallery),\njust like other pages on the web. To help Google better understand your page, you can add\n[structured data](/search/docs/appearance/structured-data/intro-structured-data) to your page. It's\nimportant to note that Google doesn't guarantee that adding\nstructured data will enable a rich result in Search results. For more information, refer to the\n[Structured Data General Guidelines](/search/docs/guides/sd-policies).\n\nIf you have duplicate pages for the same content, place the same structured\ndata on all page duplicates, not just on the canonical page. For more information on placement,\nsee the [Structured Data General\nGuidelines](/search/docs/guides/sd-policies#location).\n\n\nAMP pages can also appear as Web Stories. Learn more about how to\n[enable Web Stories on Google Search](/search/docs/appearance/enable-web-stories).\n\nAfter users click AMP content\n-----------------------------\n\n\nWhen users click your AMP content in Google Search, AMP content may be shown in one of two ways:\n\n- **[Google AMP Viewer](#about-google-amp-viewer)**: At the top of the Google AMP Viewer, the domain of your content is displayed so that users understand who published it.\n- **[Signed exchange](#about-signed-exchange)** : A technology that allows the browser to treat a document as belonging to your [Origin](https://en.wikipedia.org/wiki/Same-origin_policy).\n\n### About the Google AMP Viewer\n\nThe Google AMP Viewer is a hybrid environment where you can collect data about the user in\nbrowsers that support the Google AMP Viewer. The Google AMP Viewer may render when our systems\ndetermine it can provide a helpful user experience, especially in situations where swiping\nthrough content is expected. Data collection by Google is governed by Google's\n[privacy policy](https://www.google.com/policies/privacy/). As an AMP page publisher\nwhose content is displayed in the Google AMP Viewer, your data collection is governed by your\nprivacy policy. Because you choose the behaviors and vendor integrations in your AMP page, you\nare responsible for fulfilling the compliance obligations that result from those choices.\n\n### About signed exchange\n\n\nA signed exchange allows you to use first party cookies to customize content and measure\nanalytics. Your page appears under your URL instead of the `google.com/amp` URL.\nGoogle Search prioritizes linking to content as signed exchange over using the Google AMP\nViewer in browsers that support signed exchange. To provide users with results in this format,\nyou must publish AMP content as a signed exchange in addition to the regular AMP HTML format.\nCurrently, signed exchange is only supported in Google Search for rich results and basic\nresults, not carousels. To learn more about setting up signed exchange for AMP pages, visit\n[Serve AMP using Signed Exchanges](https://amp.dev/documentation/guides-and-tutorials/optimize-and-measure/signed-exchange)."]]
