AMP Pages in 2026: Are They Still Worth It and When to Drop Them

AMP has not been a requirement for Google Top Stories since 2021. In 2026, AMP is relevant only for large news publishers with millions of pages; every other site gets a better return by optimising Core Web Vitals on the canonical version.

What AMP is and why Google effectively walked away from it

AMP (Accelerated Mobile Pages) is an open-source framework for creating lightning-fast mobile pages, launched by Google and Twitter in October 2015. The premise was straightforward: mobile internet was slow, pages were heavy, users were leaving — so the industry needed a standard that would force publishers to ship lean page versions with strict limits on JavaScript, CSS, and external resources.

From 2016 through 2021, Google tied AMP to Mobile Top Stories — the horizontal carousel block on the first page of mobile search results. Only AMP pages could appear there. For news publishers, the incentive was enormous: Top Stories delivered 30–60% of all organic traffic. Newsrooms adopted AMP not by choice but by necessity.

The framework had serious limitations from day one. AMP prohibits arbitrary JavaScript — which rules out interactive elements, A/B tests, and personalisation. Ad revenue on AMP pages ran 30–50% lower than on canonical versions. The URL in the browser showed as google.com/amp/... rather than the publisher's own domain — damaging brand recognition and complicating analytics. Publishers complained loudly. Regulators took notice. In April 2021, Google made the move the industry had been waiting for.

Google officially confirmed in 2021: Core Web Vitals — not AMP — are the ranking signal for Top Stories. Any page with good LCP, INP, and CLS scores can appear in the carousel without a single line of AMP code.

That decision is on record in the official Google blog post on Page Experience. From that point on, AMP became one possible technical approach rather than a mandatory condition for visibility.

AMP in 2026: what changed after the Top Stories priority was dropped

Five years after the rule change, the picture is settled. HTTP Archive data shows a steady decline in AMP adoption: around 1.8% of tracked sites used AMP in 2021; by 2026, fewer than 0.6% do. No mass return to AMP has happened, and none will.

Other things that have shifted since 2021:

• Google Search Console no longer surfaces AMP as a standalone section in its newer reports. AMP Coverage Reports still exist but carry less weight in the overall site picture.
• AMP validation tooling (amp.dev/validator) continues to function, but Google no longer actively promotes it.
• The Google AMP Cache (cdn.ampproject.org) is still live — but using it is now a publisher's choice, not a search requirement.
• Core Web Vitals are the central technical signal. LCP, INP, and CLS measurably affect rankings — and you can hit good scores without AMP.

In our practice, AMP is already irrelevant for 95% of sites, except large news publishers with very specific operating conditions. We helped several news sites migrate off AMP, and none lost positions in Top Stories — provided Core Web Vitals were in good shape before AMP was switched off.

AMP pros and cons in 2026 — comparison table

Before deciding whether to keep AMP or drop it, it helps to look at an honest breakdown of the trade-offs in current conditions.

When AMP still makes sense: 3 real-world cases

Despite the broader trend away from AMP, there are three situations where keeping it in 2026 is genuinely justified.

Case 1: Large news publisher with millions of pages

If you have 500,000+ articles and limited engineering resources, AMP can be the most realistic way to maintain acceptable Core Web Vitals across the board. Newsrooms at that scale — Reuters, the Associated Press, large regional outlets — continue using AMP not for any ranking edge, but for guaranteed speed on weak mobile connections in regions where slow 3G is the norm.

Case 2: Site with a poorly optimised canonical version

If your LCP exceeds 4 seconds, CLS is above 0.25, and you lack the technical bandwidth for a deep optimisation sprint — AMP can be a temporary measure to hold on to Top Stories traffic while you fix the underlying issues. Think of it as a bridge, not a destination. Our guide to Core Web Vitals: LCP, INP, and CLS walks through the specific fixes.

Case 3: Markets with a significant share of slow mobile connections

For sites targeting audiences in sub-Saharan Africa, South Asia, or rural areas where 3G is standard, Google CDN caching through AMP provides real speed gains. Even here, though, Service Workers and PWA are increasingly the preferred approach — they deliver comparable speed without AMP's content and monetisation restrictions.

