AMP Status

What is AMP?

AMP (originally an acronym for Accelerated Mobile Pages) is an open source HTML framework developed by the AMP Open Source Project. Google launched the Accelerated Mobile Pages open-source project to ensure that mobile webpages operate at optimal speed. Using AMPs helped increase conversions for businesses in varying industries.

AMP leads to a 10% increase in website traffic with 2 times increase in time spent on page. Ecommerce websites that use AMP experience a 20% increase in sales and conversions compared to non-AMP pages.

The 3 core components of AMP

AMP HTML. The AMP HTML is essentially HTML just with some restrictions for reliable performance.Most tags in AMP HTML are regular HTML tags, however, some HTML tags are replaced with AMP-specific tags. These custom tags are called AMP HTML components and they make common tag patterns easy to implement in a performant way. AMP pages are discovered by search engines and other platforms by the HTML tag. 

AMP JavaScript (JS). The AMP JS library ensures the fast rendering of AMP HTML pages. The JS library implements all the AMP’s best performance practices such as inline CSS and font triggering, this manages resource loading and gives you the custom HTML tags to ensure a fast page rendering.

AMP Cache.The Google AMP Cache is used to serve cached AMP HTML pages. The AMP Cache is proxy-based content delivery network used for delivering all valid AMP documents. The Cache fetches AMP HTML pages, caches them, and improves page performance automatically.

To maintain maximum efficiency AMP Cache loads the document, the JS files and all images from the same origin that is using the HTTP 2.0.

AMP status report

This report helps you fix errors that prevent your AMP pages from appearing in Google Search results with AMP-specific features.

The top level view shows all AMP pages with issues found by Google on your site, grouped by issue. Click a specific issue to see issue details, including a sample list of pages affected by that issue, information about how to fix it, and a process to notify Google about your fixes.

What to look for

Ideally you should see this on the report:

• Zero AMP errors on your site (warnings are considered recommendations, not errors). If not, see Prioritize and fix issues.
• The total count of AMP pages on the report (valid + warning + error pages) should be close to the number of AMP pages on your site. If not, see Missing AMP pages.

Prioritize and fix issues

1. On the summary page, filter out the warnings and focus on the errors first. By default, issues are sorted by a combination of severity, validation state, and number of affected pages; we recommend that you address them in this default order. Fix errors caused by a common cause first (such as a bad template), then fix errors that are unique to each page.
2. See if any increase in the total error count is caused mostly by a single error: look for a corresponding spike in a single issue in the table.
3. See information below about debugging spikes and missing AMP pages.
4. Click a row in the table to see the error details page:
   • The details page includes a sample of affected URLs. The list is not always complete, because it is limited to 1,000 rows, and might not include very recently discovered instances of this error.
   • If it is a syntax error, click Learn more to get official documentation about the proper syntax.
   • Click the inspect icon to run a validity test against an affected page. This test will pinpoint all errors (not just the current issue) and provide a code explorer highlighting the errors and providing more information. It is possible that an error has been fixed in the live page but is still listed as an error because it has not yet been recrawled; if so, request validation after you have fixed all instances of this issue.
5. Fix all instances of the issue on your site, test your fix, and ensure that your fixes are live on the web.
6. Return to the issue details page and click the Validate Fix button to begin the validation process. This process is not immediate. See About validation below to understand the validation process.
7. Continue fixing errors.
8. When all errors have been fixed, remove the filter for warnings, and consider fixing the warnings. Some warnings are about missing optional structured data markup, which can enable new search features for pages with relevant content.

Understanding warnings

AMP pages with warnings are indexed and can be shown in Google Search results, but might not be shown with all possible AMP features (such as being shown in a Top Stories carousel). In other words, these pages might only be shown as plain blue link search results.

About Validation

After you fix all instances of a specific issue on your site, you can ask Google to validate your changes. If all known instances are gone, the issue is marked as fixed in the status table and dropped to the bottom of the table. Search Console tracks the validation state of the issue as a whole, as well as the state of each instance of the issue. When all instances of the issue are gone, the issue is considered fixed. (For actual states recorded, see Issue validation state and Instance validation state.)

Issue Lifetime

An issue’s lifetime extends from the first time any instance of that issue was detected on your site until 90 days after the last instance was marked as gone from your site. If ninety days pass without any recurrences, the issue is removed from the report history.

The issue’s first detected date is the first time the issue was detected during the issue’s lifetime, and does not change. 

Sharing the report

You can share issue details in the coverage or enhancement reports by clicking the Share  button on the page. This link grants access only to the current issue details page, plus any validation history pages for this issue, to anyone with the link. It does not grant access to other pages for your resource, or enable the shared user to perform any actions on your property or account. You can revoke the link at any time by disabling sharing for this page.

Exporting report data

Many reports provide an export button  to export the report data. Both chart and table data are exported. Values shown as either ~ or – in the report (not available/not a number) will be zeros in the downloaded data.