When Google’s Accelerated Mobile Pages Project was first announced, I was pretty excited by the idea behind it. Trying to load websites on a mobile device was always a bit of a pain, so AMP was a welcome idea for sure. But even though accelerated mobile pages have a number of pros, they have some cons as well. If you went the way of AMP, you may have to be ready to sacrifice ad revenue.
Despite all the hype surround it, site owners, webmasters and digital marketers have to decide if their site would actually need Google’s AMP Project. Google did a good job highlighting the benefits of fast loading pages (especially after announcing a mobile-first index) but avoided the obvious disadvantages.
In an article written by Sergey Grybniak, he examines all the pros and cons of using AMP. Also, Sergey answers a number of questions about them, like Do AMPs magically point your site to SERP success? Does it make sense to implement AMP on all pages? Which is better — AMP or responsive design?