He avoids really hard addressing the only bit that matters > Guess what happens when the "close" button is clicked inside the AMP view? And the amount of disingenuous on this just rubs me the wrong way: > If you are not comfortable with traffic on your AMP pages, please do not publish AMP pages.
Happy to address the close button: You are on a search page, you go on layer deep by clicking. The close button goes back. I don't see what else it should do. Mind you that I do understand that a link to the origin server would be a good improvement (and I've stated that in the post). I'm not sure what you find disingenuous. AMP are just web pages saying "HEY I A AMP, please use treat me as AMP". You can publish the…
Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
101–110 of 204 posts
Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#102Earlier quoted context omitted.
If you aren't comfortable with it, just don't use it, right? I'm probably missing something, but I don't understand how something can be such a hard pill to swallow when it is opt-in.
AMP content shows up before other organic search results. So it's not really optional unless you want to lose all your search-driven traffic.
Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#103Earlier quoted context omitted.
It's one more step along Google's path to eating the internet. Google-served content discovered through Google search rendered in Google's browser running on Google's operating system on a Google-manufactured device connected through Google's ISP and Google's network protocol (QUIC). Vertical integration.
You know the cool thing about this integration ? Any part can be replaced. Some instantly, some take more time because they involve physical stuff. People use the Google integration because it's there by default, not because they are locked-in.
Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#104This 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…
The extra chrome appears to be displayed in browsers but not in the Google app. On Android it's more natural to search from the app; I don't know what the situation is like on iOS. I still don't understand why it's mandatory to use the Google CDN, but I probably don't want to know.
Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#105Earlier quoted context omitted.
To be fair, the user coming from a search engine is most likely to want to navigate back to Google than to stay on the page. It might not be benevolent but it is an improvement to the user experience of most people.
That's why we have back buttons, no?
This is modus operandi for many users, hence why Google inserting a big 'go back to Google' banner at the top, is a bad[1] thing.
--
[1] Or from the standard user point of view, a good thing.
Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#106Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#107As positive as the response sounds, it is an empty promise. > We’re looking at ways to make the source link more discoverable and will update once that is done. If Google was actually going to fix the issue, they would have said "we will make the close button direct users to the original site and will update once that is done" OR "we are changing the x (close) button to a ← (back) button". "x" means "close" and "←" m…
Am I in the minority in that I found the function of the "x" to be very clear? I don't know if it is fair to call it "nothing less than a dark pattern" without a bit more data.
I've also sometimes been on a non AMP version, and Chrome has suggested "a version optimized for mobile". Clicking that has opened the AMP version and after reading the article, clicking the X took me back to the non AMP version.
Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#108This 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…
Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#109Of all his 725-words response only 18 words directly address the problem:
>We’re looking at ways to make the source link more discoverable and will update once that is done.
That's 2.5%. Is he really a tech lead?
Re: Response from Google Tech Lead, Re: “Google May Be Stealing Your Mobile Traffic”
#110Earlier quoted context omitted.
It's one more step along Google's path to eating the internet. Google-served content discovered through Google search rendered in Google's browser running on Google's operating system on a Google-manufactured device connected through Google's ISP and Google's network protocol (QUIC). Vertical integration.
Google is just sending a different type of traffic: "one page traffic", but let's not forget that it is Google that is sending the traffic to AMP pages in the first place, there should be no entitlement on the part of webmasters.