What AMP was, and why everyone adopted it
AMP (originally Accelerated Mobile Pages) is an open source framework Google announced in October 2015. The pitch: build a parallel, heavily restricted version of each page (limited HTML, a mandated JS runtime, no custom JavaScript, inline size-capped CSS) and let Google serve it from its own AMP cache so it loads near-instantly on mobile.
The technology was never the real story. The distribution deal was. From early 2016, the mobile Top Stories carousel, the most valuable block of news real estate on any phone screen, was effectively AMP-only. If you were a publisher, you did not adopt AMP because you loved the framework; you adopted it because opting out meant vanishing from where mobile news traffic lived. Plenty of publishers spent a hell of a lot of engineering budget maintaining a second rendering stack for exactly that reason.
Along the way the project tried to soften its rough edges: governance moved to the OpenJS Foundation in 2019, and signed exchanges made it possible to show the publisher's own URL instead of a google.com/amp address. Both were responses to the same persistent criticism, that AMP put Google between publishers and their readers.
June 2021: the requirement disappears
The Page Experience update, which rolled out from June 2021, changed the deal. Google opened Top Stories eligibility to any page that meets Google News content policies, dropped AMP as a requirement, and removed the AMP badge from mobile search results. Google's own Search Central documentation from that rollout is explicit: AMP is no longer required for Top Stories, and using AMP grants no ranking advantage over any other page that performs equally well.
That last part deserves emphasis because it is still widely misunderstood: AMP was never a direct ranking signal even before 2021. The benefits were always indirect: speed (which feeds real ranking signals like Core Web Vitals) and carousel eligibility (which was a distribution gate, not a ranking boost). Once the gate came down, the entire SEO case for AMP reduced to "it makes pages fast," and you do not need a parallel page format to make pages fast.
A short history you can cite in meetings
| When | What happened | Why it mattered |
|---|---|---|
| Oct 2015 | Google announces the AMP project | Response to slow mobile web and to Facebook Instant Articles |
| Feb 2016 | AMP pages start appearing in mobile Top Stories | Carousel becomes effectively AMP-only, forcing publisher adoption |
| 2019 | Project joins the OpenJS Foundation; signed exchanges show origin URLs | Damage control on governance and URL criticism |
| June 2021 | Page Experience update: AMP requirement and badge removed | Any page meeting Google News policies can enter Top Stories |
| Late 2021 onward | Twitter stops linking to AMP versions; major publishers begin dropping AMP | The distribution case erodes on every front |
How to exit AMP without hurting yourself
Dropping AMP is a small migration, and sloppy exits do real damage. The sequence that works:
- Reach speed parity first. Confirm your canonical mobile pages pass Core Web Vitals in the field, using the CrUX data in Search Console's Core Web Vitals report and PageSpeed Insights, not just lab scores. If AMP is currently the only fast version you have, fix that before removing it.
- Remove the pairing. Delete the
<link rel="amphtml">tag from canonical pages so Google stops discovering AMP versions. - 301 every AMP URL to its canonical. Do not 404 them. AMP URLs hold backlinks, social shares, and bookmarks. Redirect /amp/ paths or ?amp parameters to the standard page, one hop.
- Watch the reports. The AMP report in Search Console should trend to zero as pages drop out. Track mobile clicks and Top Stories visibility for your key sections through the transition; a dip that recovers within weeks is normal, a sustained drop means a redirect gap.
- Crawl to confirm. A Screaming Frog crawl filtered to your old AMP URL pattern verifies every one redirects correctly and nothing internal still links to them.
DO and DON'T
- Get canonical pages passing Core Web Vitals before touching AMP
- 301 every AMP URL to its canonical equivalent
- Remove rel=amphtml tags when you exit
- Monitor GSC's AMP and Core Web Vitals reports through the transition
- Treat the exit as a mini migration with a checklist and an owner
- Adopt AMP for a new site expecting a ranking benefit
- 404 or 410 AMP URLs that hold backlinks and shares
- Delete AMP while your canonical pages still fail CWV on mobile
- Assume Top Stories traffic is safe without checking News policy compliance
- Leave orphaned AMP pages live and indexable, duplicating every article
FAQ
Is AMP dead?
Will removing AMP hurt my rankings?
Do I still need AMP for Google Top Stories?
What about AMP for email or AMP ads?
We are a news publisher with deep AMP integration. Should we rush the exit?
An advanced SEO audit measures your real mobile performance, maps your AMP footprint, and gives you a safe, sequenced removal plan.
Source: https://www.seoforgooglenews.com/p/lets-talk-about-amp
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!
