Why I will wait on implementing Google AMP

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Why I will wait on implementing Google AMP

      What are your thoughts? Google is fighting Facebook back. Is anyone planning to try this out in some blog? Blogs that have added AMP haven't yet received their AMP icon in google search. But on the plus side, they have seen small improvements in google search.

      It’s been a few months since Google released the Accelerated Mobile Pages (AMP) pages into its search engine results. It’s open source and backed by WordPress and Google specifically for speeding up the mobile web rendering experience. However, I’m not yet sold on this. Here are some thoughts on why I will wait on implementing Google AMP.
      AMP is Google reply to Facebook Instant Articles. If you haven’t heard about Facebook Instant Articles – it’s ok. Only a few publishers are using it. In short, to explain – you’re staying in a Facebook application and reading news instantly. There is almost no waiting time and usually, I’m getting less than a second to load the article. According to Facebook, you’re opening web page 10X faster than opening an external link.
      AMP plugin is free and you can download it from WP plugin directory. The main intention is to boost page speed by using stripped down the page. However, your AMP links will only work from Google search or Twitter.

      Why I’m not implementing AMP

      AMP is latest SEO opportunity but publishers are slow to implement it and I understand them. AMP plugin is for free and it would seem like a good idea to add it. But after doing it, you will receive a lot of AMP errors in Google Search Console.
      You’ll need to customize a template and fix errors. A lot of dynamic elements will be gone. The idea is to make page load fast, but elements like comments, pop-up boxes may actually slow a page down. I don’t see this working on businesses that use any kind of forms for users.
      Some cache plugins are reporting errors together with AMP. At this moment there are more problems with AMP plugin and functionality. I will wait a couple of updates and see how it moves forward. If you have time to look for errors and fixes you could try to implement AMP.
      Also, some branding and elements will be removed as the style will be stripped down. It’s not something I’m looking for now. However, I would like to say that AMP projects have more friendliness than Facebook Instant Articles. After knowing both projects I’m interested in implementing AMP more.

      Original article from my blog.
      /Enter Your Signature here/