What is Google AMP and how does it work?

Accelerated Mobile Pages (AMP) was one of the most talked-about SEO technologies of the late 2010s. Google launched it in October 2015 as a way to make mobile web pages load instantly, and for several years, adopting AMP was the fastest path to getting into Google’s Top Stories carousel and earning the lightning-bolt badge in mobile search results.

That era is over. In June 2021, Google’s Page Experience update removed AMP as a requirement for Top Stories. A few months before that, Google had already removed the AMP badge from search results. By 2026, major publishers (The Washington Post, CNBC, Vox Media, Bustle Digital Group, and many others) have migrated off AMP, and Google’s own guidance is that Core Web Vitals on standard HTML now drives the performance story AMP used to own.

This article explains what AMP is, how it still works, and whether you should use it in 2026. Short answer: for new sites, almost certainly no. If you’re already on AMP, the question is when to migrate, not whether. For a broader look at how the modern performance-SEO landscape came together, our getting started with SEO guide covers the current fundamentals.

What AMP Is

AMP is an open-source framework (originally stewarded by Google, transferred to the OpenJS Foundation in 2019) for building stripped-down, ultra-fast web pages. An AMP page has three core components:

• AMP HTML — a restricted subset of HTML with custom tags like <amp-img>, <amp-video>, and <amp-iframe> that enforce performance-safe patterns. Many normal HTML tags are disallowed, and author-written JavaScript isn’t permitted at all.
• AMP JS — a JavaScript library, loaded from a Google CDN, that implements the custom AMP tags and manages resource loading. Everything it does is asynchronous, so nothing blocks page rendering.
• AMP Cache — originally a Google-operated CDN that cached validated AMP pages and served them from cdn.ampproject.org. Bing runs its own AMP cache. The Google AMP Cache made AMP pages load “instantly” from Google search results because the page was pre-fetched and served from Google’s own infrastructure.

The trade-off: you give up a lot of design and functional flexibility, and in exchange you get guaranteed fast loading and (historically) preferential SEO placement. The technology itself still works. The SEO payoff largely doesn’t.

How AMP Works

AMP’s speed comes from a series of engineering decisions that any site could theoretically copy, but that AMP enforces strictly:

• No synchronous JavaScript. Nothing script-related blocks page rendering. Third-party JS runs only inside sandboxed iframes.
• External resources declare their size up front. Images, videos, ads, and embeds all declare their dimensions in HTML so the browser can lay out the page without waiting for them to download. This eliminates layout shifts as content loads in.
• CSS is inline and capped at 75KB. (The original limit was 50KB; Google raised it to 75KB in 2022.) Inline CSS eliminates an extra HTTP request in the critical rendering path.
• Web fonts load alongside the rest of the page. AMP’s restrictions prevent render-blocking font requests.
• Resources prioritize by visibility. AMP downloads above-the-fold content first and lazy-loads things the user hasn’t scrolled to yet.
• Animations are GPU-accelerated only. AMP CSS allows transform and opacity animations (cheap on modern browsers) but not animations that trigger full-page re-layout.
• The Google AMP Cache prerenders search results. When an AMP link appears in Google results, Google fetches the page in the background and serves it from its own CDN so the perceived load time is near zero.

All of this was innovative in 2015-2016. In 2026, modern frontend frameworks (Next.js, Astro, Nuxt) and optimized hosting (Vercel, Cloudflare Pages, Netlify) achieve comparable speed without AMP’s restrictions, and Google now measures real-world performance through Core Web Vitals rather than giving AMP pages a special fast-track.

Why Google Pulled Back from AMP

AMP’s decline traces to three developments.

The June 2021 Page Experience update was the turning point. Google announced that the Top Stories carousel would no longer require AMP, and that pages passing Core Web Vitals thresholds would be eligible regardless of whether they used AMP. Publishers who had invested heavily in AMP specifically for Top Stories visibility suddenly had no reason to keep the extra infrastructure.

The AMP badge disappeared from mobile search results around the same time. The distinctive lightning-bolt icon that told users “this page will load instantly” was quietly retired. Without the visual differentiation, AMP’s perceived user benefit also faded.

Publisher sentiment turned sharply negative. AMP had always required maintaining two versions of every page (a canonical version and the AMP version), which doubled development and editorial workload. It also routed traffic through Google-controlled URLs (google.com/amp/s/yoursite.com/...) in ways that muddied analytics, cookies, and brand perception. Major publishers led an industry conversation about whether AMP represented an acceptable trade-off between speed and independence. The answer, increasingly, was no.

Google itself shifted focus. The team behind AMP moved to other projects. The AMP Project’s governance transferred to the OpenJS Foundation in 2019. AMP Stories were renamed to Web Stories in 2020 and positioned as a content format rather than a speed framework. In 2023, Google’s own technical guidance stopped recommending AMP for most use cases.

Should You Use AMP in 2026?

