Google AMP Issues
page-template-default,page,page-id-16611,ajax_fade,page_not_loaded,,qode-child-theme-ver-1.0.0,qode-theme-ver-17.1,qode-theme-bridge,wpb-js-composer js-comp-ver-6.6.0,vc_responsive

What are some common complaints about Google AMP?

With all of the pros that come along with Google AMP, it also has its fair share of cons. With that said, many of these issues will most likely clear up as the program develops further and Google works with its users. The simple answer is that Google AMP is not for everyone, preventing sites that are not blogging or publishing articles to reap the benefits.

One of the most common complaints that comes along with Google AMP is that it is limited in design and functionality. Google AMP only allows a very basic format to ensure optimal speed. This includes a heading, image, body content and other small additions. This is going to hurt any site where Javascript and external style sheets are a factor. Publishers will need to make simplified versions of the pages they will be using for AMP to meet the codes. Google AMP doesn’t offer forms for publishers, making it impossible to grow e-mail lists through Google AMP.

Another common complaint is that Google AMP does not directly impact Google ranking. As many predictions say, Google will most likely add Google AMP to the ranking algorithm in the near future. If you’ve noticed, when a user navigates to a Google AMP page, the URL provided is just added on to the already existing google URL, directly impacting website domain authority. The user is not viewing this through the publisher’s URL.

While Google AMP is allowing ad placement on their webpages, there are currently many regulations to the program. Ads are loaded with a custom amp element called <amp-ad>. Just like the rest of the Google AMP elements, AMP ads do not support any javascript at this time, and is instead replaced with iframes, which execute the ad network’s JS inside the iframe sandbox.