What Is AMP? Accelerated Mobile Pages, Honestly Reviewed

Jul 27, 2026 · SEO Glossary

Let me say the quiet part first: you almost certainly don't need AMP. That wasn't always true, and the story of how it stopped being true is worth ten minutes of your time — especially if you're maintaining a site that still runs it.

So, what is AMP? AMP stands for Accelerated Mobile Pages, an open-source HTML framework Google launched in late 2015. The idea: publishers create a parallel, stripped-down version of each page using a restricted subset of HTML, a special JavaScript library, and hard limits on what the page can do. In exchange, those pages load almost instantly on mobile — partly because of the restrictions, and partly because Google pre-loaded and served them from its own cache the moment they appeared in search results.

What is AMP actually doing under the hood?

An AMP page is regular HTML with strict rules bolted on:

• No custom JavaScript. Interactivity comes only from pre-approved AMP components (amp-img, amp-carousel, amp-analytics and friends).
• Size-capped, inline CSS. All styles live in a single inline block limited to 75KB. No external stylesheets.
• Mandatory dimensions on media. Every image and embed declares its size up front, so the layout never shifts while loading — AMP was enforcing what we now measure as Cumulative Layout Shift years before that metric existed.
• The Google AMP Cache. Valid AMP pages got copied to Google's servers and pre-rendered from search results, which is why tapping an AMP result felt instantaneous. It's also why the URL bar showed google.com/amp/... instead of the publisher's domain — a detail publishers hated from day one.

A typical setup meant maintaining two versions of every article: the normal page at example.com/article/ and an AMP twin at example.com/article/amp/, linked to each other with rel="amphtml" and canonical tags.

The carrot: why everyone adopted it anyway

Nobody built AMP pages for fun. They built them because from 2016 to 2021, Google's Top Stories carousel — the prime news real estate at the top of mobile search — required AMP. No AMP, no carousel, no matter how good your journalism or how fast your regular pages were. For news publishers that was existential, so the industry complied. At its peak, AMP powered billions of pages, and platforms like WordPress made it a one-plugin install.

The complaints piled up in parallel: publishers lost their URLs to the Google cache, analytics got messier, ad revenue on AMP pages often ran lower, and maintaining two page versions doubled the QA surface. The deeper objection was strategic — a single company's format had become a de facto toll booth for search visibility.

What changed: the page experience update

In June 2021, Google rolled out the page experience update and removed the AMP requirement for Top Stories. Eligibility switched to metrics any page can meet: the Core Web Vitals — loading (LCP), interactivity (now INP, which replaced FID in March 2024), and layout stability (CLS). Google also removed the AMP lightning-bolt badge from search results and stopped requiring the AMP cache.

The logic was sound: AMP was always a means to an end, and the end was fast, stable pages. Once Google could measure that outcome directly from real Chrome user data (the CrUX dataset), the format stopped mattering. A well-built regular page that hits its vitals gets everything AMP used to gate.

The years since have been a slow exodus. Major publishers — The Washington Post, Twitter's link handling, countless mid-size outlets — dropped AMP. The project moved to open governance, development slowed, and in 2026 AMP survives mostly as legacy infrastructure on sites that adopted it a decade ago and haven't gotten around to removing it.

Should any site adopt AMP today?

For nearly everyone: no. The honest decision tree is short. If you're building new, invest directly in performance — optimize images, cut JavaScript, use a CDN, measure with PageSpeed Insights and fix what it flags. You'll get AMP-level speed without maintaining a second codebase. If you run interactive features, e-commerce, or anything needing custom JavaScript, AMP was never a fit anyway.

The narrow exceptions: some ad-driven publishers still see acceptable monetization through AMP's ad pipeline and haven't prioritized migration, and AMP for Email (interactive emails in Gmail) is a separate technology that remains quietly useful. Neither applies to a typical business site, agency client, or blog.

Retiring AMP without breaking things

If you're maintaining a site that still serves AMP pages, removal is straightforward but has to be done in order — I've seen a rushed removal take out a site's article traffic for weeks because step three got skipped:

1. Confirm your regular pages perform. Check Core Web Vitals in Search Console and PageSpeed Insights first. If your normal mobile pages are slow, fix that before removing the fast versions.
2. Remove the rel="amphtml" link from your regular pages so Google stops discovering the AMP variants.
3. Redirect every AMP URL to its canonical page with a 301 redirect. This is the step people skip. AMP URLs are indexed, cached, and linked from other sites; letting them 404 throws that equity away and floods Search Console with errors.
4. Deactivate the AMP plugin or templates only after the redirects are live and tested.
5. Crawl the site afterward to catch stragglers — leftover /amp/ internal links, redirect chains, or orphaned AMP URLs still returning 200. A full-site crawl surfaces all of these quickly.

Expect the AMP URLs to fall out of Google's index over a few weeks. Traffic should transfer cleanly to the canonical pages if the redirects are one-to-one.

The lesson AMP leaves behind

Strip away the politics and AMP taught the industry something real: speed and layout stability are product features users notice. The framework enforced disciplines — sized images, minimal JavaScript, restrained CSS — that remain best practice on any page you build. AMP the format is fading; AMP the performance philosophy won so thoroughly that Google now measures it on every page on the web. Learn the philosophy, skip the framework.