Despite understanding and largely agreeing with the concerns against AMP Cache that get discussed any time an AMP article gets posted on HN, I cannot stress enough on how relieved I feel to see the lightning icon next to a mobile search result, especially on my now aging phone. Most content websites have become such a massive crapfest of ad-bloat, bad UX, huge page sizes and general usability hell that it's nigh impo…
Google AMP is bad for e-commerce
31–40 of 159 posts
Re: Google AMP is bad for e-commerce
#32Earlier quoted context omitted.
I don't think its that. Its that AMP is borderline an anti-trust. But the point is, even with the speed and possible ranking boost, does it boost conversions? More traffic without conversions generally does not help an e-commerce site.
First, how is it anti-trust? And second, it's been shown that faster page loads = better conversions since your bounce rate drops. This is especially true for mobile.
Re: Google AMP is bad for e-commerce
#33The author seems to completely misunderstand the point of AMP. It was never designed or created for dynamic, interactive content, especially e-commerce. This is like complaining that a hammer is bad for driving screws.
Re: Google AMP is bad for e-commerce
#34Earlier quoted context omitted.
Cloudflare provides AMP cache. If you don't want to use Google CDN.
That still doesn’t give you any of the ranking boost – that is only given if you allow Google to cache it on their CDN. Google does that by default, you likely don’t even notice it, but if you try to prevent it, you lose the ranking boost.
Re: Google AMP is bad for e-commerce
#35Earlier quoted context omitted.
There is no direct source, but you can try it, or just look at the current implementation. Currently, Google serves AMP by serving all AMP search results from its own cache, which allows Google to add features such as the header bar, or the swiping between carousel elements. This doesn’t work if the pages are from different origins. EDIT: I found some sources: > contain a " rel="nofollow">https://cdn.ampproject.org/v…
> Q: Can I stop content from being cached? How different is this from common HTML caching done all over the web? And that's about using the Google AMP Cache, not about using AMP. And you still didn't provide a source about "having to use Google's CDN". Essentially: do AMP pages hosted on Cloudflare's cache do not get into Google Search carrousel?
> And you still didn't provide a source about "having to use Google's CDN".
This is the issue I meant with Google’s CDN/Cache.
If a user clicks a link to an AMP page in Google search, they are not redirected to your page. They ALWAYS get the cached version from Google, and Google modifies your page by adding UI, and changing other functionality (for example, the left/right swipe gestures are changed to navigate to other Google search results).
You can not opt out of this while still appearing in the carousel.
Re: Google AMP is bad for e-commerce
#36Earlier quoted context omitted.
> Its that AMP is borderline an anti-trust. And why is that? > More traffic without conversions generally does not help an e-commerce site. You should not be using AMP for e-commerce, at least not for anything but a static product page. Again, if you try to drive a nail with a hammer and it doesn't work, the fault isn't on the hammer, it's on you.
> And why is that? Because you only get a ranking boost if your page > contains a " rel="nofollow">https://cdn.ampproject.org/v0.js"> tag inside their head tag. and > is allowed to be cached in the Google AMP cache
Re: Google AMP is bad for e-commerce
#37Despite understanding and largely agreeing with the concerns against AMP Cache that get discussed any time an AMP article gets posted on HN, I cannot stress enough on how relieved I feel to see the lightning icon next to a mobile search result, especially on my now aging phone. Most content websites have become such a massive crapfest of ad-bloat, bad UX, huge page sizes and general usability hell that it's nigh impo…
Re: Google AMP is bad for e-commerce
#38Why would you build your whole site on AMP??? Please read this before think about build AMP. https://www.smashingmagazine.com/2016/12/progressive-web-amp...
> Why would you build your whole site on AMP??? To get a ranking boost? For some search terms, moving to full AMP gives you a ranking boost catapulting you from page 13 or worse to the #1 result. So if you don’t use that, someone else will use that advantage.
Re: Google AMP is bad for e-commerce
#39Earlier quoted context omitted.
That still doesn’t give you any of the ranking boost – that is only given if you allow Google to cache it on their CDN. Google does that by default, you likely don’t even notice it, but if you try to prevent it, you lose the ranking boost.
Can you provide a reference where it says that there is rank boost for AMP sites. AFAIK if you're site is fast it will get some boost only in mobile. But it doesn't need to be an amp site. Gurdian for example runs their own AMP cache.
For example, none of the newspapers reporting about stuff where I live support AMP, but a few US newspapers that report about sports events that happened years ago do.
So when I search about stuff in my city, at the top there’s an AMP carousel with news from years ago, and below that only the actual results.
Re: Google AMP is bad for e-commerce
#40Earlier quoted context omitted.
First, how is it anti-trust? And second, it's been shown that faster page loads = better conversions since your bounce rate drops. This is especially true for mobile.
Imagine the scenario, a user lands on the AMP page and a user lands on a responsive page. Both have a question about shipping time. The AMP user has to navigate to a contact form to ask, then submit. The responsive user can just ask in the chat window on the page.
Why would you use an AMP page for that? It was specifically NOT designed for those use cases.
Now back on your point: if the users who have a question are a small % of the total users, why would you have all users load the heavy chat window on mobile devices with limited screen space?