AMP (Accelerated Mobile Pages) is an open-source HTML framework Google introduced in 2015 to make mobile pages load near-instantly by restricting what a page is allowed to contain. The stakes today are mostly about legacy: if you still run AMP, you're maintaining a parallel version of your site for a program whose carrots — the Top Stories requirement and the lightning-bolt badge — Google removed back in 2021.
How AMP works, mechanically
An AMP page is regular HTML with rules. Author-written JavaScript is forbidden; interactivity comes from a managed runtime and a catalog of components (<amp-img>, <amp-carousel>, <amp-analytics>). Every resource must declare its size so the layout never shifts. CSS is capped and must be inlined. In exchange, pages validate against a strict spec and could historically be served from Google's AMP Cache — which is why AMP results used to open with a google.com/amp/... URL instead of yours.
A minimal valid AMP document looks like this — note the ⚡ attribute, the mandatory boilerplate, and the canonical link pointing back to the normal page:
<!doctype html>
<html ⚡ lang="en">
<head>
<meta charset="utf-8">
<script async src="https://cdn.ampproject.org/v0.js"></script>
<link rel="canonical" href="https://example.com/article/">
<meta name="viewport" content="width=device-width">
<style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;
animation:-amp-start 8s steps(1,end) 0s 1 normal both}</style>
<noscript><style amp-boilerplate>body{-webkit-animation:none;animation:none}</style></noscript>
</head>
<body>
<h1>Hello AMP</h1>
<amp-img src="/img/photo.jpg" width="1200" height="800" layout="responsive"></amp-img>
</body>
</html>The non-AMP page advertises its AMP twin with <link rel="amphtml" href="...">, and the AMP page points back via rel="canonical". That pairing is where most AMP bugs live — see our note on AMP canonicals pointing to disallowed URLs for a classic failure mode.
The rise and fall, honestly
Here's the timeline that matters, because half the AMP advice still circulating online predates the 2021 turn.
| Year | What happened | What it meant for site owners |
|---|---|---|
| 2015 | Google announces AMP as an open-source answer to Facebook Instant Articles and Apple News | Publishers start building parallel AMP versions |
| 2016 | AMP results go live in Google Search; the mobile Top Stories carousel effectively requires AMP | News sites adopt en masse — it was the only door into Top Stories |
| 2018–2019 | AMP for Email launches; Signed Exchanges let AMP pages show the publisher's own URL; project governance opens up and moves toward the OpenJS Foundation | Google addresses the two loudest complaints: URL hijacking and Google control |
| 2020 | Google announces the Page Experience update: Core Web Vitals will replace AMP as the Top Stories gate | The writing is on the wall |
| 2021 | Rollout completes: AMP is no longer required for Top Stories, and the AMP badge disappears from results | The two incentives that drove adoption are gone the same year |
| 2021–2023 | Major platforms and publishers quietly drop AMP; Twitter stops redirecting mobile users to AMP versions | Traffic to AMP variants shrinks; maintenance cost stays |
| Today | AMP remains a functioning open-source framework; Google neither requires nor rewards it | A fast responsive page achieves everything AMP promised, without the second codebase |
To be fair to the framework: AMP pages are genuinely fast, because the constraints outlaw the things that make pages slow. But Core Web Vitals now measure the outcome directly, so you can get the same credit with one well-built codebase instead of two.
How to check it on your own site
- Find out if you serve AMP at all: view source on a few templates and search for
rel="amphtml", or run a Screaming Frog crawl and check the AMP tab. WordPress sites: look for the AMP plugin, and test any URL with/amp/or?amp=1appended. - Measure what AMP actually earns you: Search Console → Performance → Search Appearance filter → AMP article / AMP non-rich results. If clicks are a rounding error, you have your answer.
- Validate what remains: paste an AMP URL into the validator at
validator.ampproject.orgor append#development=1and read the browser console. Invalid AMP is the worst of both worlds — maintenance cost, no eligibility. - Check canonical pairing: confirm each AMP page's canonical points at its real counterpart and that the counterpart's
amphtmllink resolves with a 200. - Compare speed like-for-like: run PageSpeed Insights on the AMP page and the canonical page. If your regular template already posts good LCP/INP/CLS, AMP is earning nothing.
Common audit mistakes (and fixes)
Recommending AMP adoption in 2026
Some audit tools still ding pages for "no AMP version." Ignore it. Fix the underlying speed problem on your real pages instead; that's what's actually measured.
Killing AMP without redirects
AMP URLs collect indexed status and backlinks. Deactivating a plugin and letting /amp/ URLs 404 leaks that equity. Fix: 301 each AMP URL to its canonical and treat retirement as a small site migration — map, redirect, monitor.
Leaving zombie AMP half-configured
The most common state I find: AMP plugin abandoned mid-setup, serving broken AMP variants with missing analytics and mangled ads. Fix: either maintain it properly or retire it deliberately. The middle state costs money silently.
Forgetting analytics parity
AMP pages need their own <amp-analytics> configuration. Teams routinely "lose" mobile traffic that was actually landing on untagged AMP pages served from the AMP Cache. Fix: before drawing any conclusions from a traffic dip, check whether AMP variants exist and whether they're tagged.
Assuming AMP equals structured data
Top Stories eligibility always needed valid Article markup too, and still does — on regular pages now. AMP never was a substitute for schema.
FAQ
Should a new site use AMP today?
Almost certainly not. The ranking incentives are gone, and modern frameworks plus sane image handling get you the same speed. The exception is narrow: if a partner or platform you distribute through still consumes AMP, or you're deep in AMP for Email.
Will removing AMP hurt my rankings?
Not inherently — Google treats the canonical page as the page. The risk is entirely in execution: broken redirects, lost analytics, and internal links still pointing at dead AMP URLs. Retire it with a redirect map and the risk is close to zero.
Is AMP a ranking factor?
No, and it never was one directly — it was an eligibility requirement for specific features (Top Stories on mobile), which is a different thing. That requirement ended in 2021. Speed matters; the AMP label does not.
What is AMP for Email?
A separate use of the same component model: interactive emails (forms, carousels, live content) supported by Gmail and a few other providers. It lives on independently of AMP's search story — evaluate it as an email-engagement tool, not an SEO one.
Why do I still see google.com/amp/ URLs?
Cached AMP documents served from Google's AMP Cache. They thin out as pages drop AMP or as Signed Exchanges show the origin URL, but old links and some surfaces keep the cache URLs alive. The canonical still gets the credit.
Claude Vincent is a technical SEO consultant focused on crawlability, rendering, and AI-search visibility. He writes the field guides and case studies at SEO ProCheck, with a bias toward the durable, unglamorous work that decides whether search engines and AI answer engines can actually read and cite a site.
About SEO ProCheck
Technical SEO consulting and GEO strategy with 20 years of enterprise experience. Case studies, resources, and tools for search and AI visibility.
Work With Me
Technical SEO audits, GEO strategy, site migrations, and international SEO. Hourly consulting for teams who need hands-on support, not just reports.
Subscribe to our newsletter!
