Accelerated Mobile Pages (AMP) report

New Search Console has an upgraded experience for this report. Try out the AMP Status report in the new Search Console.

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<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

In addition to standard AMP errors, the report can expose the following additional error types.

Google-specific AMP errors
Error Description
Content mismatch: Missing embedded video The canonical web page has an embedded video that is missing in the AMP version. It is usually best to include all the same important content resources in your AMP version as in the canonical web page. Note that the video is detected by URL; if you have two different URLs pointing to the same video, you will see this warning.
Image size smaller than recommended size The structured data in the AMP refers to an image that is smaller than our recommended size. This may prevent the page from appearing with all AMP-related features on Google. To fix, use a larger image according to our guidelines.
AMP page domain mismatch The AMP page is hosted on a different domain than its canonical version. This can be confusing to mobile searchers who see one URL domain in search results and a different one when they open the page in the AMP reader. (Does not affect page indexing or ranking.)
URL not found (404) The AMP URL requested could not be found. Learn more about 404 pages.
Server error (5XX) Unspecified 5XX server error when requesting the AMP page. Learn more about server errors.
Blocked by robots.txt The requested AMP URL was blocked by a robots.txt rule.
Crawl issue Unspecified crawling error for the AMP page. Use the URL Inspection tool on your AMP URL to troubleshoot the problem. 
Referenced AMP URL is not an AMP A canonical page references an AMP that is not, in fact, an AMP page. Learn how a non-AMP page should reference an AMP page.
Referenced AMP URL is self-canonical AMP The canonical page points to a stand-alone AMP. You cannot reference a stand-alone AMP as the AMP version of a page. Learn how to reference an AMP from a non-AMP page.
URL marked 'noindex' AMP is blocked by a 'noindex' directive. Google cannot index a page that is blocked by noindex; either remove the noindex directive, or remove the reference to the blocked page.
'unavailable_after' date for this page has expired AMP page has an "unavailable_after" meta tag or directive that has already passed, indicating that it should no longer be served. You should either update the tag to a future date, or remove the tag.
Canonical points to invalid URL A canonical page references an AMP version using an invalidly formatted URL. Learn how to properly reference an AMP version.
amp-story canonical error

A page incorrectly references an amp-story page as its AMP version. This is not allowed because an amp-story page is, by definition, self-canonical: it must point to itself with a <rel="canonical"> tag, and cannot serve as an AMP version of another 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

  • - 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 Use the following syntax to test a specific page:<url_to_test> For example:
  • 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
Was this article helpful?
How can we improve it?