How to avoid common mistakes when publishing Accelerated Mobile Pages

Sebastian Benz
Mar 29, 2016 · 4 min read

1. Publish only valid AMP files

Something is wrong.

2. Include correct metadata

3. Ensure your AMPs are discoverable

<link rel=”canonical” href=”http://example.ampproject.org/article.html" />
<link rel=”amphtml” href=”http://example.ampproject.org/article.amp.html" />

4. Allow Crawlers to access your AMP Files

User-agent: *
Disallow: /amp/ <= don't!
<meta name="robots" content="noindex" />   <= don't!
$ curl -I http://www.example.com/amp.htmlHTTP/1.1 200 OK
Date: Tue, 25 May 2010 21:42:43 GMT
(…)
X-Robots-Tag: noindex <= don't!
(…)

5. Test that your AMPs load correctly via the Google AMP Cache

Your AMP page cannot be shown in the AMP Cache.

6. Serve everyone the same version of your AMPs

More Resources

Google Developers

Engineering and technology articles for developers, written and curated by Googlers. The views expressed are those of the authors and don't necessarily reflect those of Google.

Thanks to Adewale Oshineye.

Sebastian Benz

Written by

Developer Advocate @Google — Android, AMP and Co.

Google Developers

Engineering and technology articles for developers, written and curated by Googlers. The views expressed are those of the authors and don't necessarily reflect those of Google.