Does AMP really boost Google's rankings or is it just an SEO myth?

Is AMP truly neutral regarding rankings?

The statement from John Mueller cuts through a recurring debate: AMP does not act as a ranking signal in Google's algorithm. Unlike Core Web Vitals or HTTPS, using AMP provides no direct algorithmic advantage. Your AMP page and your equivalent standard page start on equal footing in the positioning race.

However, Mueller introduces an important nuance: the fast user experience that AMP offers can boost engagement. More page views, lower bounce rates, longer time spent. These behavioral signals can theoretically influence your visibility. The mechanism is indirect, but potentially real.

Why does Google maintain AMP if it doesn't impact rankings?

AMP was designed to speed up mobile web, not to serve as an SEO tool. Google developed it in response to editorial sites overloaded with ad scripts that made the mobile experience terrible. The goal was to standardize an ultra-fast format, even at the cost of restricting certain JavaScript functionalities.

For content publishers and news sites, AMP provided privileged access to the Top Stories carousel in mobile SERPs. That was the real SEO benefit: premium editorial visibility. But this privilege has been extended to any fast page that meets Core Web Vitals, which has reduced AMP's exclusive appeal.

What does 'improving overall engagement' actually mean?

Mueller refers to users who “explore more content.” Practical translation: reduced bounce rates, increased visit depth, longer session times. These engagement metrics are measurable in Analytics, but their exact weight in the ranking algorithm remains unclear.

Google has always been vague about using behavioral data as ranking factors. We know they test these signals extensively, but public confirmation remains rare. Here, Mueller suggests an indirect link without ever claiming that better engagement = better ranking. This ambiguity is typical of official communications.

• AMP is not a direct ranking factor — no algorithmic boost for its sole use
• The advantage lies in the loading speed and user experience that can improve engagement
• Behavioral metrics (bounce, depth, time) remain potentially influential signals but are not officially confirmed
• Access to the Top Stories carousel no longer exclusively requires AMP since the introduction of Core Web Vitals
• Investing in AMP solely for SEO is a strategic mistake — overall performance is paramount

Is this statement consistent with field observations?

Absolutely. A/B tests conducted by many publishers show that adopting AMP alone does not change organic positions. Sites that have dropped AMP have not experienced ranking declines, provided they maintain equivalent performance in standard. This is a conclusion I share after dozens of audits: format matters less than actual speed.

Where it gets complicated is with engagement. Yes, a page that loads in 0.5 seconds has a lower bounce rate than a page that takes 4 seconds. But attributing this gain solely to AMP is reductive. A well-optimized standard page (lazy loading, CDN, compression) achieves comparable performance without the constraints of the AMP framework.

What nuances need to be added to this claim?

Mueller remains deliberately vague about the true weight of engagement in ranking. He says it may “potentially” improve, not “improves.” This caution hides a reality: Google likely uses these signals, but in a contextual manner, weighted by dozens of other factors. [To check]: no Google study has ever quantified the direct impact of visit depth on ranking.

Another nuance: AMP has historically benefited from display privileges (lightning icon, carousel) that generated more clicks. This higher CTR can indirectly influence ranking through positive user signals. But since these privileges have been extended to fast non-AMP pages, the argument falls apart.

In what cases does this rule not apply?

For news sites targeting the Top Stories carousel, AMP remains a legitimate strategic choice. Although it’s no longer exclusive, the framework guarantees immediate compliance with Google’s speed requirements. For media outlets with short publication deadlines, it’s a valuable technical safety net.

However, for e-commerce sites, SaaS, or corporate blogs, AMP is often counterproductive. You lose flexibility in JavaScript, customization, and advanced tracking. The engagement gains promised by Mueller do not compensate for these limitations. It is better to optimize your standard pages and aim for excellence on Core Web Vitals.

Should you invest in AMP to boost your SEO?

No, not if your sole goal is organic ranking. Instead, invest in overall performance optimization: image compression, server caching, CSS/JS minification, CDN. These actions benefit 100% of your traffic, not just AMP mobile visitors.

If you are a content publisher aiming for the Top Stories carousel, AMP might justify itself as a performance guarantee. But first, check if your standard pages can achieve the same Lighthouse scores. In 80% of cases, they can with a thorough technical audit.

What mistakes should you avoid in interpreting this statement?

A classic mistake: thinking that AMP boosts ranking because you observe a traffic increase after deployment. This gain often comes from access to the carousel, a better CTR attributed to the lightning icon, or a reduced bounce rate. None of these mechanisms means that Google has improved your ranking in organic results for the same keyword.

Another trap: abandoning all performance optimization on your standard pages on the grounds that your AMP pages are fast. Google indexes and ranks both versions. If your canonical page remains slow, it is likely to underperform, not your AMP version. Engagement on AMP does not rescue a poor experience on the standard version.

How can you measure the real impact of AMP on your site?

Isolate the metrics that matter: average positions in Search Console (by AMP page vs standard), bounce rate in Analytics (segmented by format), session depth, conversions. Compare these KPIs before and after deploying AMP while controlling for other variables (seasonality, algorithm updates).

If you notice better engagement on AMP but no position gains, you confirm Mueller's statement: AMP improves UX, not direct ranking. If you gain positions, it is likely tied to another competitive factor (improved content, acquired backlinks, weakened competition). Do not wrongly credit AMP.

• Audit your Core Web Vitals on standard pages before considering AMP
• Measure the actual loading time (TTFB, LCP) with tools like WebPageTest
• Compare the bounce rate and visit depth between AMP and standard pages
• Check if your pages are eligible for the Top Stories carousel without AMP
• Test a classic performance optimization (CDN, lazy loading, compression) before switching to AMP
• Monitor your organic positions by format in Search Console