Get a free consultation
Website Design

Is Google AMP Dead in 2026? What Changed and What to Use Instead

By Sigmato Editorial TeamUpdated 15 Nov 20269 min read

An adult woman working on a laptop while holding an iced drink, seated outside.

Key takeaways

  • AMP is not banned and AMP pages still rank, but Google Search gives them no special treatment. On 1 July 2026 Google confirmed AMP content ranks “just like any other web page”.
  • The two reasons most sites adopted AMP, Top Stories eligibility and the lightning-bolt badge, went away in 2021.
  • Keeping AMP now mostly means maintaining a second, restricted copy of every page.
  • The replacement is not a product. It is a short list of habits: good Core Web Vitals on your normal pages, lean JavaScript, optimised images, caching and a fast server.
  • If you decide to retire AMP, do it with 301 redirects and by removing the amphtml link, not by simply switching the plugin off.
An adult woman working on a laptop while holding an iced drink, seated outside.

The short answer

Is Google AMP dead? Not in the sense that it stopped working. AMP pages still load, still get indexed and still rank. But as a strategy, AMP is finished: it no longer wins you anything in Google Search that a well-built normal page cannot win, and it costs you a second version of your site to maintain. Most teams who still run it today are running it out of habit.

That is the honest 2026 position, and it is worth understanding how we got here, because the history tells you exactly what to do next.

What AMP was supposed to fix

Accelerated Mobile Pages was introduced around 2015 and wired into mobile search in early 2016. The pitch was simple: mobile pages were slow, so publishers could write a stripped-down version of each page in a restricted flavour of HTML, and Google would serve it from its own cache almost instantly. In return, AMP pages got a lightning-bolt badge in search results and, for a while, were effectively the ticket into the Top Stories carousel on mobile.

It worked, in a narrow way. Pages were fast because the rules made it hard to build them slow: limited JavaScript, fixed layouts, controlled third-party code. The trade-off was that you gave up control of design, tracking, advertising and forms, and you maintained two versions of the same page.

A timeline of how AMP lost its special status

When What changed Why it matters
2015 to 2016 AMP launched and was integrated into mobile search. Speed was rewarded, but only through the AMP format.
June 2021 Google’s page experience update began rolling out. AMP stopped being required for Top Stories, and the AMP badge was retired. The two biggest incentives disappeared. Normal pages with good Core Web Vitals could compete.
1 July 2026 Google’s Search documentation changelog records that it removed outdated references to the AMP viewer, the AMP Cache and signed exchanges. Search now links people directly to the publisher’s own AMP pages. Google adds that AMP content “will continue to rank just like any other web page”. The last piece of the original AMP delivery model, the Google-hosted copy, is gone from Search. What remains is simply a web page.

Notice what is not in that list: any announcement that AMP pages are penalised. They are not. The shift is that AMP is now neutral, and neutral is not a reason to carry the cost.

So should you remove AMP?

It depends on what AMP is doing for you today. Use this as a quick decision guide.

Your situation Recommendation
AMP is a second copy of your pages and your normal pages are slow Fix the normal pages first, then retire AMP. Removing AMP before fixing speed can make mobile worse.
Your normal pages already pass Core Web Vitals Retire AMP. You are paying maintenance cost for no search benefit.
AMP pages are broken or heavily out of date Retire AMP. A neglected AMP page is a liability, not an asset.
Your whole site is built on AMP and you have no resources to rebuild Plan a staged migration, template by template, starting with your highest-traffic pages.
An ad or publisher partner contractually requires AMP Keep it until the contract changes, but stop expanding it.

The real cost of keeping AMP

  • Two sources of truth. Every template change, new component and content fix has to be made twice and kept in sync.
  • Restricted features. Forms, custom scripts, consent tools, A/B testing and richer tracking are limited or need AMP-specific components.
  • Validation errors. A single invalid tag can stop a page being treated as valid AMP, and these errors tend to appear after a theme or plugin update.
  • Split analytics. AMP and canonical traffic can be recorded differently, which makes conversion analysis messy.
  • Design drift. The AMP version rarely looks exactly like your brand, which hurts trust when a visitor lands on it from search.

How to retire AMP safely (step by step)

The most common mistake is to deactivate the AMP plugin and walk away. The AMP URLs then return errors, and any links or search results pointing to them waste crawl budget and send visitors to dead pages. Do it in this order instead.

  1. Check content parity. The normal page must contain everything the AMP page did: text, images, structured data and internal links.
  2. Measure the normal page. Look at field data in Search Console’s Core Web Vitals report and in PageSpeed Insights. If the normal page is slow, fix that first (see the toolkit below).
  3. Add 301 redirects from every AMP URL pattern to its canonical page. On Apache that can look like this:
# Send /amp/ versions and ?amp parameters to the normal page
RewriteEngine On
RewriteRule ^(.+)/amp/?$ /$1/ [R=301,L]
RewriteCond %{QUERY_STRING} (^|&)amp(=1)?(&|$)
RewriteRule ^(.*)$ /$1? [R=301,L]

On nginx, the same idea is rewrite ^(.+)/amp/?$ $1/ permanent;. Test a handful of URLs before and after.

  1. Remove the AMP link tag from your canonical pages. The tag looks like <link rel="amphtml" href="https://example.com/page/amp/">. If you use a plugin, switch the plugin off only after the redirects are live.
  2. Clean up supporting code: AMP-specific analytics tags, ad units, consent configuration and any AMP-only sitemap entries.
  3. Update your XML sitemap so it lists only canonical URLs.
  4. Watch for two to four weeks. Check Search Console for crawl errors, coverage changes and Core Web Vitals, and check your server logs for requests to old AMP URLs that are not redirecting.

What to use instead of AMP

