When it comes to making advertising revenue off ads hosted on your website running your site via the AMP platform has a significant disadvantage. Since users are effectively accessing content hosted on Google’s servers, they will be viewing Google ads as opposed to paid content that is hosted on your website. This feature means that there will be more ad revenue for Google and less for the paid content creator. However, Google has acknowledged this shortcoming and allows you to link back to ads on your original site by using an amp-ad script and adding an amp-ad tag to your Accelerated Mobile Page site.
User Tracking and AMP Cached Pages
Another disadvantage of using the AMP platform instead of having visitors access your regular website directly is that tracking user activities is not straightforward. The fact is that AMP does not work with any visitor tracking that you have already implemented. Google tracks and stores these pages differently. Although some solutions resolve this challenge, monitoring user activity on AMP pages takes effort and a different set of resources. The other negative drawback from using AMP is that the content is served directly from Google’s cache servers. This feature allows Google to serve AMP pages much faster as they do not need to send traffic to an origin server. However, it also means the pages that appear in search results are held on the Google platform. As a result of this cached architecture, your visitors are not receiving content from the pages you originally created. They are effectively viewing a cached copy of your content that is stored somewhere else. Not only does this influence user tracking behavior, but it also means sites that need to serve refreshed content regularly need to factor this mechanism into their overall solution architecture.
Hidden Implementation Costs
The Benefits of AMP Far Outweigh the Costs