Is AMP still relevant for boosting your mobile SEO?

What is AMP and why did Google launch it?

Accelerated Mobile Pages (AMP) is a restricted HTML framework developed by Google to force websites to load quickly on mobile. The principle is to drastically limit JavaScript, CSS, and heavy media, then serve the pages via a Google CDN. The declared goal? To improve the user experience on mobile.

In practice, AMP has primarily benefited news publishers by offering them a priority visibility in the mobile Top Stories carousel. This incentive led thousands of sites to adopt the format, despite major technical constraints: double development, costly maintenance, loss of functionalities.

What types of sites does Mueller refer to regarding AMP?

Mueller's statement mentions published content as the main use case. Specifically: blogs, media, news sites. These formats naturally benefit from lightweight HTML as they are mostly textual.

He also mentions “other types of sites” but remains vague. An e-commerce site with dynamic filters, a shopping cart, comparators? A SaaS with interactive dashboards? AMP quickly becomes a technical nightmare once you step outside pure editorial content. Mueller does not clarify these limitations, leaving ambiguity about the actual relevance of the framework.

What is the real connection between AMP and ranking?

Google has always maintained that AMP is not a direct ranking factor. However, for years, the mobile Top Stories carousel was reserved for AMP pages, creating a de facto SEO advantage. Since 2021, this restriction has lifted: non-AMP pages can also appear there if they meet the Core Web Vitals.

The result: AMP's main argument collapses. If a well-coded fast mobile page reaches the same performance thresholds, why impose the AMP constraint? Mueller does not answer this question in his statement, which speaks volumes about Google's current position.

• AMP imposes a restricted HTML served via Google's CDN to ensure speed and lightweight
• Initially reserved for editorial content (news, blogs), its use in e-commerce or SaaS is still technically problematic
• No direct ranking boost, but historical advantage in mobile Top Stories until 2021
• Since Top Stories opened to non-AMP pages, the SEO interest in AMP has significantly diminished
• The real question is: AMP or native optimization to meet Core Web Vitals?

Does this statement reflect the ground reality?

To be honest, as of 2023-2024, AMP is largely abandoned by most sites that adopted it. Why? The technical constraints (double coding, limited JS compatibility, dependence on Google's CDN) no longer compensate for the lost SEO advantage.

Mueller refers to AMP as a "major topic in the future." This projection sounded accurate in 2016-2018 but no longer matches current observations. SEO audits show that sites that have abandoned AMP are not facing any ranking penalties, provided their standard mobile version is fast and meets the Core Web Vitals.

What critical nuances are missing from this statement?

Mueller does not mention that AMP creates URL fragmentation (AMP version vs canonical version), complicating analytics tracking, conversions, and sometimes the crawl budget. He also omits that Google itself has removed the AMP badge from search results, a sign that the initiative is losing weight.

[To be verified] The claim that AMP would be "relevant for other types of sites" lacks concrete examples. Can an e-commerce site truly maintain AMP without sacrificing its conversion funnel? Ground data suggests otherwise, unless major functional compromises are accepted.

In what cases does AMP still hold value today?

AMP can still serve pure editorial sites looking for a turnkey solution to speed up their mobile without investing in a complete technical overhaul. The framework enforces a strict discipline that mechanically guarantees good performance.

But be cautious: this convenience comes at a cost. You delegate to Google the hosting and caching of your content, you lose flexibility in design and functionality, and you multiply the complexity of your technical stack. For 90% of sites, optimizing the standard mobile version natively remains more cost-effective in the medium term.

Should you still implement AMP on a live site?

For a new project launched today, the answer is clear: no. Focus your efforts on native mobile optimization: image compression, CSS/JS minification, lazy loading, fast server, lightweight theme. These optimizations benefit all your pages, not just a parallel AMP version.

If you already have AMP in place, the question is different. Check in Google Search Console if your AMP pages are generating significant traffic. If AMP traffic accounts for less than 5% of your total mobile traffic, you can consider gradually removing the framework without major SEO impact.

How to migrate from AMP to a standard optimized mobile version?

First step: ensure that your canonical mobile version meets the Core Web Vitals (LCP < 2.5s, FID < 100ms, CLS < 0.1). Use PageSpeed Insights and Google Search Console to validate real ground metrics.

Next, gradually remove the rel=amphtml tags from your canonical pages and the rel=canonical tags from your AMP pages. Redirect the old AMP URLs with a 301 to their canonical equivalents. Monitor crawl logs to confirm that Googlebot recrawls and reindexes the standard versions correctly.

What mistakes to avoid during an AMP transition?

Classic mistake: removing AMP without first optimizing the standard mobile version. Result: sharp drop in Core Web Vitals, loss of positions in Top Stories if you benefited from it, mobile bounce rate skyrocketing.

Another pitfall: forgetting to clean up the duplicated structured data between AMP and canonical. If both versions send contradictory schema.org signals, Google may deprioritize your rich snippets. Always check with the rich results test after migration.

• Audit the Core Web Vitals of your standard mobile version before making any decisions
• Measure actual AMP traffic in Search Console (if < 5%, removal is conceivable)
• Optimize natively: WebP/AVIF images, lazy loading, CDN, server caching
• Gradually remove rel=amphtml tags and redirect AMP URLs with 301
• Verify structured data after migration to avoid duplicates
• Monitor crawl, indexing, and positions for 4-6 weeks post-migration