Ok, so back in this previous post I discussed the fact that Accelerated Mobile Pages are now global and will apparently expand to other industries apart from news/blog sites. I also mentioned and linked to a WordPress plugin that is supposed to add AMP functionality to your posts with ease. I installed that plugin to see how well it would work, and here are the results!


So the first thing I wanted to do was make sure that the new pages the AMP WordPress plugin created actually validated as Accelerated Mobile Pages. If they didn’t, then there would have been no point checking anything else really… Now, to test this you need to go to the AMP version of a blog post and add the following to the end of the URL.


This will cause the page to load in a manner ready for validation. The next step is simple – just open the Google Chrome Developer window and the results of the validation will be shown immediately. As you can see from the screenshot above, the pages the AMP WordPress plugin creates validate with no issue.

Note: The easiest way to access the Google Chrome Developer window is to right click on the page and then select Inspect. The validation window will appear in the bottom right of the browser.

Duplication of Content

The next aspect that I felt needed to be checked was whether or not the new pages created by the plugin would lead to a duplication issue. Let’s face it, no one wants to install something that will duplicate the content of every single post on their website. So naturally the first thing I did was look through the source code of the /amp/ pages to determine whether it contained a canonical tag. It did, and it referenced the original post, so that was great.

But being a bit of a pedantic man, I had to check every single one of these pages. So, I ran a Screaming Frog crawl of the site and found that all of the pages created by the AMP WordPress plugin had canonicals pointing to their original counterparts. Win!

Crawler Access to the AMP Pages

So, the last thing that needed to be addressed was whether crawlers could actually get to the new AMP pages. The correct way to link to these pages is to use the “amphtml” link ref to tell crawlers that the page linked to is the correct page for inclusion in the AMP search results.

So, another quick look at the source code revealed that, yes, the pages created by the AMP WordPress plugin are linked to within the standard pages correctly! I guess that means another win on the checklist for the plugin.

So, To Wrap It All Up…

Now, I’m still waiting for any of my posts to appear in the actual AMP search results but that’s more a site equity issue (this is still a very new site that I’ve only just started truly bothering with). But in terms of this test and the usefulness of the AMP WordPress plugin? Everything went well!

Therefore, I highly recommend that you go and get it installed on your site if you haven’t already! It is easily the best and simplest way to get going on the AMP side of things, especially now that Google are rolling it out globally!

UPDATE 14th Oct 2016: Google have released an AMP testing tool (found here), and I ran one of my AMP pages made with the plugin through it. Here are the results I got!

So there you go! Just one more piece of evidence that the plugin works just the way we need it to!

Get the AMP WordPress Plugin here!