AMP (Accelerated Mobile Pages)
AMP is an open-source framework for fast mobile pages built from AMP HTML, the AMP JS runtime and AMP caches. Google supports it but no longer requires it.
What is AMP (Accelerated Mobile Pages)?
AMP (Accelerated Mobile Pages) is an open-source framework for building fast-loading web pages, introduced by Google in 2015 and now governed by the OpenJS Foundation. AMP pages use a restricted form of HTML, a managed JavaScript runtime and optional cache delivery. Google Search still supports AMP, but it is not a ranking factor or a requirement for any search feature.
This entry covers how AMP is implemented and how teams manage or retire it. For the history and the 2021 Top Stories change, see Accelerated Mobile Pages.
How it works
AMP has three building blocks:
| Component | What it does |
|---|---|
| AMP HTML | HTML with custom elements (amp-img, amp-video, amp-form) and rules such as inline CSS size limits |
| AMP JS | Runtime that controls resource loading and layout to avoid content shifts |
| AMP Cache | CDN that serves validated AMP pages, enabling preloading |
Pairing a standard page with AMP:
- Create the AMP version with the same main content.
- On the standard page, add rel=amphtml pointing to the AMP URL.
- On the AMP page, add rel=canonical pointing to the standard page.
- Validate with the AMP validator and check the AMP report in Search Console.
Structured data should match between versions.
Examples
- A publisher uses a CMS plugin to generate /amp/ versions of articles. Each article links to its AMP twin with rel=amphtml, and Search Console reports AMP validation errors for pages with unsupported embeds.
- A B2B SaaS company retires AMP after its main templates pass Core Web Vitals. It removes amphtml links, 301 redirects every /amp/ URL to the canonical article and confirms in Search Console that AMP pages drop out of the index without traffic loss.
Best practices
- Prefer one fast responsive page over two templates unless you have a specific reason for AMP.
- Keep parity of content, internal links and structured data between AMP and canonical versions.
- Check analytics. AMP needs its own analytics configuration (amp-analytics); otherwise sessions go missing.
- Test forms and CTAs. Lead forms often break or behave differently in AMP.
Common mistakes
- Removing AMP by deleting pages instead of redirecting them.
- Leaving rel=amphtml links pointing to AMP URLs that no longer exist.
- Assuming AMP pages automatically pass Core Web Vitals. Heavy ads and images can still slow them.
Related terms
- Accelerated Mobile Pages (AMP)
- Core Web Vitals
- Redirects
- Canonical URL
- Lazy Loading
- Mobile Usability
Sources
Frequently asked questions
How do you link an AMP page to its canonical page?
On the standard page, add a link element with rel=amphtml pointing to the AMP URL. On the AMP page, add a link element with rel=canonical pointing to the standard page. If the AMP page is the only version, it should reference itself as canonical.
How do you remove AMP without losing traffic?
Remove the rel=amphtml links from canonical pages, then 301 redirect each AMP URL to its canonical equivalent. Keep the redirects in place long term, update internal links, and watch Search Console coverage and performance reports for a few weeks. Expect a short transition period.
What is the AMP Cache?
An AMP Cache is a content delivery network that stores and serves validated AMP documents. Google operates one, and search results could preload AMP pages from it, which is why AMP pages often appeared to load instantly from search. Other providers have operated caches too.