validate the amp page. A single error or warning will keep the page out of the amp cache. Validation is therefore a crucial step. Check this page for common company employee list validation errors. This video produced by the amp project explains how to validate pages: 2. Deploy amp pages I like the idea of testing one or two types of pages on your website on amp first. Ideally, include ranked pages so you can see if google offers the amp version in mobile search results.
Depending on your site's crawl rate, it may take a few days for google to find, verify, and index the amp version of the page. Let the deployment run for at least a month (longer if you can). As long as your pages are generating traffic, you will generate enough data company employee list to ensure that deploying amp sitewide is worthwhile. 3. Track with analytics you will want to track the performance of your amp pages. Since amp analytics will be different from normal google analytics, read this guide to understand how it works. You can track pages through internal or third-party analytics.
Many analytics providers have built-in configurations for amp-analytics. You can use amp-pixel for simple tracking and amp-analytics for everything else. Technical recommendations when setting up tracking: be sure to use the canonical url and other variables to company employee list define what should be logged. This is critical to understanding any increase or decrease in traffic due to amp. Use the extraurlparams attribute in amp‐analytics to add a query string parameter to the.