This article is also available in:
Accelerated Mobile Pages (AMP) is flexible technology for creating fast websites and web ads with cross-device and cross-platform optimization. It's relatively new and interesting technology.

AMP is designed to naturally stick to existing web structure and code. Major advantage of AMP pages is extremely fast loading. AMP Checker will help you to validate AMP implementation and AMP HTML.

Input data

To input data, a user uses the URL Miners section, where he imports URL dataset using one of the import methods.

Not sure how this works? Begin with article How to import data for processing.



Selecting miner and collecting data

In the miner selection section click on the AMP Checker miner which is used for checking the Accelerated Mobile Pages implementation.



Then, a user clicks on Get data, which will take him to the data processing section. Depending on the data volume, its processing will be done in the background and once completed, emailed to the user.



Miner output

The output is going to be a table with several columns which will contain info on ana AMP status.

Example of output report

Column description

Input: URL for which that data was collected
Status code: Input URL status code
AMP: Information if AMP markup was found on the page
rel=amphtml: AMP URL information
Valid: Information if AMP markup is valid
Schema.org: Found entities of Strutured Data markup
Canonical URL: Canonical URL for inputed URL

Attachment to a project

A completed report can be attached to a previously created project.

Output analysis

In column AMP focus on rows that don't contain yes. Fix all errors and run another check. Warning! Pages contaning only rel=amphtml will have value "no". This is fine because AMP markup should not be there but on the rel=amphtml page.

In colums rel=amphtml and Canonical URL focus on rows that contain other than expected URL. Both columns must contain valid ULRs. Pay attention to these data and run multiple check to be sure everything is OK.

In column Valid focus on rows that don't contain yes. Fix all errors and run another check.

Tips on how to use it in practice

We recommend inputting mainly URL that return status code 200. AMP HTML errors can be debugged before implementation in tool The AMP Validator. For instant checks you can use Chrome plugin AMP Validator.

Conclusion

AMP is interesting technology worthy of some exploration. It's mostly used by web publishers. But it's slowly penetrating also e-commerce market. Nevertheless you should consult your specialist before deciding to implement AMP. It's still niche technology and it doesn't have to be the right thing for you.

AMP should be validated after first implementation and after web modifications that can affect AMP HTML or rel links. For monitoring errors continuously you can use report AMP report in new Google Search Console.
Was this article helpful?
Thank you!