There is no single “AMP replacement” product. The point of AMP was fast pages, and fast pages are built from a handful of well-understood practices. Here is the toolkit we recommend, in the order that usually pays off.

1. Measure real users first

Use field data, not just lab scores. PageSpeed Insights shows Chrome user experience data for your URL and origin, and Search Console groups your URLs by Core Web Vitals status. Lab tools such as Lighthouse are good for diagnosing a problem, but real visitors decide whether the problem exists. Our guide to Core Web Vitals explains the three metrics in plain language.

2. Fix images (usually the biggest win)

  • Serve modern formats (AVIF or WebP) and responsive sizes with srcset and sizes.
  • Always set width and height so the layout does not jump (this protects Cumulative Layout Shift).
  • Lazy-load images below the fold, but never lazy-load the main image at the top. Give that one fetchpriority="high".

3. Keep JavaScript on a budget

The reason AMP pages were fast was mostly that they could not run much script. You can adopt the same discipline voluntarily: defer non-critical scripts, remove libraries you no longer use, split large bundles, and audit third-party tags (chat widgets, tag managers, A/B testing tools) because they often cost more than your own code. Slow responses to taps and clicks are measured by INP, which we cover in a separate guide on how to improve Interaction to Next Paint.

4. Make the server and network do less work

  • Use full-page caching and a CDN so most visitors never wait for your application to render a page.
  • Enable Brotli or Gzip compression and HTTP/2 or HTTP/3.
  • Set long cache lifetimes on versioned assets.

On WordPress this is usually a caching plugin plus a quality host. See our practical notes on WordPress speed optimisation.

5. Prefer server-rendered or pre-built pages

Pages that arrive as complete HTML paint sooner than pages that wait for a large JavaScript bundle to build the screen. Frameworks such as Next.js can render on the server or generate pages ahead of time, and a headless CMS lets editors keep a familiar interface. If you are weighing options, read Next.js vs React and what a headless CMS is.

6. Consider instant navigation with prerendering

Chromium-based browsers support the Speculation Rules API, which lets you tell the browser which pages a visitor is likely to open next so it can prepare them in the background. Used carefully on your most common journeys, this gives the “instant” feel AMP was known for, without a separate format. Google documents it at developer.chrome.com. Keep it conservative: prerendering uses bandwidth and can distort analytics if not set up correctly.

7. Add app-like resilience where it fits

If your audience often has poor connections, a progressive web app adds offline support and caching rules you control. Our PWA development checklist covers what is worth building and what is not.

AMP constraints and their modern equivalents

What AMP forced What you do instead
Almost no custom JavaScript A script budget, deferral and regular third-party audits
Required image dimensions Set width and height on every image
Cached copy served by Google Your own CDN and full-page caching
Inline, size-limited CSS Critical CSS plus one small stylesheet
Lazy loading managed by the framework Native loading="lazy" below the fold
A separate AMP template One responsive template that is already fast

What about news publishers and Top Stories?

Publishers were the group most tied to AMP. Since the 2021 page experience update, AMP is not a requirement for Top Stories, and good page experience signals are what matter alongside the usual content and policy requirements. If your newsroom still produces AMP only because of that old rule, you can plan the same migration described above, starting with your highest-traffic templates.

How to know the move worked

  • The Core Web Vitals report in Search Console shows the same or a better share of “good” URLs.
  • Impressions and clicks for your canonical URLs hold steady after the AMP URLs drop out of the index.
  • Your analytics no longer splits one article across two URL patterns.
  • Crawl stats show fewer requests to redirected URLs over time.

You can also measure interaction speed on real devices with Google’s open-source web-vitals library.

What we would do on a typical site

If you asked us to look at a site with an AMP layer today, we would not start with AMP at all. We would run a field-data audit, fix the biggest image and script problems on the normal templates, confirm the Core Web Vitals report is healthy, and only then schedule the AMP retirement with redirects and a monitoring window. That order protects your traffic and usually leaves the site faster than AMP ever did. If you want a hand with that, our website maintenance and performance support and CMS website development teams do this regularly, and you can talk to us about an audit.

Frequently asked questions

Is AMP officially discontinued by Google?

No. AMP pages still work and are indexed. What changed is that Google Search treats them like any other page: it removed old references to the AMP viewer, AMP Cache and signed exchanges from its documentation on 1 July 2026, and says AMP content ranks like any other web page.

Will removing AMP hurt my rankings?

Not by itself. AMP gave no ranking advantage. The risk is in how you remove it: redirect AMP URLs to the canonical page, remove the amphtml link, and make sure the normal pages have good Core Web Vitals before you switch AMP off.

Do I need AMP to appear in Top Stories?

No. Google stopped requiring AMP for Top Stories with the page experience update in 2021. Eligibility depends on content and policy requirements together with page experience, not on the AMP format.

What should I do with my AMP plugin?

Add 301 redirects from your AMP URLs to the normal pages first, confirm they work, then deactivate the plugin. Deactivating first leaves old AMP URLs returning errors.

Is there a direct replacement for AMP?

No single product. Use fast, server-rendered pages, lean JavaScript, optimised images, caching and a CDN, and measure real users with Core Web Vitals. Optional extras include prerendering likely next pages.

How long should I monitor after retiring AMP?

Two to four weeks is a sensible minimum. Watch Search Console coverage and Core Web Vitals, your analytics and your server logs for requests to old AMP URLs.

Sources and further reading

Sigmato Editorial Team

Written by

Sigmato Editorial Team

The Sigmato Editorial Team is made up of software engineers, UI/UX designers and AI specialists at Sigmato Solutions Pvt Ltd in Bengaluru, India and the UK. We write practical guides on web, mobile, cloud and AI development, drawing on the products we design and build for startups and enterprises worldwide.

Last updated 15 November 2026 · Talk to our team