AMP is one of the most polemic projects from Google inside the DEV and SEO communities. Every week new information appears with data both in favour and against the project, which in most of the cases shows an incorrect picture about it.
Deciding whether to implement AMP or not can have a huge impact for some businesses, so it’s crucial to know what the pros and cons are and if they are completely true.
Most of that data is usually flawed, meaningless or half-true, so in this post you will found a compilation of some of the most common assumptions, and what they hide.
Important note! This is not an article in favour nor against AMP. It’s just an analysis of some assumptions, both favourable and not so favourable about it.
Tabla de contenidos
- 1 example.com is getting XX% of its Google mobile traffic from AMP
- 2 Bounce rate on AMP pages is really high
- 3 AMP pages rank higher on Google’s Mobile SERP results
- 4 CTR on SERPs is higher for AMP results
- 5 Google will steal my SEO traffic
- 6 So, should you implement AMP on your website?
- 7 My take about AMP
example.com is getting XX% of its Google mobile traffic from AMP
This specific news piece refers to The Guardian, but you can find similar metrics from other websites.
The Guardian was one of the first news website to implement AMP, working side by side with Google, months before the project was publicly launched. They went “all-in” with AMP, creating an AMP version of all their articles (retroactively)
What does this mean? That a huge percentage of their URLs, have an AMP version. Why not all? Well, because AMP was designed in the first place for news articles, not for any kind of page. Some examples of pages in The Guardian that do not have an AMP version are:
- Their homepage: http://www.theguardian.com/
- Their categories / topics: http://www.theguardian.com/football, http://www.theguardian.com/books/stieg-larsson
- Interactive / more complex pieces of content: http://www.theguardian.com/world/ng-interactive/2017/may/07/french-presidential-election-results-latest
When implementing AMP on your site, Google (on mobile) will replace your normal URLs by your AMP URLs on their SERPs, sending traffic to your AMP pages instead of to your normal pages.
So, saying that “The Guardian is getting 60 percent of its Google mobile traffic from AMP”, just means that they implemented AMP correctly and that results are what you would expect, if you knew the % of mobile SEO traffic those pages had before AMP.
If you implement AMP on 100% of your pages, those pages will eventually get 100% of Google Mobile traffic, saying nothing about the quality or success of using AMP. It’s just part of the implementation. You could be getting less SEO traffic than before, but having 100% of it landing on AMP pages anyway.
It doesn’t tell if the Guardian is getting more or less traffic from Google Mobile, as the traffic has stopped landing on the normal pages, and started landing on the AMP pages. And even if Google Mobile traffic grew post-AMP implementation, it could be from a lot of factors and it will be difficult to know the exact reason (specially in huge sites like The Guardian, where traffic varies heavily depending on the news)
The article goes on saying: “AMP has gradually been taking over the Guardian’s mobile traffic; today, 60 percent of its Google mobile traffic is AMP, well above the 10 to 15 percent that publishers have been getting from AMP“. Which is again, meaningless, as the % of traffic AMP pages get from Google mobile depends on your AMP implementation and not from your SEO performance itself.
Bounce rate on AMP pages is really high
If you search inside forums and blogs, you can find lots of comments about this, stating lots of reasons why the bounce rate of our AMP is so high. Those reasons can indeed be affecting, but the main cause of that high bounce rate is that it is probably wrongly calculated.
As I explained here, the way AMP works causes an inflation of sessions and users on your Analytics tool, which then causes an incorrectly calculated high bounce rate.
This is a well-known problem by Google, which is tricky to solve, and although they are working on it and have already improved it, the problem still remains for the main use scenario (people reaching your AMP pages through Google search on mobile).
So, if you want to analyse the behaviour of your AMP pages, don’t count on the bounce rate metric unless you have implemented any kind of solution to solve it.
AMP pages rank higher on Google’s Mobile SERP results
Here, we need to consider two different scenarios:
- The “Top Stories” box results, which appear for some queries in the SERPs
- The organic results.
Top Stories box results (AMP article rich results)
This box of results is not new, nor created because of AMP. Since Google launched “Universal”, they try to show different types of results depending on the query.
That way, if you for example search for “Despacito”, the first result is a giant youtube video with the song:
And if Google consider that the query is somehow related to “news” it will also show a box with news results:
Which in mobile now highlights AMP results:
Although sometimes there are non-AMP results inside:
That box was initially exclusive for white-listed publishers (you could opt-in if you comply with the requisites), and later on started to show, sometimes, results from websites outside that list (even tweets and youtube videos).
With the launch AMP, Google “forced” publishers to adopt its platform in order to appear in that box in mobile. Although sometimes non-AMP results appear there, it’s not the norm.
So, when some people say that AMP is a ranking factor because of this box: it’s not. Or at least not a new one, or not because of AMP. The news box existed before AMP, and even if you implement AMP on your pages, your results won’t probably appear there, as most of them are from big publishers.
The reason Google uses to justify favouring AMP in the Top Stories box is that “AMP is the format that currently delivers the best possible user experience on the mobile web. That is because AMP allows for consistent speed, caching, pre-rendering, and enables swiping between full-length pages. This is a big deal for topics where there isn’t “that one best result” that a user might want to look at.” (source: Malte Ubl, Creator and Tech Lead of AMP, on HN).
You can read my take on this at the end of this post.
Organic results (AMP non-rich results)
For the organic, “normal” results, Google says AMP is not a ranking factor yet. Believe it or not, there is no data (at least I couldn’t find it) which demonstrate the opposite.
So right now, if you implement AMP on your pages, and you rank 2nd for a query, with your “normal” URL, as soon as Google detects the AMP version of that URL, the AMP result will appear instead, in the same 2nd position.
So what about this data? It says it’s clear that rankings and CTR are better on AMP pages:
It seems better, but that data is comparing different things.
The only way to try (you cannot be 100% sure as you cannot A/B test AMP results) to get real stats about rankings and CTR for AMP vs non-AMP results would be:
- To have several URLs rankings for several keywords, really stable for a long time (in terms of traffic and CTR)
- Create the AMP version for some of those URLs, leaving some of them without AMP as a control group
- Check if Google index the AMP versions properly
- Monitor mobile rankings for both AMP and non-AMP URLs after they get indexed
- Monitor CTR for both in Search Console
That way, you can see if a keyword for which you have been ranking in the same position for long time, with a stable CTR, gets any improvement right after implementing AMP. Of course there is the possibility that lots of other factors influence this, so you can’t be 100% sure.
If you just compare, in Search Console, the performance of your AMP pages with your non-AMP pages, you are probably doing it wrong.
These are the stats, from Search Console, for my travel blog RandomTrip.es, both for Mobile AMP pages and Mobile non-AMP pages.
So with these stats, AMP Mobile pages win: better CTR (8.82% vs 5.01%) and better average position (7 vs 7.7), right?
Well, not exactly. These are not stats about the same pages with different output, they are about different pages (pages that have AMP version always appear with their AMP version on mobile), so the comparison makes no sense. What we are comparing here is different kind of pages (the homepage and categories/tags vs posts), which may have, by themselves, different SEO performance for lots of different reasons.
CTR on SERPs is higher for AMP results
This can be true, under the assumption that users have learned that the AMP symbol means pages load faster and so they tend to click more on those kinds of results, but it’s unlikely (ask any of your non-tech friends what they think it is)
And, it’s not demonstrated with data. It can be true, but it also cannot, so if you want to use it as an argument to implement AMP, you will need to test it yourself or get real data from someone who already tested it.
Google will steal my SEO traffic
Source: http://www.alexkras.com/google-may-be-stealing-your-mobile-traffic/ (the author, Alex Kras, rectified about the headline and says at the beginning of the article that it is inaccurate)
This article was one of the first polemic ones that took of in communities like Hacker News against AMP, and it is an interesting read as it reflects how little people know/understand about AMP (even inside the dev community).
So, will google steal your SEO traffic if you implement AMP? Not exactly
AMP is a complex project, you can learn more about how it works here. Basically, it makes your pages load fast thanks to these two main factors:
- There are a lot of restrictions regarding CSS, JS and Ads, so they force you to create pages without all the “stuff” that makes your “normal” pages slow and that you are not willing to take out of them. So your AMP pages will (or at least should) be faster than your “normal” mobile pages.
- Instead of sending the visitors to your AMP pages, Google is actually caching your AMP pages on its servers and serving them itself. This assures some server side optimizations their infrastructure already have.
Point 2 is the controversial here: you are no longer serving these pages, Google does, and that’s why it seems Google is stealing your traffic.
In reality, traffic will still count on your web analytics tools, and you still control the content, menus, ads and links you are showing there (with some problems carried along as I demonstrate in this post)
BUT, users don’t completely leave Google when they click on AMP results, they can swipe from one news piece to another between different websites when using the “Top Stories” box, and the URL showed on the user’s browser is a Google one, not yours.
So the traffic is counted as yours, but it’s Google serving it, and it’s Google the one controlling the environment in which the users are seeing your content.
Another complaint the author of the article (Alex Kras) does, is that AMP is not optional for the user. Contrary to what happens with App indexing, where if you have the app from the result’s domain installed and Google know that you can check the content there, it will direct you there, but offers another link to just check the content on the website.
So, should you implement AMP on your website?
Well, as with every business decision, and as we Galicians always say: it depends!
You need to evaluate the pros and cons, and take extra care with the metrics you use to evaluate your decision.
If you rely on Google News traffic, then you probably are already using AMP. If not, you are at disadvantage as most of the results in the “Top Stories” box are AMP ones.
Right now it is not demonstrated that using AMP will give you a rank nor a CTR boost, so if your mobile website is fast enough, you can probably live without AMP.
If Google starts giving AMP results (because they want to promote the technology or because they give speed more weight in their new mobile index), then you need to take that into account as well.
If your mobile website is slow, fix it! Whether you implement AMP or not, speed should be a priority, specially on mobile.
My take about AMP
My take here is that Google is not trying to fool websites and business with AMP and that the negative aspects of how AMP works right now are more of consequences / limitations of the platform than their goal itself.
In general, if you implement AMP on your website you will see your pages loading faster, which is a good thing. Also, the adoption of AMP is bringing to the table some best practices in terms of web performance that you should follow on your own website too, and not only on the AMP version.
On the other side, I hope Google stop using its power to make websites to adopt their whole ecosystem. It should be possible to implement AMP without using Google’s cache, getting the “AMP” label anyway.
Actually, as probably 99,9% of the users don’t even know what “AMP” means, they should test other kind of labels if they want to highlight “mobile optimized” results, and it should rely on the speed and UX of the destination page, not on AMP.
Do you have data to prove any of the assumptions? If so, let me know!