How to drop AMP without losing traffic

Removing AMP is a technical process with a specific order of operations. Getting that order wrong can result in 404 errors for AMP URLs still in Google's index, or a temporary dip in Top Stories traffic.

Step 1: Check Core Web Vitals on your canonical page

Before disabling AMP, confirm that LCP < 2.5s, INP < 200ms, and CLS < 0.1 on mobile. Use PageSpeed Insights and Chrome UX Report data in Google Search Console. If scores fall short, fix them first — then disable AMP. Our Mobile-First Indexing readiness checklist covers the mobile requirements in detail.

Step 2: Remove rel=amphtml from the canonical page

Find the <link rel="amphtml" href="..."> tag in your template or CMS and remove it from all canonical pages. This severs the relationship between AMP and canonical versions — Google stops following the link between them and begins treating AMP URLs as standalone pages, which is the precondition for removing them from the index.

Step 3: Set up 301 redirects from AMP URLs

For all AMP URLs (typically /amp/ or ?amp=1) set up 301 redirects to the canonical page. Server examples:

Step 4: Notify Google via Search Console

In Google Search Console, use URL Inspection to request indexing for several key pages. Check your Sitemap — AMP URLs must not remain there. If your CMS auto-generates the Sitemap, confirm that AMP URLs are gone after you deactivate the plugin.

Step 5: Monitor traffic and Coverage for 4–6 weeks

Watch the Performance (Mobile) and Coverage reports in GSC. Within 2–3 weeks, AMP URLs should disappear from the Coverage report. After 4–6 weeks you will know whether traffic levels have held. With good Core Web Vitals in place, the impact is typically negligible.

AMP alternatives: PWA, Core Web Vitals, Prerender

If AMP is no longer relevant for you — or you never adopted it — three modern approaches address the same goals without AMP's constraints.

Core Web Vitals optimisation

This is the primary path for the vast majority of sites. LCP, INP, and CLS are genuine ranking signals, and you can improve them without restructuring your site architecture:

• LCP — optimise images (WebP, AVIF), use a CDN, add preload for hero images. Target: < 2.5s.
• INP — minimise JavaScript, break up long tasks, use requestIdleCallback for non-critical operations. Target: < 200ms.
• CLS — set explicit dimensions for images and video, avoid injecting content above existing elements. Target: < 0.1.

Progressive Web App (PWA)

A PWA is a web application with native-like capabilities: offline mode via Service Workers, push notifications, home-screen installation. PWA does not accelerate the first load as dramatically as AMP with Google's cache, but it delivers a substantially better overall experience — particularly for returning users. For content-heavy sites it is the most future-proof path away from AMP.

Prerender.io and Static Site Generation

For sites built on heavy JavaScript frameworks (React, Vue, Angular), prerendering is an effective solution: the server renders HTML in advance and returns a complete page to Googlebot without the delay of JavaScript execution. Static Site Generation (SSG) through Next.js or Gatsby achieves a similar result — but for all users, not just crawlers. Both approaches can bring Core Web Vitals well within Google's thresholds without any AMP involvement.

Frequently asked questions

Does AMP still give a ranking advantage in Google search in 2026?

No. Google removed the AMP requirement for Mobile Top Stories in 2021. Any page with good Core Web Vitals can appear in Top Stories. AMP provides no ranking priority — it is simply one way to achieve speed.

Should a new website implement AMP in 2026?

For most sites — no. If you correctly optimise Core Web Vitals on the canonical version of your pages, AMP is unnecessary. The exception is large news publishers with millions of pages where Google's AMP cache helps with speed on slow mobile networks.

How do you remove AMP without losing traffic?

The core sequence: achieve good Core Web Vitals on the canonical page, remove rel=amphtml, set up 301 redirects from AMP URLs to canonical, notify Google via GSC, and monitor traffic for 4–6 weeks. With good CWV scores in place, traffic loss is typically negligible.

What is better — AMP or PWA?

PWA and AMP solve different problems. PWA delivers a full app experience: offline mode, push notifications, home-screen installation. AMP is exclusively about fast loading of static pages. In 2026, most sites choose Core Web Vitals optimisation over either approach.