Google AMP errors widely reported by webmasters and publishers

Many webmasters, developers and publishers are complaining about AMP issues in Google mobile search and within the Google Search Console. Some are seeing Google show their stories in the “Top Stories” section with and without the AMP icon within minutes of each other. Others are noticing significant spikes in AMP errors reported within Google Search Console. Either way, it seems to be a widespread issue and John Mueller, a Google webmaster trends analyst said he is investigating the reports.

What is the issue? Besides Google sending notifications via Google Search Console that the site has issues with AMP all of a sudden, some publishers are seeing Google show their AMP content in Top Stories in Google mobile and then minutes later, the AMP version disappears. It will eventually come back later. This is even when the URL Inspection Tool shows the AMP page is valid and working fine.

Screenshots: Here is the same content in Google mobile search both showing the AMP logo for the page and not showing the AMP logo for the page:

Here are screenshots showing the Search Console reports around this issue:

@JohnMu Search Console AMP Crawl Errors have spiked on all our domains the last three days. Other webmasters are reporting the issue as well. Live versions of reported pages are all valid/up to standard (but no longer indexed). Any ideas? Bug? https://t.co/azAyyL8OSh pic.twitter.com/C7wSnvKa8U

— Ben Kendrick (@benkendrick) January 28, 2019

Google is investigating. Google’s John Mueller said on Twitter “the team here is looking into this.”

Thanks — the team here is looking into this.

— John 🧀 … 🧀 (@JohnMu) January 28, 2019

Why it matters. Many developers and publishers who see these AMP issues will run to make changes to their sites. In this case, it probably makes sense to wait, not make any changes and see what Google says. We will continue to monitor the issue and update this story with Google’s recommendations. But for now, we would recommend you wait and not make changes based on these specific AMP errors.

Postscript: John Mueller from Google confirmed on Twitter that this is a Google issue and they will resolve it on their end. There is nothing webmasters need to do to fix this specific issue on their end. Here is the tweet:

https://twitter.com/JohnMu/status/1090196899146186752