Google introduced Accelerated Mobile Pages (AMP) to the world in October 2015. Google AMP is an accessible framework that generates mobile pages which load quickly. Google AMP is an open-source initiative that allows website developers and publishers to improve the speed and, as a result, the website experience for mobile users without sacrificing any ad revenue.
Experienced publishers can usually get similar results with intensive performance optimizations. However, they often neglect doing this due to resource or time constraints. Google AMP validation allows developers and publishers to make optimizations easily without changing the primary mobile web experience of their websites. With Google AMP validation, you get the additional benefit that Google and other prominent web technology companies want you to use because it’s heavily integrated into their respective platforms.
How does Google AMP validation work?
Google AMP validation is basically a blueprint for building mobile web pages. It contains three main parts.
- AMP HTML – This stripped-down subset of HTML has some custom tags and properties. There are also many restrictions. It’s kind of like HTML on a diet. If you are acquainted with HTML in general, you should have no problem implementing AMP HTML into your mobile pages.
- AMP CDN – This is an optional content delivery network that will take your AMP pages, cache them automatically, and provide you with performance optimizations.
How will you use Google AMP validation on your website?
Multimedia needs to be dealt with in a special way. With Google AMP, images must use the custom amp-img element and have an explicit height and width. When you convert a legacy website to a Google AMP validated website, this can be a major problem if the same width and height attributes aren’t in use already. In addition, if you use animated GIFs on your site, you need to use the separate amp-anim extended component.
Like images, Google AMP provides you with a custom tag that must be used in order to embed locally hosted videos via HTML5. It’s called amp-video. For embedding YouTube videos, you will use a separate extended component called amp-youtube.
We’re not saying that these tag and extended components are difficult to use. They are not. They just require that you do some planning when you design your site. For Google and other technologies that support AMP to detect that you have an AMP version of an article, you will need to alter the original copy of your article page. The original article page has to include this tag. It’s basically a canonical tag for AMP pages:
<link rel=”amphtml” href=”http://www.example.com/blog-post/amp/”>
The AMP discovery page also makes mention of platforms that support AMP requiring Schema.org meta data to specify the content type of the page. (Currently, “article,” “recipe,” “review” and “video” are listed as page type examples on GitHub.)
Another indication is that Schema.org meta data is required to make your content eligible to make an appearance in the demo of the Google Search news carousel. So if you’re want to benefit in the future by Google’s implementation of AMP, you’ll need to get your schema right!
So, to get your pages Google AMP ready, you will need to undertake some work. It’s vitally important to make your mobile pages load quickly. Google AMP validation will only become more important as time goes on so if you can do things to get your site ready now it is well worth the effort.