AMP Mobile SEO: A Practical Guide for 2026

The short answer

AMP is not a ranking factor, and Google indexes AMP pages like any other page. Speed is what matters, and Google now measures it through Core Web Vitals on every page. Keep AMP only if your AMP pages pass those measures and removing them costs more than keeping them; otherwise, drop AMP and fix speed on plain HTML.

Key takeaways

Google Search Central states that AMP itself is not a ranking factor; speed is, and the same standard applies to AMP and non-AMP pages.
AMP has not been required for the Top Stories carousel since the June 2021 page experience update.
Core Web Vitals thresholds are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1.
Most business sites should not build new AMP pages in 2026; standard HTML that passes Core Web Vitals competes equally.
Removing AMP means deleting the AMP version, the canonical link and the paired structured data, then checking Search Console.

What AMP mobile SEO actually means

AMP, short for Accelerated Mobile Pages, is an open-source framework for building lightweight mobile pages. An AMP page is a stripped-down HTML page: it uses the AMP HTML specification, loads the AMP JavaScript library, and forbids most custom JavaScript, so the page renders fast on a phone. AMP mobile SEO is the practice of using that framework to make mobile pages fast enough to rank well.

The idea made sense when it launched in 2015. Phones were slower, mobile pages were heavy, and Google wanted a format that guaranteed speed. AMP gave publishers a shortcut: follow the rules, and the page would load almost instantly from Google's cache.

That bargain no longer exists. Google Search Central now states that it indexes AMP pages just like other web pages and applies the same standard to all pages, regardless of the technology used to build the page. AMP itself is not a ranking factor. Speed is a ranking factor, and Google measures speed the same way on AMP and non-AMP pages alike.

How an AMP page works

An AMP page is a second version of a normal page, built under strict limits. Three rules do most of the work:

Restricted HTML. The page uses AMP HTML, a subset of HTML with its own tags for images, video and ads. Custom JavaScript is not allowed; interactive features must use AMP components.
One JavaScript file. The AMP runtime library loads once and handles layout, so the browser does not wait on a chain of scripts.
A canonical link. Every AMP page points back to its canonical page with a link rel="canonical" tag, and the canonical page points to the AMP version with a link rel="amphtml" tag. That pairing tells Google the two pages are the same content.

Google can serve a valid AMP page from its cache, which is why AMP pages used to appear instantly in search results. The page also has to pass AMP validation: an invalid AMP page loses eligibility for AMP-related features.

For a publisher, the cost is a parallel site. Every article exists twice, every template change ships twice, and every feature that needs JavaScript has to be rebuilt as an AMP component or left out.

What Google says about AMP today

Google's current documentation is short and clear. Three statements from Google Search Central settle most debates about AMP in 2026:

AMP is not a ranking factor. The documentation states this directly: while AMP itself is not a ranking factor, speed is a ranking factor for Google Search.
AMP pages are indexed like any other page. Google Search indexes AMP pages just like other web pages and applies the same standard to all pages, regardless of the technology used to build the page. An AMP page can appear as a rich result, just like a standard page.
AMP is not required for Top Stories. Google removed the AMP requirement for the Top Stories carousel with the page experience update in June 2021. Since then, any page that meets Google News content policies and the page experience standard can appear there, and Google no longer shows the AMP badge in results.

What replaced AMP as the performance standard is Core Web Vitals, the three measurements Google uses to judge how a page feels to a visitor:

Metric	What it measures	Good threshold
LCP (Largest Contentful Paint)	How fast the main content loads	Under 2.5 seconds
INP (Interaction to Next Paint)	How fast the page responds to a tap or click	Under 200 milliseconds
CLS (Cumulative Layout Shift)	How much the page jumps around while loading	Under 0.1

These thresholds apply to every page, AMP or not. A standard HTML page that passes them competes equally with an AMP page that passes them. A slow AMP page loses to a fast standard page.

If you want the mobile picture in full, the mobile SEO versus desktop SEO guide explains how Google's mobile-first indexing changes what to check first, and the Core Web Vitals optimisation guide walks through the three metrics above in detail.

When AMP still earns its keep

AMP is not dead, and removing it is not always the right move. It still earns its keep in a few narrow situations:

A large news site with thousands of AMP articles already indexed. If the AMP versions rank, pass Core Web Vitals and cost little to maintain, there is no urgency to remove them.
A team with no developer time. If nobody is available to rebuild templates and fix speed on the standard pages, a working AMP setup is better than slow standard pages. Keep it until the rebuild is funded.

In each case the test is the same: do the AMP pages pass Core Web Vitals, and does keeping them cost less than removing them?

When AMP costs more than it saves

For most other sites, AMP is now a cost with no matching benefit. Watch for these signs:

Your standard pages already pass Core Web Vitals. If the normal pages are fast, the AMP versions add nothing. They are duplicate pages to maintain, validate and debug.
Features keep breaking on AMP. Paywalls, consent banners, interactive tools and ad formats all need AMP-specific versions.
Analytics never quite match. AMP pages load through a different path, so traffic, conversions and revenue attribution need extra work to line up with the canonical pages.

