Comment

Comment by cyrusshepard

This is a good response and I appreciate Malte's effort to engage publishers, but it doesn't calm my nerves about the biggest publisher complaint about AMP:

Google owns the chrome (top navigation) on all AMP pages. This makes it easy to navigate back to Google (why would you ever want to leave?) and other publishers in the AMP ecosystem, but much harder to navigate to the publisher that created the page in the first place

In essence, this means that what was once a publisher-owned page is now shared property: between the Google and the publisher. By controlling the top navigation, Google more easily controls the content the visitor sees, keeps visitors on Google longer, provides greater opportunity to track visitors, and perhaps most importantly has the opportunity to earn more ad revenue.

Now imagine if this was a requirement for ALL pages served in Google search results. You publish a page and it appears in Google, but when the user clicks on it Google has pasted a new navigation on the top of your page. This is exactly what is happening with AMP.

This is especially troubling in light of all the anti-trust controversies Google is finding itself in, both in the US and abroad. A recent study showed that 49% of all Google clicks go to Google properties of one kind or another (Maps, YouTube, Ads, etc) http://www.slideshare.net/randfish/intro-to-mozcon-2016/24-L...

Does AMP count as another Google property that will push more than 49% of clicks their way? Hard to say, but it's a disturbing trend for a monopoly and a hard pill for publishers to swallow.

parent cyrusshepard 10 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton