When power is too concentrated in one area, its never a good sign for the common good.
The speed improvements and mobile friendliness should be the only criteria that the Google ranking engine should use for boosting the SERP rankings of these articles using it, not simply the fact they use AMP. But objectively measuring the quality of these page vs other unoptimized sites - which I hope is currently what Google is doing. That way there is nothing monopolistic about it.
Considering how awful most news sites are JS/ad-wise Google is attempting to solve a problem the publishers themselves created. Sites like Forbes are notorious for loading mb's of ads and they have that ridiculous quotes splash page. It also does away with annoying pop up modals news sites love to use.
So if these sites rankings are getting hurt because of their failure to offer good caching, image optimization, reducing the size of JS assets, etc, etc, to offer a competitive experience with AMP pages then I see nothing wrong with that. The competition will be good for users.
As long as publishers are voluntarily using this because it improves their UX then I'm fine with it.
Ideally in the long run this is just a stop gag until these publishers learn how to optimize their own sites. Then they can move off the platform. I don't see it as a viable permanent solution given the compromises involved and nor should the publishers.
My only complaint is the URLs are prefixed with Google.com making it harder to share direct links. But otherwise the UX improvements are worth the tradeoffs - in the meantime at least. If it's still the default in 2-3 yrs and news sites haven't fixed their sites I might take issue with it.
Edit: I did some testing and it looks like Google puts AMP articles in a carousel at a higher prioritized position vs other news stories. They aren't mixed with other news sites... that's not cool.
https://medium.com/@pbakaus/why-amp-caches-exist-cd7938da245...
They are a bad reminder of the early days of the mobile internet when lots of websites would automatically redirect you to a terrible 'mobile version'. I certainly want better mobile sites, but not in the form of these AMP pages.
Here's the patch that adds it to the list of search providers: https://sr.ht/h4bZ.patch
What choice do you have? Reject traffic from Google? Every time I have been to an AMP-enabled page it's been an awful experience and unwanted. But you don't "search" for something you "Google" it.
Publishers typically aren't where people go to buy things. In fact, I imagine Google views them as part of COGS in a sense since they are what create display inventory.
So if Google has the leverage to reduce the cost and increase user satisfaction while simultaneously exerting more control on the display ecosystem, it seems like a smart business move to do so.
AMP links are given priority in search.
I posted a complaint here a while back and the response I got made me wonder what I was missing. Like I was the only one who didn't appreciate it.
Yeah, I get that it speeds things up. But, do they really have to prevent you from linking out to the publisher's full site? There is no legitimate reason to serve up the publisher's content and force me back to Google. Can't even share the underlying URL. They are essentially hiding sites, but displaying their content. It's a hijack and I'm not sure why publishers approve.
And, on a recent search, the SERP only showed AMP, without the site name. Had to click thru before I even knew which site it was. Don't know if that was a bug or something they are testing.
Way too much power.
I find it works well, I don't think there's any abuse of power, and I think it's an entirely necessary standard.
1: I won't have a page that bounces around for 5 minutes as useless, non-content elements load.
2: I won't have to peer at a few lines of content through a window of toolbars and ads.
Christ, I tried to visit https://productforums.google.com/d/msg/webmasters/_O8kJMSDpO... from a Google SERP to link to their forums about this issue, and there's an unavoidable Google login prompt gating it...and I use 2FA. Why in the hell do I need to log in to view a forum thread?
Hopefully the push their product cycle up a year or two and deprecate AMP in the next few months.
A spark icon next to the search result that would take you to the AMP page if you want to just read something without navigating to a whole new website and the behavior of clicking to a search result is the same as before ––or vice versa, an icon would still take you to a website.
Beyond the distasteful navigation hijacking, and often broken or buggy page loading... I think Google throwing its weight around to force publishers to use it is an abusive use of power. I also think it's an unnecessary standard since it's nothing more than simple well wittten HTML and CSS.
Yes, we should make less shitty (meaning bloated) web pages that are rendered server side especially for mobile clients-- but that doesn't mean that if we don't we should be second class citizens.
More and more Googles search results are being materially affected by this choice. That is to say, AMP pages with no or little significance to my query are pushed to the top; while, relevant ones are not to be found. I find this primarily true with historical content or localized content where the host/author/org doesn't spend time updating things that aren't broken. Further, the companies prone to adopting AMP are doing as many things as they can simply to generate more traffic (i.e. click bait). So it's a race to the top for advertisers/media companies and a race to the bottom for quality results.
I will resume using google IFF they allow me to permanently opt out of AMP otherwise I will begin the slow arduous migration off all Google services.
Google trying to be the source of content instead of the guide to content will be its downfall from the top. I'm not saying they'll go out of business just that they'll someday be made less relevant from it.