>with seemingly no opt out (on the consumer or publisher side)
I though AMP was opt-in for publishers? As in you have to write the front-end spec and pick a CDN to cache with.
I though AMP was opt-in for publishers? As in you have to write the front-end spec and pick a CDN to cache with.
It is but Google will only put you in the carousel at the top of the search if you use AMP. That's a significant enough driver of traffic where publishers can't afford to lose it.
we had an emergency AMP project after our traffic dropped 35% due to a smaller competitor implementing AMP and google rewarding them by boosting them in the search results.
So unless you can survive getting bumped off of the first page of results, not implementing AMP isn't optional.
I now use https://github.com/bentasker/RemoveAMP, but that's only possible because I'm lucky enough to have a Jailbroken iPhone. :/
I guess you'd call it an "extension"? It feels weird to use that term, as it implies (to me) that there's some sort of extension framework in place. There isn't, it's just code injection.
Yeah extension does sound weird.
Every link aggregator that indexes your AMP page will cache it, including Bing and Baidu. That's what makes safe prerendering possible.