Search
Clear search
Close search
Google apps
Main menu

Accelerated Mobile Pages (AMP) report

The AMP report shows a count of AMP pages either successfully indexed or with AMP-related errors encountered when Google crawled your site. Connectivity errors, broken links, and other errors are not shown in this report.  Pages with AMP errors or lacking required structured data elements will not be shown in Google search results with AMP-related features.

Open the AMP report

 

Accelerated Mobile Pages (AMP) are lightweight pages designed to load quickly on mobile devices. AMP-compliant pages use a subset of HTML with a few extensions.

What's in the report

If Google has found any AMP pages on your site it will show a chart of AMP pages successfully indexed as well as pages with AMP-specific errors.

  • To see errors by type: The landing page of the AMP report shows a list of AMP errors by error type. Click on an error type row to see which pages have that error.
  • To see all errors affecting a page:
    • ​Structured data errors: Open the page in the structured data testing tool
    • AMP errors: There are two testing tools available:
      • Online tool: An online validator. Open the AMP to test at https://validator.ampproject.org/#url=<url_to_test>
      • In-browser tool: Open the AMP in your browser with #development=1 added to the URL and the browser's debugging console open.

How to use the report

Here are recommendations on the best use of this report:

When should I use the report?

Look at it perhaps once a month, or if you receive a notification of a spike in AMP errors, or if you notice a sudden decrease in AMP impressions on the Search Analytics report, which might be caused by an error in your AMP pages. (Typically Search Console will notify you if there is a spike in AMP errors for your site.)

What should I look for?

Address your errors in this order:

  1. Critical errors. These will keep your AMP page from being displayed with AMP-specific features, such as Top Stories carousels.
  2. Non-critical "Deprecation" errors. These are warnings about deprecated tags or attributes in your pages. They are not errors now, but will become errors in the future.
  3. Search the Rich Cards report for structured data errors that affect canonical pages for your AMP pages. Specifically, look for errors in topic-specific structured data (for example, recipe, course, article descriptions): errors in the topic-specific descriptor on a canonical page can affect the experience of the associated AMP page in search results.
  4. Non-critical "Content mismatch" errors. These indicate a minor mismatch between an AMP page and its canonical page. If Google thinks that the pages are different, it might indicate a misunderstanding of the content of your page, which in turn can affect where and when your AMP page appears in search results.

AMP errors

The report includes links to learn more about each reported error type. In addition to standard AMP errors, the report can expose the following error types.

List of errors
Error Description
Content mismatch

There is a difference in content between the AMP page and its canonical web page.

The content of the AMP page and its canonical web page should be essentially the same. The text need not be identical, but the topic should be the same, and users should be able to accomplish the same tasks on both the AMP and the canonical page.

A mismatch can also occur when a robots.txt file blocks significant resources on one or the other. Open the Blocked Resources Report to see whether either page has blocked resources.

To fix:

  • Ensure that the AMP is referencing the correct canonical web page.
  • Ensure that the general content of the AMP and canonical page are the same.
  • Check that Google's view of the page is not different from the user's view of the page by using the Fetch as Google tool for both the AMP and the canonical page.

Google isn't seeing my fix!

If you've submitted a fix but the error is still being shown in the report, remember that Google crawls a page only periodically. You can wait for the scheduled regular recrawl, or you can request a recrawl using the Fetch as Google page.

Google can't find any AMP pages!

If you have published AMP pages that are not appearing in your AMP report, here are a few possible reasons:

  • Are you looking at the right property? The Search Console property must match the hosting site. A common mistake is to post AMP pages on the www site but look at the non-www site in Search Console, or to post pages on the https site but look at the http site in Search Console.
  • Have you given Google time to crawl your AMP pages? It can take a few days for Google to crawl any newly submitted or changed pages; be patient and wait a few more days to see if the pages show up.

Useful resources

  • ampproject.org - Reference and tutorials for building AMP-compliant pages, as well as information for content publishers, such as the why and when of AMP.
  • Online AMP validator - There is an online AMP validation tool at  https://validator.ampproject.org/. Use the following syntax to test a specific page:  https://validator.ampproject.org/#url=<url_to_test> For example: https://validator.ampproject.org/#url=http://www.example.com/myamp
  • Google-specific requirements for AMP pages in search results.
  • AMP language code on GitHub - Source code for the AMP project, as well as source used to generate documentation in ampproject.org.
Was this article helpful?
How can we improve it?