Identify and fix AMP Signed Exchange errors in Search Console
Stay organized with collectionsSave and categorize content based on your preferences.
Tuesday, August 18, 2020
Signed Exchanges (SXG) is a subset of the emerging family of specifications calledWeb Packaging, which enables publishers to
safely make their content portable, while still keeping the publisher's integrity and
attribution. In 2019,Google Search started linking to signed AMP pagesserved from Google's cache when available. This feature allows the content to be prefetched
without loss of privacy, while attributing the content to the right origin.
Today we are happy to announce that sites implementing SXG for their AMP pages will be able to
understand if there are any issues preventing Google from serving the SXG version of their page
using the Google AMP Cache.
Use theAMP reportto check if your site has any SXG related issues - look for issues with 'signed exchange' in
their name. We will also send emails to alert you of new issues as we detect them.
To help with debugging and to verify a specific page is served using SXG, you can inspect a URL
using theURL Inspection Toolto find if any SXG related issues appear on the AMP section of the analysis.
You can diagnose issues affecting the indexed version of the page or use the "live" option which
will check validity for the live version currently served by your site.
To learn more about the types of SXG issues we can report on, check out thisHelp Center Articleon SXG issues. If you have any questions, you can ask in thehelp communityor the Google WebmastersTwitter handle.
Posted byAmir Rachum, Search Console Software Engineer and Jeffrey Jose, Google Search Product Manager.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eGoogle Search can now detect and report issues preventing the serving of Signed Exchanges (SXG) for AMP pages from the Google AMP Cache.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can use the AMP report in Search Console to identify SXG-related issues impacting their pages.\u003c/p\u003e\n"],["\u003cp\u003eThe URL Inspection Tool allows publishers to debug and verify if a specific page is served via SXG, including live and indexed versions.\u003c/p\u003e\n"],["\u003cp\u003eA help center article provides further details on the types of SXG issues reported and troubleshooting guidance is available via the help community and Google Webmasters Twitter.\u003c/p\u003e\n"]]],["Signed Exchanges (SXG) allow publishers to make content portable while maintaining integrity. Google Search now links to signed AMP pages from its cache. Sites can now identify issues preventing Google from serving the SXG version of their AMP pages using the AMP report. The URL Inspection Tool can also diagnose SXG-related problems. Users can check for issues with the indexed or live versions of their pages. Additional details are available in the Help Center or through the help community.\n"],null,["# Identify and fix AMP Signed Exchange errors in Search Console\n\nTuesday, August 18, 2020\n\n\nSigned Exchanges (SXG) is a subset of the emerging family of specifications called\n[Web Packaging](https://github.com/WICG/webpackage), which enables publishers to\nsafely make their content portable, while still keeping the publisher's integrity and\nattribution. In 2019,\n[Google Search started linking to signed AMP pages](/search/blog/2019/04/instant-loading-amp-pages-from-your-own)\nserved from Google's cache when available. This feature allows the content to be prefetched\nwithout loss of privacy, while attributing the content to the right origin.\n\n\nToday we are happy to announce that sites implementing SXG for their AMP pages will be able to\nunderstand if there are any issues preventing Google from serving the SXG version of their page\nusing the Google AMP Cache.\n\n\nUse the\n[AMP report](https://support.google.com/webmasters/answer/7450883#sgx_warning_list)\nto check if your site has any SXG related issues - look for issues with 'signed exchange' in\ntheir name. We will also send emails to alert you of new issues as we detect them.\n\n\nTo help with debugging and to verify a specific page is served using SXG, you can inspect a URL\nusing the\n[URL Inspection Tool](https://support.google.com/webmasters/answer/9012289)\nto find if any SXG related issues appear on the AMP section of the analysis.\n\n\nYou can diagnose issues affecting the indexed version of the page or use the \"live\" option which\nwill check validity for the live version currently served by your site.\n\n\nTo learn more about the types of SXG issues we can report on, check out this\n[Help Center Article](https://support.google.com/webmasters/answer/7450883#sgx_warning_list)\non SXG issues. If you have any questions, you can ask in the\n[help community](https://support.google.com/webmasters/threads?thread_filter=(category:search_console))\nor the Google Webmasters [Twitter handle](https://twitter.com/googlesearchc).\n\n\nPosted by [Amir Rachum](https://amir.rachum.com/), Search Console Software Engineer and Jeffrey Jose, Google Search Product Manager."]]
