This package, having been based on SEO code in coderedcms, has previously had the ability to generate AMP markup based on the HTML version of a page. This functionality existed purely for SEO reasons, as Google would prioritize sites in search rankings which served pages in their AMP format.
In practice, it is extremely difficult to accurately transform HTML to AMP, as they are two totally different languages. We would frequently see AMP errors in coderedcms sites in Google search console and webmaster tools. Editors simply add a lot of different content onto pages, and it turned out to be a fool's errand to try and dynamically translate unknown HTML content to AMP content. The "right way" to implement AMP is to lock down what editors can do on that page, and provide separate AMP and HTML templates for each component on that page.
All in all, as a developer, I am very glad to kill off AMP support as it has been nothing but a headache, with minimal gains for any customer outside the news industry.
If Google changes their mind in the future, we will always consider supporting AMP in the future if needed. For now, we recommend that anyone who needs AMP support do it "the right way" and implement dedicated AMP templates for each block and page in your Wagtail site.
vsalvino
commented
3 years ago
This package, having been based on SEO code in
coderedcms, has previously had the ability to generate AMP markup based on the HTML version of a page. This functionality existed purely for SEO reasons, as Google would prioritize sites in search rankings which served pages in their AMP format.In practice, it is extremely difficult to accurately transform HTML to AMP, as they are two totally different languages. We would frequently see AMP errors in
coderedcmssites in Google search console and webmaster tools. Editors simply add a lot of different content onto pages, and it turned out to be a fool's errand to try and dynamically translate unknown HTML content to AMP content. The "right way" to implement AMP is to lock down what editors can do on that page, and provide separate AMP and HTML templates for each component on that page.Further weighing on this decision is the fact that Google is no longer requiring AMP pages in order to be ranked in "Top Stories". Many articles have recently been written about this. See this article: https://www.searchenginejournal.com/google-retires-amp-icon-survey/406770/
All in all, as a developer, I am very glad to kill off AMP support as it has been nothing but a headache, with minimal gains for any customer outside the news industry.
If Google changes their mind in the future, we will always consider supporting AMP in the future if needed. For now, we recommend that anyone who needs AMP support do it "the right way" and implement dedicated AMP templates for each block and page in your Wagtail site.
Related:
1
2
22