(sigh)
if you read the docs and understand its purpose of working with “posts” which are different than “pages” in WordPress — (posts are typically articles, pages are typically static information like “about us”) — then you would “get” that the purpose of AMP is to speed up popular pages in mobile. It’s more likely that a large number of people might read a new review of new Star Trek movie, but unlikely that thousands would read your “about us” page all at the same time.
Why not go read up on what the purpose of AMP is actually intended for and you’ll have better idea of why to use it.
This plugin is made by the same people who make WordPress, so it’s currently the best choice for quick compatibility, provided you don’t have other issues with your content.
This isn’t likely to help a corporate information portal, but is intended for the publishing business, news sites, and “post pages” which likely get a lot of traffic on mobile devices.
Hope that helps!
Welcome to WordPress!
Thanks for the reply @neotrope, I have read up on AMP and I know how Google’s algorithm is changing to provide AMP higher priority with a majority of users browsing the web via mobile devices compared to desktop.
Since WordPress is used not only for blogging anymore and a lot of sites have WordPress websites with static “pages”, I would expect the plugin to be able to convert static pages as well as blog posts. Therefore, I believe the title of this plugin is a bit misleading, but also understand that marketing Accelerated Mobile Posts may be harder to get people to download the plugin.
Since this won’t help for a majority of my clients, I think I will keep looking around or work on making their pages as fast as I can in the mean time.
I’m not that great with coding in php just yet, but would it not be easy to include the pages post type in this plugin?
Heh… well, Automattic/WordPress didn’t come up with the ‘pages’ in Accelerated Mobile Pages (AMP), Google did. SO, probably good to complain to Google about that 😉
No, I believe that Google knows what they are talking about when they updated their algorithm to support Accelerated Mobile Pages and I don’t feel a need to complain to them for a plugin that Automattic can’t code correctly. If you research Google’s AMP, you will find that it’s not specifically related to blog posts but to all pages out there on the web, including posts.
Before things get twisted, I never complained about AMP or the plugin that says it will make your site AMP compliant. I just research things before I use them and if a plugin says it will only make Posts, AMP ready, then it’s not the plugin I am looking for.
I’m sorry, but I believe Google knows what the fuck they are doing and I’m even more sorry that this plugin wasn’t coded accordingly.
Google is only currently indexing “content” for AMP in compatible device mobile searches, so at this point kind of irrelevant whether “this plugin” will serve up pages. If you read the threads, and the plugin support site, you’ll see info on how to enable it for pages if you really want to do that.
You can of course build your own AMP support – we did that for client with a static content site, by simply making our own template and publishing the verisions for AMP with amp-nameofile.shtml and added the rel link to all pages to be “itself with amp- appended to front” — Q E D.
This plugin does what it advertises and it’s free.
So, you likely want to mark this topic resolves as your query wasn’t really support oriented and more of feedback on what you think about it, not what it actually does and does very well.
Anyway – won’t pester you any more about it. 🙂
Hey Neotrope, thanks for breaking that all down. I didn’t realize I created a support ticket, I thought it was more of a pre-download question so I will gladly mark it as resolved. Especially after you mention that it can be set up and enabled to work for pages.
Sorry for getting a little hostile there to your comment, thanks again for explaining everything!
