In addition AMP has penetrated other platforms, like Facebook, Twitter and Pinterest.
The cat is out of the bag, and it will not be easy to put it back.
Yup, now that those damn users have gotten a taste of speed & low data usage, it's gonna be hard to drag them back to how it used to be. We had a good thing going, and they didn't know any better.
AMP isn't going anywhere so don't get your hopes up. But, by all means I encourage you to initiate a lawsuit if only to see you fleeced by a lawyer for your litigious attitude.
Also, the article you linked to is so full of inaccuracies that it's impossible to take it seriously.
This is a major ranking factor, in some situations moving sites that would be on page 13! to the #1 spot in search. In other cases, the effect is less visible.
That is what keeps people from not implementing AMP.
And you get this ranking benefit not for using AMP, or for a certain performance, but it is given to everyone that uses Google’s AMP version, from Google’s CDN, with Google’s tracking solutions. If I want to run AMP from my own CDN, I can’t do it, and if I want to avoid Google’s cache, because I have my own CDN, I also don’t get the ranking boost.
Got a source for that? I always heard that the criteria for the carousel was AMP-compatibility, not being hosted on Google's CDN.
Currently, Google serves AMP by serving all AMP search results from its own cache, which allows Google to add features such as the header bar, or the swiping between carousel elements. This doesn’t work if the pages are from different origins.
EDIT: I found some sources:
> contain a <script async src="https://cdn.ampproject.org/v0.js"></script> tag inside their head tag.
https://www.ampproject.org/docs/reference/spec#required-mark...
Which prevents self-hosting the JS
And https://developers.google.com/amp/cache/faq
> Q: Can I stop content from being cached?
> A: No. By using the AMP format, content producers are making the content in AMP files available to be cached by third parties. For example, Google products use the Google AMP Cache to serve AMP content as fast as possible.
How different is this from common HTML caching done all over the web? And that's about using the Google AMP Cache, not about using AMP.
And you still didn't provide a source about "having to use Google's CDN".
Essentially: do AMP pages hosted on Cloudflare's cache do not get into Google Search carrousel?
Link here:
https://blog.branch.io/google-accelerated-mobile-pages-amp-a...
> Anyone can use a CDN to set up and run an AMP cache, but only content in Google’s cache (which Google has stated can be used without restriction and at no cost) is currently getting preferred search results treatment
But the whole point is kinda moot because AMP requires that your assets be "cacheable", which means google will come along and cache them, and the search results will use the google-cached version.
So sure, another CDN could cache your stuff, but nobody clicking through a google search result will ever hit it.
> And you still didn't provide a source about "having to use Google's CDN".
This is the issue I meant with Google’s CDN/Cache.
If a user clicks a link to an AMP page in Google search, they are not redirected to your page. They ALWAYS get the cached version from Google, and Google modifies your page by adding UI, and changing other functionality (for example, the left/right swipe gestures are changed to navigate to other Google search results).
You can not opt out of this while still appearing in the carousel.
I can only point to what the Google AMP documentation says, where they state that you have to allow your site to be served by Google AMP Cache to count as an AMP site: https://developers.google.com/amp/cache/faq and https://developers.google.com/search/docs/guides/about-amp
Maybe they don't follow their own docs and there are sites out there not cached in the Google AMP Cache that still get placed in the carousel. I have no way to prove that without being able to test every single possible search term (plus all the other variables like location which affect the results).
To quote the AMP specs, a page is only eligible for showing up as AMP in search if it
> contains a <script async src="https://cdn.ampproject.org/v0.js"></script> tag inside their head tag.
and
> is allowed to be cached in the Google AMP cache