1. Weston Ruter

    Given the complexity of the AMP plugin and its many configuration options, the onboarding wizard was a critical addition if the plugin is going to grow past 500,000 active installs to reach a larger number of non-technical users.

    Building on the capabilities in 2.0, we’re currently working on site compatibility scanning functionality that will better identify to what degree your existing theme and plugins are already AMP-compatible. With this information we can then provide more guidance for tailoring the default configuration for a given site. We’re also looking at ways to better highlight AMP-compatible themes and plugins in WordPress’s directory browsing screens, including suggesting alternatives to incompatible plugins. We’re also aware that extending such screens is controversial so we want to make sure it is done right. (Nevertheless, the AMP-compatible ecosystem is not comprised of our own themes and plugins.)


  2. Kingsley Felix

    Google analytics is not working because we can’t track visit for AMP.


  3. Marcus Tibesar

    So if you are sure that your theme is AMP compatible, which of the three modes is preferred?


    • Sarah Gooding

      Google would probably recommend Standard Mode so that all your URLs are serving AMP pages.


    • Sam

      Never go full AMP, please. There’s no reason to use non-standard proprietary Google tech. The only reason to use AMP is to get access to their AMP carousels, so you can do well by limiting it to that.

      Focus your efforts on getting a speedier site without the AMP overhead.


    • Weston Ruter

      Yes, that’s right. If the theme is AMP-compatible then Standard mode is best because it means desktop visitors get the same UX of AMP as mobile visitors.

      However, there’s still a case where Transitional mode may be preferable: if you’re using a plugin that is not AMP-compatible where some of its functionality has to gracefully degrade on AMP pages (due to the custom JavaScript being stripped out), then in this case Transitional mode can be better since mobile visitors would have the opportunity to navigate to the non-AMP version to access that functionality.

      The upcoming plugin compatibility scanning feature in the AMP plugin will help guide you when Transitional mode is preferable to Standard mode for your site.


  4. Sam

    Google and AMP. How sad it is the number of dev-hours are wasted on this monstrosity.

    Instead of focusing on a speedier web on its own, when it’s proven time and again things can be much faster without AMP, we have this wasted effort on the proprietary Google invention. All for the sake of, well, Google.


    • Weston Ruter

      AMP has been a testing ground for new technologies to improve the page experience. Several of them are on the road to becoming standardized outside of AMP. See Standardizing lessons learned from AMP.

      Also, AMP is no longer a Google project. It is under the OpenJS foundation, same as jQuery and Node.js. AMP has an open governance model. It’s not just for the benefit of visitors to Google search. Twitter also links to AMP pages. Microsoft has also linked to AMP pages in Bing.

      That being said, it’s true that you do not need AMP to make a fast website. Google even has made this explicit this year with the announcement of Core Web Vitals. Any page that has the similar performance as AMP pages can receive the same treatment in Google search. (For example, Top Stories carousel on search no longer requires AMP.)

      In the same way that WordPress democratizes publishing, AMP’s goal is to democratize performance. While you can make a fast website from scratch, it is very hard to do so. In WordPress this is particularly so given the huge variance in quality among themes and plugins. The AMP plugin is an enforcer: it provides performance constraints to help ensure that visitors will be able to get a good page experience.


Comments are closed.

%d bloggers like this: