Does AMP really impact Google rankings?

Why does Google emphasize AMP neutrality in SEO?

This clarification from John Mueller addresses a persistent confusion within the SEO community. For years, many believed that adopting AMP guaranteed a ranking boost, especially since AMP pages enjoyed preferential display in the Top Stories carousel on mobile.

Let’s be honest: this confusion wasn’t entirely unjustified. The association between AMP and premium positions in mobile SERPs created a misleading correlation. However, Google has always maintained that what matters is loading speed, not the framework used to achieve it.

Is AMP still relevant if it’s not a ranking factor?

AMP remains a valid technical tool to achieve high performance quickly, particularly if your development team lacks resources or expertise in optimization. The framework imposes strict constraints that eliminate common mistakes: JavaScript blocking render, unoptimized CSS, uncompressed images.

In practical terms? AMP can be a quick solution for a news site or blog that must deliver content instantly. But for a complex e-commerce site or a SaaS platform, the functional limitations of AMP quickly become a hurdle. And if your current tech stack is already delivering excellent Core Web Vitals, why completely overhaul it?

What is the real variable that Google measures?

What Google values is the user experience measured by concrete metrics: LCP, FID, CLS. It doesn’t matter whether you achieve these scores through AMP, a PWA, good old optimized HTML, or a modern framework like Astro or Next.js.

Mueller's message is clear: stop looking for magic shortcuts. It’s not the AMP badge that ranks you; it’s the actual performance of your site. A non-AMP page that loads in 0.8 seconds will always outperform a poorly optimized AMP page that takes 2 seconds.

• AMP is not a direct ranking factor in Google's algorithm
• Loading speed remains an important criterion, measured by Core Web Vitals
• AMP can facilitate achieving good performance, but it’s just one means among others
• Already fast sites have no SEO benefit in migrating to AMP
• Access to the Top Stories carousel is no longer exclusive to AMP since the Page Experience update

Is this statement consistent with field observations?

Yes, and it’s confirmed by data post-Page Experience Update. Since Google opened the Top Stories carousel to non-AMP pages that meet Core Web Vitals, we observe sites without AMP occupying these privileged positions — as long as they are genuinely fast.

What’s more interesting is what Mueller doesn’t say: AMP can still indirectly influence SEO through improved behavioral metrics. A page that loads instantaneously reduces the bounce rate and increases time on site. These signals have weight, even if Google will never officially admit it. [To be verified] how much these behavioral metrics actually weigh in the current algorithm.

In what cases does AMP still make sense?

For news sites and news blogs, AMP maintains a practical advantage: caching on Google servers. Content is served from Google's infrastructure, ensuring maximum availability even during traffic spikes. If you publish a scoop that goes viral, your server won’t crash.

On the other hand, for e-commerce, AMP is often a functional dead end. The JavaScript limitations complicate implementing product configurators, advanced dynamic filters, or certain payment systems. The question isn’t even SEO anymore; it becomes UX: do you sacrifice critical features for a performance gain that can be achieved otherwise?

What nuances should be added to this message?

Mueller remains deliberately vague on one point: the correlation between speed and ranking. Saying "AMP doesn’t rank" is technically true, but it masks a more complex reality. If AMP allows you to achieve excellent Core Web Vitals while your standard site is slow, you will see an SEO impact — not because it’s AMP, but because it’s fast.

And that’s where the issue lies. Many sites have adopted AMP as a band-aid for a flawed architecture. The real work is to optimize the main site. AMP should never be an excuse to avoid cleaning up technical debt. [To be verified] if Google penalizes sites that serve an ultra-fast AMP version but keep a slow canonical version.

Should you abandon AMP if you’re already using it?

Not necessarily. If your AMP implementation is working well, your Core Web Vitals are in the green, and you have no blocking functional limitations, there is no urgency to break everything. The cost of migration should be justified by tangible gains.

However, if you were maintaining AMP solely out of fear of losing positions, this statement from Mueller gives you the green light to explore other options. Instead, invest in optimizing your main site: performant CDN, intelligent lazy loading, modern image optimization formats (WebP, AVIF), critical inline CSS, reduction of third-party JavaScript.

How to ensure equivalent performance without AMP?

The key is to treat performance as a feature, not an afterthought. Integrate performance budgets into your CI/CD: if a PR degrades LCP by more than 10%, it doesn’t pass. Use tools like Lighthouse CI, SpeedCurve, or Calibre for continuous monitoring.

In practical terms, audit your Core Web Vitals via Search Console and PageSpeed Insights. Identify elements that hinder LCP (often unoptimized hero images), CLS (fonts loading late, ads shifting content), and FID (heavy JavaScript). Prioritize quick wins: Brotli compression, preloading critical resources, using a modern CDN.

What mistakes to avoid in this transition?

Do not remove your AMP pages overnight without proper 301 redirects. Google must understand that the non-AMP version becomes the new canonical. Properly configure your canonical tags and ensure that the structured data (Schema.org) is identical across both versions during the transition.

Another classic pitfall: believing that abandoning AMP means speed no longer matters. On the contrary, you must now take on the optimization that the framework imposed. If your non-AMP site is slower than your old AMP version, you will lose traffic — not because of the absence of AMP, but because the user experience degrades.

• Audit your current Core Web Vitals (LCP, FID, CLS) via Search Console and PageSpeed Insights
• Compare AMP vs. non-AMP performance on a representative sample of pages
• If you abandon AMP, implement 301 redirects and update canonical tags
• Optimize images (modern formats, lazy loading, responsive images with srcset)
• Reduce blocking JavaScript: defer, async, code splitting
• Implement a performant CDN with Brotli compression enabled
• Continuously monitor Core Web Vitals post-migration to detect any regression