Drawbacks and additional considerations for

 While AMP can help to improve your ranking as well as the experience and performance of your content to mobile readers, it does have drawbacks and caveats which you should consider when deciding whether to implement AMP for your site:

• To begin with, adopting AMP pages entails sacrificing a significant number of UX elements on your webpage. At its core, AMP HTML prioritizes efficiency over creativity, so if engaging visuals is a big part of your web experience, this may not be for you.
• In addition to limited images on your AMP pages, you’ll also only be allowed one advertisement per page. This limiting framework also doesn’t support disruptive ads like expendables, while direct-sold ads can be difficult to implement.
• From a marketing perspective, it costs double the crawl for one piece of content, part of Google’s thrust to ensure parity. For many publishers, it’s been found to drive impressions but not necessarily engagement metrics. This is due to the Top Stories carousel that encourages users to read from other sources.
• In a similar vein, Google’s AMP viewer tends to dilute brand identity as a Google domain is shown in the address bar. While there is a fix to show the actual site on top of the AMP page, it takes up precious space above the fold. You may also not achieve the same brand feel with a Google AMP page vs a standard page, as seen with the example below:

 

• As well, AMP only works if users click specific database by industry  on the AMP version of a webpage (instead of the canonical version). And while studies have found that the AMP library can reduce the number of server requests to fetch a document by as much 77%, the AMP version is not always served if it’s not implemented correctly.
• While AMP has been around for four years, it’s still relatively in its nascent stages.

Here are some final details about Google AMP that must be considered when deciding whether to implement it on your site.

• You need to use a streamlined version of CSS.
• You’re only allowed to use the JavaScript library that AMP provides, and because you’re not in control, you could experience lazy loading (perhaps the only downside of AMP).
• AMP sites must be properly validated if they are to work every time.
• AMP plugin pages don’t allow forms.
• Custom fonts need to be specially loaded for better experience.
• You need to declare image heights and widths.
• You need AMP-approved extensions if you want video content on your pages.

Finally, AMP prioritizes speed and readability, not shareability. So because your social sharing buttons are created using JavaScript, they may not display properly.

AMP prioritizes speed and readability, not shareability.

How to implement AMP to improve your content and SEO

Of course, if you have a WordPress site, the simplest way to start implementing AMP is to use the official AMP plugin from WordPress and Google.  If you’re looking to have more control over how your AMP pages look or gather analytics more easily, you might try other free plugins such as WeeblrAMP or AMP for WP.