“The AMP Project is an open-source initiative aiming to make the web better for all. The project enables the creation of websites and ads that are consistently fast, beautiful and high-performing across devices and distribution platforms.” (AMPProject.org)
To simplify that statement, the AMP Project is Google’s way of facilitating the creation of really fast-loading mobile pages, ones pared down to the bare minimum for maximum speed of delivery. The need for this is fueled by the fact that mobile users have surpassed desktop users at a time when multiple types of media are slowing down websites. Plus, content management systems—which are slow by nature—have taken over the web, which isn’t conducive to efficient mobile browsing. Now that U.S. consumers are spending an average of five hours per day on mobile devices, solutions clearly needed to be devised. Thus, the AMP Project.
Debut of Accelerated Mobile Pages (AMP)
This development is fairly new, an open source collaboration between Google and Twitter that was officially announced on October 7, 2015, only five months after Facebook rolled out Instant Articles. To quote Facebook on Instant Articles rollout day (May 12, 2015), “As more people get their news on mobile devices, we want to make the experience faster and richer on Facebook. People share a lot of articles on Facebook, particularly on our mobile app. To date, however, these stories take an average of eight seconds to load, by far the slowest single content type on Facebook. Instant Articles makes the reading experience as much as ten times faster than standard mobile web articles.”
No matter where the concept of fast-loading times existed on Google’s list of priorities in May 2015, competition from Facebook surely caused this project to become more urgent. AMP launched on February 24, 2016 and, since that time, literally billions of AMP pages have been published. An average AMP page boasts a speed increase of about 400% over a typical mobile page—and, yet, it needs ten times less bandwidth to load.
Here is what Malte Ubl, the tech lead of the AMP Project, said about AMP in a presentation given in October 2015:
Importance of Speed
As digital media giants race to facilitate lightning fast online content consumption, we feel compelled to refer to the now-ubiquitous Microsoft Corp study that, in 2015, shared how the average human attention span had dropped to below that of a goldfish. This cold-water fish, commonly found in aquariums, registers an attention span of nine seconds, whereas the human span had dropped to an average of eight, “highlighting the effects of an increasingly digitalized lifestyle on the brain.” Looking back to when the mobile revolution occurred (in 2000), human attention span was about 12 seconds, so it had dropped by one third in 15 short years. Thus, the AMP Project.
How Does AMP Work – and Is It Really Working?
Answering the first part of the question first, the answer is “yes.” More specifically, here are just three examples of boosted success on news sites:
- Wired.com has experienced a 25% increase in its click-through rate (CTR) from search results pages
- Gizmodo.com has benefitted from a 50% increase in impressions
- Slate.com has witnessed a 44% increase in monthly unique visitors
As for the number of AMP documents: in September 2016, there were 600 million. As of May 18, 2017? Two billion! As of October 19, 2017? FOUR billion from more than 25 million different domains. At this point in time, more than 400 people have contributed to this open source code.
Elements of AMP, broadly speaking, are three-fold:
- Restricted HTML: certain HTML tags are replaced with AMP HTML tags
- Google AMP Cache: this content delivery network uses HTTP 2.0 for maximum efficiency
Taking a closer look at AMP HTML, you can find more specifics on how to create this type of page from the AMP Project site. To ensure that you can take advantage of all AMP features to their fullest, you need to use HTTPS protocol (rather than HTTP). You can find even more information about creating an AMP page and relevant structured data at Developers.Google.com.
DAGMAR’s Take on AMP: Good, Bad and Ugly
Like any new development, there are positives and negatives.
Looking first at the up side of AMP, we agree: pages are fast. Really fast. From an SEO perspective, there does seem to be a ranking boost for AMP-validated pages on mobile phones, especially when connected to news stories (more about rankings later).
Then there is the mobile first index. This concept was announced by Google on November 4, 2016, and was originally projected to become a reality some time in 2017. It is now projected to roll out in 2018. When the index finally does become a reality, it will be a time of significant change for websites, their rankings, and for the SEOs and webmasters who manage those sites. In June 2017 at SMX Advanced, Google webmaster trends analyst Gary Illyes said the mobile first index debut was “probably many quarters away,” adding that Google plans to be very proactive about communicating with webmasters about this index. Stay tuned!
Since we’re talking about good news, here’s the good part of this news. You’ve got time to get your mobile site up to speed before this significant change takes place, and Google is promising proactive support. The bad part? Time flies and you will need plenty of time to get your site AMP-validated. So, if you plan to AMP up your pages, don’t procrastinate too long. (And, we don’t really know how Google is defining “proactive” support!)
Finally, in the good news category: because AMP uses open source protocol, it is continuing to be updated, and updates are likely to have a net positive effect.
Although AMP is achieving its goal for speed, how readily will the average webmaster participate? These pages have only been included in organic search results for a little more than a year (since September 20, 2016), so all is still unfolding.
As mentioned, AMP pages require validation, so you’ll need to monitor your Google Search Console for validation problems. If you have validation issues, you will need to head to the AMP Project validator tool where you must enter the AMP URL (with “param hs_amp=true”) to receive more information about what the validation problem is. Typically, there are HMTL issues within the content itself that need to be addressed.
Here are more validation specifics:
Other challenges associated with AMP include:
- Lead generation forms are hard to implement
- Most AMP documents permit only one advertisement-related tag, one that isn’t necessarily easy to implement
- Google’s cache can cause problems when people share or link to the cached version of a page, rather than to your actual website
- Google has, in effect, gained control of how you display content for mobile devices
- Switching to AMP HTML in your source code isn’t easy, requiring an expert
- Although mobile usage is clearly increasing and is now dominant, companies will still need to consider desktop users and their needs
- While AMP pages are valuable for news articles, they aren’t for white papers, e-books, podcasts, videos, and other more in-depth forms of content
As a subset of “The Bad,” AMP pages are also ugly—as in, really ugly. By stripping down the HTML, the styling of these pages and the webmaster’s ability to incorporate branding into the pages have gone back in time. Yes, we know that nostalgia is in, with people buying retro cell phones and the like but: no branding + simple styles = UGLY. Note that increasing numbers of templates are being created for AMP. So, again, stay tuned.
How to Implement AMP
If you’re ready to implement AMP, how you do so depends upon your site. If you have a custom website, you pretty much need to hire a developer. If you have a content management system, you can carefully read all your documentation and install the AMP plugins yourself. Or, you can hire a developer. No matter what you decide, it’s crucial that you validate your pages and create a separate AMP sitemap to speed up indexing. If you’ve got a WordPress site, you can find plenty of information and options for AMP with pages and posts at AmpForWP.com. Extensions are required for full functionality and options are pricey with support likely to be sketchy. WordPress.org offers a simple and free plugin, but AMP is supported for posts only (not pages). The Yoast Glue plugin is also needed for the AMP plugin to work well—and, even then, the setup is buggy.
AMP and Organic Search Results
Google has said, repeatedly, that AMP in and of itself is not a ranking signal. Here is where John Mueller said so on January 25, 2017. However, in the video found on that page, Mueller states that, if the AMP pages are your primary (canonical) version, then these are the pages that Google will judge when making ranking decisions. And, since site speed has been a ranking factor for several years, the speed of pages that are successfully AMP-ed will play a role in ranking.
Plus, when your site has faster-loading pages, this affects the user experience, which is likely to continue to play an increasingly larger role in organic SEO rankings.
Furthermore, at least for now, AMP pages are seen on the news carousel, found above-the-fold and pushing down standard organic results. Pages in the carousel are therefore naturally going to receive more impressions and clicks, with a lower bounce rate as the more impatient searchers receive more instant gratification.
AMP pages making the carousel will benefit even further with clicks when a compelling image and headline are included. And, assuming that your content is what searchers want and need, this should boost dwell time and then conversion rates (even AMP won’t help, of course, if your content isn’t what consumers want to consume!).
Although the value of AMP has first been harnessed by publishers, in October 2017, a case study for a top shoe retailer was published, showing how local pages are benefiting from AMP. When reviewing period-over-period data:
- session traffic increased for that retailer by 32 percent
- year-over-year increased by 45 percent
- customer actions increased by 9.5 percent after the 2017 launch
- customer actions increased by 21.3 percent when comparing 2016 data to 2017
AMP’s potential impact widened in another way when, at the March 2017 AMP Conference, Google announced that this technology will be available over additional search engines, including Baidu, Sogou, and Yahoo Japan. Two months later, on May 23, 107, Google shared that AMP was now available via AdWords in display and search ads alike.
AMP and AdWords
In May 2017, Google began beta testing the concept of sending PPC traffic to AMP landing pages. In September, it was anticipated that all advertisers using search text ads would have the ability to direct mobile search ads to AMP landing pages. Initially, caching would only be available through Chrome on Android devices, although more widespread options and support is said to be in the works.
Early positive results include:
- Wego.com, with a 95 percent increase in partner conversion rates, along with a 31 percent drop rate in bounce rates
- Greenweez.com, with an 80 percent increase in mobile conversions, with a 66 percent lower mobile CPA
Developer resources for AdWords can be found here.
Sense of Urgency
A significant percentage of companies are clearly prioritizing AMP, given that there are now four billion pages using AMP. But, the fact that the mobile first index is still scheduled for “someday” rather than for a specific upcoming date probably means that numerous other companies are pushing this line item down on their priority lists—and may continue to do so until the consequences that will occur with a mobile-first search engine index loom. That’s the role that human nature plays in adopting any new technology, and it’s no different with AMP. Google’s own sense of urgency may ramp up if competition from other fast-loading content systems (such as Facebook Instant Articles) becomes more significant.
Latest posts by Chris Gregory (see all)
- Google Analytics Setup Best Practices - February 8, 2021
- Pest Control Marketing Tips: How to Improve Your Website’s Page Speed - July 22, 2020
- What To Know About Google’s New Core Update - May 12, 2020