Does AMP really boost your ranking on Google?

Has AMP ever been a direct ranking factor?

The short answer is: No, never. Contrary to what many believed for years, AMP has never been a direct ranking signal in Google's algorithm. This confusion mainly arises from the Top Stories carousel, which was initially reserved for AMP pages on mobile.

The Top Stories carousel displayed a distinctive lightning badge next to AMP results, creating the illusion of an SEO advantage. In reality, the advantage was purely related to eligibility for the carousel, not classic organic ranking. Non-AMP pages were simply excluded from this enriched format until Google gradually opened up this feature.

What’s the difference between eligibility and ranking?

This is a point that too many SEOs still confuse. Eligibility determines whether a page can appear in a specific format, such as Top Stories, featured snippets, or rich results. Ranking, on the other hand, determines the position in standard results.

AMP worked as a ticket to access certain SERP features, not as an algorithmic boost. A page could be technically perfect in AMP and rank on page 3, while a well-optimized non-AMP page could hold position 1. The AMP format alone guaranteed nothing in terms of positioning.

Why this statement now?

This clarification comes in a context where AMP is gradually losing its mandatory character. Google has opened the Top Stories carousel to non-AMP pages that meet Google News content policies and Core Web Vitals. The question then becomes: why maintain AMP if it doesn’t offer a ranking advantage?

The statement aims to refocus the debate on what AMP actually does well: perceived speed and user experience. Google implicitly acknowledges that too many sites have implemented AMP solely for SERP eligibility, without genuine consideration for the final UX. This cargo cult approach to SEO has generated frustration and wasted resources.

• AMP is not and has never been a direct ranking factor in Google's algorithm
• The historical advantage of AMP was eligibility for the Top Stories carousel, not a ranking boost
• Since the opening of Top Stories to non-AMP, the SEO justification for AMP is collapsing significantly
• Loading speed remains a factor, but can be achieved without AMP through other technical optimizations
• The Core Web Vitals are measured across all pages, AMP or not, using the same evaluation criteria

Does this statement align with what we see in practice?

Absolutely. A/B tests conducted in recent years consistently show that a well-optimized non-AMP page performs as well as an AMP version in terms of organic positioning. The few cases where AMP seemed to provide an advantage were related to Top Stories eligibility or measured real speed differences by Core Web Vitals.

I have personally audited e-commerce sites that removed AMP without observing any loss of organic traffic, provided they maintained solid technical performance. The myth of AMP's SEO advantage was essentially based on correlation: sites investing in AMP generally also invested in overall performance, creating an observation bias.

What are the real reasons to maintain AMP today?

If classic SEO is no longer an argument, AMP still has certain specific and measurable advantages. Google's caching drastically reduces the Time to First Byte for users arriving from the SERP. The pre-rendering of AMP pages in search results creates an almost instantaneous browsing experience.

For high-traffic news sites, these milliseconds gained can lead to significantly lower bounce rates and longer sessions. But quantify these gains: if your CWV is already excellent without AMP, the delta becomes marginal. [To verify]: Google does not publish any reliable comparative data on the actual UX impact of AMP vs non-AMP at equal performance levels.

When does AMP become counterproductive?

For e-commerce sites, it's often a nightmare. The JavaScript limitations of AMP break essential features: product configurators, dynamic price calculators, sophisticated recommendation systems. Maintaining two versions (AMP and canonical) doubles the surface of bugs and development costs.

I have seen teams spend weeks debugging conversion issues on AMP, only to discover that a critical third-party component was simply not compatible. ROI becomes negative when the time spent far exceeds hypothetical traffic gains. If your site is not in the news vertical and your CWV are in the green, abandoning AMP is probably the most rational decision.

Should you abandon AMP immediately?

Not necessarily. Start by measuring what AMP actually brings you. Segment your Analytics traffic: compare metrics between AMP and non-AMP pages (bounce rate, session duration, page views, conversions). If AMP pages perform better in engagement, it's probably due to speed, not the format itself.

Run a controlled test: identify a homogeneous content segment and remove AMP from 50% of the URLs. Monitor for 4-6 weeks comparing organic traffic, positions, and UX metrics. If no statistically significant difference appears, you have your answer. This empirical test is more valuable than any expert opinion.

How to optimize without AMP to achieve the same benefits?

The key is to replicate AMP's speed advantages using standard techniques. Implement a high-performance CDN, enable Brotli compression, aggressively optimize the critical rendering path. Native lazy loading of images and iframes is now supported natively, without needing AMP components.

On the JavaScript side, switch to code splitting and deferred loading of non-critical scripts. Most modern frameworks (Next.js, Nuxt, etc.) handle this out-of-the-box. Aim for an LCP under 2.5s, a FID under 100ms, a CLS under 0.1. These CWV thresholds are now what truly matters for Google, not the AMP badge.

What mistakes should you avoid during the transition?

Never abruptly remove AMP without a redirect and monitoring plan. If your AMP pages were indexed separately, ensure that 301 redirects are in place and that the canonical tags point correctly. Check in Search Console that Google properly recrawls and reindexes the non-AMP versions.

Classic mistake: neglecting structured data during the migration. AMP pages often included specific Schema.org (Article, NewsArticle). Transfer this structured data to your standard pages to maintain eligibility for rich results. Test with the Rich Results Test before massively deploying.

• Audit actual UX metrics (Analytics) between AMP and non-AMP pages to quantify impact
• Run a controlled A/B test on a content segment before any broad decisions
• Optimize the Core Web Vitals of standard pages to meet "Good" thresholds
• Implement CDN, compression, and native lazy loading to replicate AMP speed
• Plan 301 redirects and update canonicals if removing AMP
• Ensure complete transfer of structured data to non-AMP pages