Meanwhile, "monetization benefits are less decisive and pending further analysis of our current implementation."
Publishers find a number of benefits to AMP -- revealed frankly in the article -- but the only reason they use it in the first place is because Google is where a lot of those eyeballs originate anyway. If Some Obscure Search Engine with ~1% marketshare reworked their mobile page to prioritize pages that adhere to some criteria of limitations, used an iframe to frame the content so that it loads inside their page, and threw in a free CDN to sweeten the deal, who'd retool their publishing infrastructure -- as excellently detailed in this post -- to publish in this format?
AMP enables an alliance of convenience between one of the top sources of traffic (Google), and the authors of long-form textual content reliant on advertising revenue. To the AMP team's credit, it does so by aligning closer than its competitors to how the web actually works, despite the Google-Search-on-Mobile page then acting as a captive newsreader.
Most user criticism of AMP is focused on Google-Search-on-Mobile stealth-morphing into a captive newsreader, while most publisher criticism of AMP is from sites outside of its target market trying out the tech and alarmed at the lack of traffic reaching their server, forgetting that offloading traffic at high volumes is a good thing. AMP isn't for people who are upset that Google is stealing your content; it's for publishers who want Google to expose their content to wide audience and hope to generate revenue through means that correlate to that reach.
> AMP enables an alliance of convenience between ... Google ... and the authors ...
The third party in that alliance is the end user who was a decent mobile browsing experience. As one, I absolutely love AMP. It guarantees that the page I am about to click on is not going to be horrible. So much so that these days, I actively seek out pages with AMP icon in my search results.
As long as they insist on using their CDN then this cannot be avoided.
And what freedoms will be lost when we are all required to run AMP website?
>> in this case it was clearly a net positive
Not so fast. When I was there, the earlier experiment was that its was a "mixed" success. This post also suggests strongly to me that that hasn't changed too much ("Monetization benefits are less decisive and pending further analysis").
For many publishers it comes down to they cant get slightly more traffic with AMP (because of the AMP carousel in Search results) at a lower CPM which is a positive. However, as more publishers come on board that gets tricky all over again and risk of it becoming another race to the bottom of lower CPMs.
So ranking #2 in search results on average correlated with an increase in click through rate. Oh, btw, just happens that you gotta use AMP to get the SERP gain.
And, like many engineering blogs about employing Google products, seems like it might've been suggested by a Google marketing team.
There's a lot of conspiracy theories and misunderstanding about how AMP works in the community. AMP is by no means perfect, but its dangers are greatly exaggerated. If you don't trust Google's CDN, no one is forcing you to use Google. The benefits for non-tech users (e.g. my cousin in a 3rd world country with a 2G connection) are there and are clear.
Then Google will make their next move.
This is exactly how Froogle/Google product search went.
As much as HN loves to bicker about Amp, in this case it was clearly a net positive.