A small business site, a SaaS marketing site or a local service site almost never belongs in the "keep AMP" group. Those sites have a handful of templates, no Top Stories ambitions and no AMP traffic worth protecting. For them, the right move is to drop AMP and put the effort into the standard pages.

How to remove AMP without losing rankings

Removing AMP is a migration, and migrations go wrong when steps are skipped. Follow this order:

Fix the standard pages first. Measure every template in PageSpeed Insights and Search Console. Do not remove AMP until the standard version of each page passes Core Web Vitals.
Remove the AMP version and the link to it. Delete the AMP page and remove the link rel="amphtml" tag from the canonical page. Leave the canonical page itself untouched.
Redirect the AMP URLs. Point each old AMP URL at its canonical page with a 301 redirect. Do not let AMP URLs return 404s, and do not redirect them all to the homepage.
Match the structured data. If the AMP page carried structured data, make sure the same markup exists on the canonical page. Google's guidance is to use the same structured data markup across both the canonical and AMP pages, so the canonical page must carry it alone after the move.
Check Search Console. Use the AMP status report to confirm the AMP pages drop out of the index, and watch the Core Web Vitals report for the canonical pages over the following month.
Watch traffic by template, not by day. Compare the same pages week over week. A single bad day after a migration means little; a template that loses traffic for three weeks means something broke.

A worked example: a news site drops AMP

Take a hypothetical news site with 2,000 AMP articles. Its AMP pages load with an LCP of 1.8 seconds, but its standard article pages load with an LCP of 4.1 seconds because of a heavy ad script and uncompressed hero images.

Dropping AMP today would swap a 1.8-second experience for a 4.1-second one. That is a speed loss, and speed is a ranking factor, so rankings would likely fall even though AMP itself was never the ranking factor. The right order is:

Remove the ad script from the critical path and compress the hero images. The standard page LCP falls from 4.1 seconds to 2.2 seconds, inside the 2.5-second threshold.
Fix the layout shift from late-loading ads. CLS falls from 0.35 to 0.05, inside the 0.1 threshold.
Only then delete the AMP versions and redirect the AMP URLs to the canonical pages.

The cost is a few weeks of developer time on the standard templates. The saving is a parallel site that no longer needs maintaining: one template instead of two, one analytics setup instead of two, and no AMP validation errors to chase.

AMP mistakes that waste time

Building new AMP pages in 2026. New projects should build fast standard HTML. Starting with AMP means starting with a second version of every page for no search benefit.
Removing AMP before fixing speed. The AMP version may be the only fast page you have. Measure first, migrate second.
Forgetting the redirects. AMP URLs that 404 waste crawl budget and break any links pointing at them.

AMP terms worth knowing

AMP HTML: the restricted version of HTML that AMP pages are written in. Custom JavaScript is not allowed.
Canonical page: the main, non-AMP version of a page. The AMP version points to it, and it points back to the AMP version.
AMP Cache: Google's cache that stores and serves valid AMP pages. It is what made AMP pages appear instantly in search results.
AMP validation: the check that an AMP page follows the AMP HTML specification. Invalid pages lose eligibility for AMP-related features.
Core Web Vitals: LCP, INP and CLS, the three measurements Google uses to judge page experience on every page.

What to do next on your own site

☐ Check whether your site serves AMP pages at all. Search Console's AMP status report lists them.
☐ Measure your standard pages in PageSpeed Insights. Note LCP, INP and CLS for each template.
☐ If the standard pages pass and the AMP pages add nothing, plan the removal: redirects first, then deletion.
☐ If the standard pages fail, fix speed before touching AMP.
☐ After removal, watch Search Console for a month and compare traffic by template, not by day.

For the numbers behind the decision, the Google Search Console versus Google Analytics guide shows how to check whether your traffic data is trustworthy before you act on it.

Common questions

Is AMP a ranking factor for mobile SEO?

No. Google Search Central states that AMP itself is not a ranking factor, while speed is. Google indexes AMP pages just like other web pages and applies the same standard to every page, regardless of the technology used to build it.

Do I need AMP to appear in Top Stories?

No. Google removed the AMP requirement for Top Stories with the page experience update in June 2021. Any page that meets Google News content policies and the page experience standard can appear there.

Should I remove AMP from my site?

For most business sites, yes, once the standard pages pass Core Web Vitals. Keep AMP only if your AMP pages already perform well, your team has no budget to rebuild them, and the AMP versions carry traffic you cannot risk during a migration.

What should I do instead of AMP?

Build fast standard HTML pages and measure them with Core Web Vitals: LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1. Fix images, third-party scripts and layout shifts first, since those decide the score on most pages.

Do AMP pages still work in Google Search?

Yes. AMP pages still work and still get indexed, and they can appear as rich results like any other page. They simply earn no ranking boost, badge or special placement for being AMP.

Sources

Adziq sells marketing services and does not accept payment for placement in its articles. See our editorial policy.