Is it still worth investing in AMP for your SEO?

AMP was limited at the start, so what has changed?

At launch, AMP was primarily aimed at news sites and blogs looking to speed up load times for articles. The framework imposed strict limitations: limited JavaScript, restricted CSS, and proprietary components. This rigidity effectively excluded e-commerce sites, SaaS platforms, or interactive portals.

Mueller's statement indicates that AMP's capabilities have expanded. The framework now supports more ambitious use cases: product sheets, complex forms, and enriched user interfaces. However, Google does not specify which components enable these evolutions, nor to what extent historic technical limitations persist.

Why is Google emphasizing this evolution right now?

The context reflects a decline in AMP adoption within the SEO ecosystem. Since Core Web Vitals became the standard for measuring performance, many sites have abandoned AMP in favor of native optimizations. AMP-only Top Stories carousels have disappeared, reducing the competitive advantage of the format.

By repositioning AMP as a flexible technology, Google is likely trying to keep its framework in technical discussions. But this statement remains vague: no concrete examples of "new types of content," no data on comparative performance between AMP and non-AMP in organic visibility.

What does this change practically for an existing site?

If you already have an AMP version, you can explore sections that were once incompatible with the format: category pages, landing pages with forms, technical sheets. This requires checking the compatibility of your current components with the updated AMP specifications.

If you have never implemented AMP, the question remains: does the ROI justify the effort of development and maintenance? Well-optimized sites achieve excellent Core Web Vitals scores without AMP. The framework adds a layer of complexity (dual version, content synchronization, CDN resources) which must be balanced against the actual gains observed.

• AMP is no longer a prerequisite for appearing in enriched news formats (confirmed by Google in 2021)
• Core Web Vitals are now the primary performance criterion, regardless of the AMP format
• The framework remains relevant for sites with heavy backend constraints that make native optimization difficult
• Maintaining two versions (canonical + AMP) imposes a significant technical burden
• No recent Google data demonstrates a measurable ranking advantage for AMP over a well-optimized non-AMP site

Does this statement address the real issues with AMP?

No. Mueller claims that AMP has become more flexible, but he does not answer the central question: why choose AMP when a well-optimized site achieves the same results without the technical complexity? Modern frameworks (Next.js, Nuxt, Astro) can achieve excellent performance without AMP constraints.

The real barrier to AMP adoption today isn't its limitation to certain types of content. It's its maintenance cost and technical debt. Managing two versions of a site, synchronizing content, maintaining functional parity between canonical and AMP: all this requires resources that many projects can no longer justify. [To be checked]: Google provides no metrics proving that AMP still offers a measurable organic visibility advantage.

Do field observations contradict this narrative?

Yes, partially. Since the removal of the AMP badge in mobile results and the opening of Top Stories to non-AMP pages, sites abandoning AMP have not observed a traffic drop. Some are even seeing gains because the better-optimized canonical version offers a better user experience (smooth animations, full interactivity).

Today, sites that maintain AMP do so mainly out of inertia or because their backend tech stack is too slow to achieve good Core Web Vitals otherwise. AMP has become a crutch rather than a performance accelerator. If your architecture allows for native optimization, you gain simplicity without losing results.

In what cases is AMP still relevant after all?

For sites with significant technical debt and a legacy CMS that is difficult to optimize (poorly configured WordPress, old Drupal, slow proprietary solutions). AMP then offers a workaround: a fast version without reworking the backend. But it's a band-aid, not a long-term strategy.

Media with a high volume of daily content can also find value in it: AMP standardization reduces the risk of performance regression across thousands of pages published each week. But again, modern build pipelines (SSG, ISR) solve this issue differently. AMP remains an option, rather than a necessity.

What should you do if you already have an AMP version?

Start by measuring the real impact of AMP on your traffic. Compare AMP and canonical pages in Google Analytics: load time, bounce rate, conversions, engagement. If both versions perform similarly or if the canonical performs better, you have a case for abandoning AMP.

Next, test a gradual phase-out: remove AMP from a non-critical section (old blog, archived pages) and monitor metrics for 4 to 6 weeks. If there is no negative impact, expand the process. Google no longer applies an AMP boost, so the transition should be neutral if your Core Web Vitals are good.

What mistakes should be avoided when migrating away from AMP?

Do not remove AMP URLs overnight. Set up 301 redirects from the old AMP URLs to the canonical versions. Google may take several weeks to reindex the entire site, and your external backlinks may point to the AMP versions.

Ensure that your canonical tags and rel=amphtml are consistent during the transition. Poor configuration can create redirect loops or conflicting signals for Google. Use Search Console to detect crawl and validation errors post-migration.

How can you tell if AMP is still beneficial for your site?

Audit your Core Web Vitals on the canonical version. If your LCP is below 2.5 seconds, your FID below 100 ms, and your CLS below 0.1, AMP is probably not providing any benefits. If these metrics are poor, optimize natively first (lazy loading, compression, CDN, server cache) before considering AMP as a solution.

Also, look at your traffic sources. If Google Discover or Top Stories generate significant volume, verify that these channels perform just as well without AMP (which has been the case since 2021). If 90% of your traffic comes from traditional organic search, AMP likely has no impact.

• Compare real performance (Analytics) between AMP and canonical pages
• Audit Core Web Vitals of the canonical version with PageSpeed Insights
• Test the phase-out of AMP on a non-critical section for 6 weeks
• Set up proper 301 redirects before any removal of AMP URLs
• Verify the consistency of canonical and amphtml tags during migration
• Monitor Search Console for crawl errors post-migration