| So, to avoid having to argue the same problems always again, here’s a summary of some of the technical and antitrust issues with AMP: 1. You have to embed the AMP version from Google’s servers, you can’t self-host the AMP js, or run it from another CDN. This makes your site unavailable in, for example, China, relies on Google’s systems, and ensures that Google knows every user of your site. Source: https://www.ampproject.org/docs/reference/spec#required-mark... > contain a <script async src="https://cdn.ampproject.org/v0.js"></script> tag inside their head tag. 2. You need to allow Google to cache the content, and all Google products will always link to the Google cache version. You can not opt out of this. You can not ensure users visit your own CDN version. You can not prevent Google from displaying modified versions of the pages (for example, the header UI of AMP pages in Google search, and the swiping between pages gesture). Source: https://developers.google.com/amp/cache/faq > Q: Can I stop content from being cached? > A: No. By using the AMP format, content producers are making the content in AMP files available to be cached by third parties. For example, Google products use the Google AMP Cache to serve AMP content as fast as possible. 3. Pages that use AMP get a massive indirect ranking boost. Yes, they don’t get directly boosted, but they get added to the AMP carousel, between the ads and the #1 result, or between the #1 and #2 result. If, for a given search term, none of the top pages have an AMP result, Google will boost the first 3-4 pages that have an AMP result to this place – even if they’d organically rank on page 10 or later. In some situations, I’ve seen results from page 13 boosted to #1. |