For new sites: no. The performance benefits AMP provides can be achieved with modern frameworks and good hosting, without the editorial overhead or the search-results URL rewriting. If you’re building a content site today, focus on Core Web Vitals (LCP, INP, CLS) on your standard HTML and move on.

For existing AMP sites: plan a migration. The question is not whether AMP is still worth it, but when you can budget the work to retire it. Migration steps typically include removing the <link rel="amphtml"> declarations, taking down the AMP versions of pages, and setting up 301 redirects from old AMP URLs to the canonical pages. Test Core Web Vitals on the canonical version before decommissioning anything.

Edge cases where AMP may still make sense:

• Publishers whose audience is heavily ad-funded and whose AMP ad stack is more profitable than the non-AMP equivalent. This is a shrinking category as most ad tech has caught up on the non-AMP side.
• Sites with extremely limited development resources where maintaining AMP’s restricted template is actually easier than building a fast responsive site from scratch. Rare.
• Specific AMP components (like amp-story / Web Stories) still have niche uses, though Web Stories’ broader momentum has also slowed.

For everyone else, the 2026 answer is straightforward: standard HTML plus good frontend engineering beats AMP on every metric that matters now.

Modern Alternatives to AMP

The path AMP promised (fast mobile pages, fewer layout shifts, better Core Web Vitals) is achievable in 2026 without AMP’s constraints:

• Static Site Generation (SSG) and Server-Side Rendering (SSR). Frameworks like Next.js, Astro, Nuxt, and SvelteKit produce HTML that’s already optimized for fast first paint. Astro’s partial-hydration model is particularly AMP-like in its philosophy but works without AMP’s tag restrictions.
• Modern hosting and CDNs. Vercel, Cloudflare Pages, Netlify, and Fastly serve content from edge locations globally. This achieves the “instant load” effect that AMP Cache pioneered, without routing users through Google.
• Image optimization. Next-gen formats like AVIF and WebP, responsive image markup (srcset and <picture>), and lazy-loading (now native in every modern browser) replace amp-img‘s role.
• Core Web Vitals monitoring. Google Search Console’s Core Web Vitals report, PageSpeed Insights, and real-user monitoring (RUM) tools tell you where your pages actually fall short. Fixing specific issues beats the blunt instrument of adopting AMP.
• HTTP/2, HTTP/3, and preload. Standard modern browser and server features now do much of what AMP’s custom resource prioritization used to.

If you want a comprehensive 2026 baseline for a fast site, start with a modern framework on a good host, pass Core Web Vitals on the live site, and skip AMP entirely.

Frequently Asked Questions

Is Google AMP dead in 2026?

Technically, no. AMP still exists as a framework and AMP pages still work. Practically, yes — Google no longer gives AMP pages any ranking advantage, the AMP badge is gone, Top Stories no longer requires AMP, and most major publishers have migrated away. For all practical SEO purposes, AMP is no longer a priority or a necessity.

Does Google still rank AMP pages?

Google ranks AMP pages the same way it ranks any other page, based on relevance, quality signals, and Core Web Vitals. AMP itself provides no ranking boost. A well-optimized standard HTML page will rank identically to (or better than) the same content served as AMP.

Will removing AMP from my site hurt my SEO?

Probably not, as long as you migrate carefully. Use 301 redirects from AMP URLs to canonical pages, make sure the canonical version passes Core Web Vitals, and monitor impressions and clicks in Google Search Console for a few weeks after the change. The vast majority of sites that have retired AMP in 2022-2026 saw no SEO loss and often saw engagement metrics improve.

What replaced AMP as Google’s preferred speed optimization?

Core Web Vitals (LCP, INP, and CLS) measured on standard pages. Google wants fast pages; it no longer cares how you get there. Modern frameworks, good hosting, optimized images, and minimized JavaScript deliver the speed AMP promised, without AMP’s restrictions.

Are Web Stories (formerly AMP Stories) worth using?

Web Stories are still a supported content format and can appear in specific Google surfaces (Discover, Images, and Search). They’re worth considering only if your content genuinely fits the swipeable-story format. As a general SEO strategy, they’re a specialized tool, not a requirement.

Bottom Line

Google AMP was a decent answer to a real 2015 problem: mobile web pages loaded too slowly, and there was no practical way to force publishers to fix them. AMP enforced good performance practices by removing the option to do anything else. That framework worked for a few years, but it also created an industry-wide dependency on Google that publishers eventually pushed back against.

By 2021, Google had acknowledged that Core Web Vitals on standard pages was a better universal framework than AMP. By 2026, AMP has faded to the category of “interesting piece of SEO history that still technically exists.” If you’re running a site in 2026, put your effort into Core Web Vitals, a modern frontend stack, and good hosting. That’s where the performance-SEO payoff lives now. For related reading, see our guides on JavaScript and SEO and the best CMS for SEO in 2026, both of which cover the modern performance-first approach that replaced AMP.