如何解决:引用的AMP URL不是AMP [英] How to fix: Referenced AMP URL is not an AMP

问题描述

Search Console添加了许多参考AMP URL不是AMP"问题.

Search console added a bunch of issues with "Referenced AMP URL is not an AMP".

如果我使用 AMP测试我得到:

但是，当我签入 https://validator.ampproject.org/时，它显示:

However, when I check in https://validator.ampproject.org/ it shows:

以下是Search Console认为无效的AMP页面的一些URL列表:

Here is a list of some of the URLs that the Search Console says are not valid AMP pages:

• https://www.beek.io/amp/frases/satan -una-autobiografia
• https://www.beek.io/amp/frases/mi-isla

• https://www.beek.io/amp/frases/satan-una-autobiografia
• https://www.beek.io/amp/frases/mi-isla
• https://www.beek.io/amp/frases/magnus-chase-y-los-dioses-de-asgard-1-la-espada-del-tiempo

我不明白Google希望我如何解决.

I don't understand what Google expect me to fix.

推荐答案

原来，我遇到了几个问题.

It turned out that I had several issues.

首先，我需要更正AMP版本和页面标准版本之间的所有链接.

First I needed to correct all the links between the AMP version and the standard version of the pages.

此后，克雷格·斯科特(Craig Scott)正确处理了重定向问题，它违反了 Google搜索指南AMP 重定向来自台式机或平板电脑的流量.

After that, Craig Scott was right about the redirection, it was against the Google Search guidelines for AMP to redirect the traffic that came from desktop or tablet.

但是，我还有另一个与AMP上的代码没有直接关系的巨大问题.

However, I had another huge problem not directly related to the code on AMP.

我们正在使用 Prerender 来帮助抓取工具读取使用React渲染的页面内容，但返回的内容无效页面版本到AMP页面的搜寻器.

We are using Prerender to help crawlers read the content of our page rendered with React, but it returned an invalid version of the page to the crawler of the AMP pages.

要解决最后一个问题，我将AMP页面(甚至不使用自定义JS！)列入了黑名单.

To fix this last issue I blacklisted the AMP pages (that doesn't even use custom JS!) for prerender.

这篇关于如何解决:引用的AMP URL不是AMP的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！