Just a quick follow up to my post on Accelerated Mobile Pages and some clarification.
AMP’d makes the mobile web run faster. That’s what it’s all about and for most people that’s all you need to know about it.
That also means that it’ll load faster and because of that Google is going push (SEO) AMP’d up posts that it finds higher in the search engine results. That’s the good thing.
Since it’s also very new, it’s going to have issues. I just received this from my Google Webmaster account.
That led to a list of 31 errors stopping my posts from being AMP’d. Most of which look like this.
So while I look for the cause and possible errors (in my free time), here’s what an AMP’d page is supposed to look like: https://areweconnected.com/technology/awc-is-ampd/amp/ and compare that with one that is not https://areweconnected.com/technology/awc-is-ampd (you can view it on your desktop, mobile or tablet).
The AMP’d version (on the left) removes the menu bar, the sidebar and pretty much everything run by scripts. Your typical share buttons, calls to action, etc are run by scripts.
THE SWORD CUTS BOTH WAYS
I’m not too happy about AMP. I can see the benefit for the readers in the big picture but like a kid who’s toys are being taken away I’m not happy.
The Good: If AMP’d takes off, and I think it will, I sure my AMP’d posts will get even better traction and much better SEO for mobile readers. We all want our content to reach a wider audience, right?
The Bad: We’ll have to watch this closely and might have to rethink the way we use lead generation and calls to action in our posts. How might we do that?
Here’s one way. If you are reading this post AMP’d, I’d like to point out that I build Custom Websites on WordPress. You can click on this LINK to find out more. Without scripting, that’s about all the Call To Action you’ll get.
What do you think about this new AMP’d stuff?