The AMP enhancement report and the URL inspection tool can now show you issues with your signed exchanges.? AMP增強報告和URL檢查工具現在可以向您顯示已簽名交換的問題。

Google?announced?that Search Console has been upgraded to support reporting on issues around AMP and signed exchanges. Signed exchanges (SXG) can be used with AMP to show?your real publisher URL and not the Google AMP cache URL?when serving your AMP articles.?谷歌宣布已升級Search Console，以支持有關AMP和已簽署交易所的問題的報告。提供AMP文章時，簽名交易所（SXG）可以與AMP一起使用以顯示您的真實發布者URL，而不是Google AMP緩存URL。

Google’s URL inspection tool and the AMP enhancement report within Search Console can both now report on issues around signed exchanges and AMP. With these updates, “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,” Google said.?Google的URL檢查工具和Search Console中的AMP增強報告現在都可以報告已簽名交易和AMP的問題。有了這些更新，“為其AMP頁面實施SXG的站點將能夠了解是否存在任何問題阻止Google使用Google AMP Cache來為其頁面提供SXG版本的頁面，”谷歌表示。

URL inspection tool.?The URL inspection tool can be run on a specific URL that you want to debug. This will help you “find if any SXG related issues appear on the AMP section of the analysis,” Google said. You can also 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.??URL檢查工具。URL檢查工具可以在要調試的特定URL上運行。谷歌表示，這將幫助您“確定分析中的AMP部分是否出現任何與SXG相關的問題”。您還可以診斷影響頁面索引版本的問題，或使用“實時”選項，該選項將檢查您站點當前提供的實時版本的有效性。

AMP enhancement report.?The AMP enhancement report has also been upgraded to show signed exchange issues. This is not as “realtime” as the URL Inspection tool, but it will highlight issues it finds without you having to manually run a URL in the URL inspection tool.? AMP增強報告。AMP增強報告也已升級，以顯示已簽名的交換問題。這不像URL檢查工具那樣“實時”，但是它將突出顯示發現的問題，而無需您在URL檢查工具中手動運行URL。

Google will also send emails to alert you of new issues as Google detects them.??當Google檢測到新問題時，Google還將發送電子郵件提醒您。

List of issues.?Here is the list of issues Google published in its?help document:?問題清單。 以下是Google在其幫助文檔中發布的問題列表：

l?The signed exchange is invalid?簽名交換無效

l?The signed exchange payload has a parse error?簽名的交換負載有解析錯誤

l?The header ‘header_name’ for the signed exchange payload has an invalid value?簽名的交換有效負載的標頭“ header_name”具有無效值

l?The mandatory header ‘header_name’ for the signed exchange payload is missing?缺少簽名的交換有效負載的必需標頭“ header_name”

l?The signature header for the signed exchange cannot be parsed?無法解析已簽名交換的簽名頭

l?The parameter ‘parameter_name’ in the signed exchange signature header is invalid?簽名的交換簽名頭中的參數“ parameter_name”無效

l?The dates for the signed exchange are invalid?簽署交換的日期無效

l?The certificate chain referenced by the signed exchange ‘cert-url’ cannot be parsed?無法解析已簽名交易所“ cert-url”所引用的證書鏈

l?The certificate chain referenced by ‘cert-url’ is invalid for the signed exchange?“ cert-url”引用的證書鏈對已簽名的交換無效

l?The signed exchange cannot be parsed?無法解析簽名的交換

l?The URL for the inner payload does not match the request URL for the signed exchange?內部有效負載的URL與簽名交換的請求URL不匹配

l?The header ‘header_name’ for the signed exchange HTTP response has an invalid value?簽名的交換HTTP響應的標頭“ header_name”具有無效的值

Why we care.?Here is another set of debugging tools from Google and the Search Console team. If you are using signed exchanges and AMP, this can come in handy in figuring out any issues you may have with those pages and URLs.??我們為什么在乎。 這是Google和Search Console團隊提供的另一套調試工具。如果您使用的是已簽名的交易所和AMP，這對于找出這些頁面和URL可能存在的任何問題非常有用。

來源：Barry Schwartz