5 ms·
To me, nobody would willingly give up the most important part of their page's real estate (the top X pixels) and the branding value of what it says in the url b
by tyingq 5y ago
To me, nobody would willingly give up the most important part of their page's real estate (the top X pixels) and the branding value of what it says in the url bar...unless there was a tradeoff that made it worth it. As far as I can tell, carousel placement was that tradeoff. Until recently, you weren't allowed in unless you were on AMP.
Also, I'm not sure this is well known, but if you navigate to a web page from the carousel, Google traps the left and right swipe events on YOUR page. Either sends to user to a competitor. That's a pretty big compromise you would only make because the traffic boost from the carousel was worth it.
- jeffbee 5y agoThere's nothing about AMP that requires anyone to give up any part of their page. The presentation you are talking about is a feature of only certain AMP hosting services. A lot of organizations host their own AMP sites, like Conde Nast magazines. Example: https://arstechnica.com/gadgets/2021/06/qualcomms-new-snapdragon-888-plus-soc-has-a-new-name-not-much-else/?amp=1 https://arstechnica.com/gadgets/2021/06/qualcomms-new-snapdr...
- tyingq 5y agoYes, I'm speaking exclusively of Google's AMP cache, which I assume dwarfs any other in numbers of notable users. Edit: As for Conde Nast, I found this article: https://technology.condenast.com/story/the-why-and-how-of-google-amp-at-conde-nast https://technology.condenast.com/story/the-why-and-how-of-go... The diagram[1] suggests the Google AMP cache is (or was) in front of users, and they also say this: "AMP helps us satisfy these needs. AMP increases the visibility and discoverability of our content by allowing it to be included in Google’s Top News Carousel, as well as improving the experience of regular Google search results" That sounds a lot like what I said. [1] https://media.condenast.io/photos/59a57e16cf742825d0b02891/master/w_680/AMP-Arch.png https://media.condenast.io/photos/59a57e16cf742825d0b02891/m...
- jeffbee 5y agoThe article directly contradicts your claim. People can use Google's CDN without losing control of any part of their content. It's just a CDN.
- tyingq 5y agoSo, from Chrome mobile, I searched for "springsteen anti-vaccine". The first carousel entry is a CondeNast property, vanityfair.com, with an AMP lightning bolt icon. I click it, and get this: https://imgur.com/a/2W3oWSW https://imgur.com/a/2W3oWSW The top bar is Google controlled. The url in the omnibar is a google url. So I'm not seeing how Conde Nast is a good example here. Before they very recently rescinded the requirement, using a non-Google AMP cache meant you didn't get into the carousel.
- jeffbee 5y agoWhat you're complaining about is that Google frames the carousel results, which is a completely legitimate complaint, but which is not really related to AMP as such. Edited to add: An example of where the same content is not framed by the same search engine is on Chrome Mobile's new tab page "articles for you". Many of these are directly links to unframed AMP content, such as what I'm seeing right now: seekingalpha.com/amp/..., thehill.com/...?amp etc
- tyingq 5y agoMy point is that I believe Conde Nast chose AMP mostly so they would be in the carousel and not lose traffic since the carousel pushes down the organic results. The quotes from them I copied in up-thread comments seem to align with that. I also believe they would have passed on AMP if the carousel wasn't there, but I obviously can't prove that.
- nightpool 5y agoAs a web developer, I really value the extra speed that having my page served from an AMP cache + predictive prefetching gives me. And now that signed exchanges have shipped, giving up the top X pixels and the URL bar are no longer required trade-offs to get that value.
- tyingq 5y ago"now that signed exchanges have shipped" For Chrome, yes.
- nightpool 5y agoThat's a good point. Webkit's opposition to Signed Exchanges (ironically, canonically expressed in an HN comment: https://news.ycombinator.com/item?id=19679621 https://news.ycombinator.com/item?id=19679621) means that I'm stuck with AMP for good performance on iOS for the foreseeable future.
- dmitriid 5y agoNot just WebKit. Mozilla is opposed, too. And they have a whole document on Web Packaging: https://docs.google.com/document/d/1ha00dSGKmjoEh2mRiG8FIA5sJ1KihTuZe-AXX1r8P-8/edit https://docs.google.com/document/d/1ha00dSGKmjoEh2mRiG8FIA5s...
- nightpool 5y agoSure, I've read Mozilla's standard-position document and I understand their objections, I'm just saying that Webkit's objection is the major blocker to me personally adopting sxg (since Firefox is basically 0% of my mobile traffic)