Do AMP pages really boost your ranking on Google?

Does AMP enhance organic rankings?

No, and that's the key takeaway from Mueller's statement. Contrary to what many sites believed when deploying AMP, the accelerated version does not directly influence ranking in search results.

Google crawls and indexes the standard desktop page, the one pointed to by the rel=canonical tag present in the AMP code. Ranking signals — content, internal links, semantic structure, linking — are extracted from this desktop page, not from the AMP version.

What is the real role of the rel=canonical tag in this mechanism?

The rel=canonical tag in an AMP page tells Google: "Here is the reference version to index." This tag points to the classic desktop page, which becomes the official source for all ranking criteria.

Technically, the AMP page only serves as a fast delivery version, especially in mobile contexts or Top Stories carousels. It is not evaluated for ranking, fundamentally changing the optimization logic: there’s no need to over-optimize AMP content if the desktop page remains mediocre.

Why has Google structured AMP in this way?

Google wanted to encourage loading speed without creating a parallel indexing system. By consistently linking AMP to a canonical desktop page, the engine avoids fragmentation of ranking signals and simplifies content duplication management.

This architecture also ensures that sites maintain a complete desktop version as an SEO reference while offering an optional accelerated experience. The trade-off: sites that heavily invested in optimizing their AMP pages without addressing the desktop have wasted their time.

• The AMP page is not indexed for ranking; it's the desktop that matters
• The rel=canonical tag in AMP points to the reference desktop version
• On-page SEO optimizations should focus on the desktop version
• AMP is only meant to enhance delivery speed, not ranking
• A site with AMP but a weak desktop will gain no SEO advantage

Does this rule apply uniformly to all types of sites?

On paper, yes. But in practice, it gets complicated. News sites that rely on the Top Stories carousel find that AMP implementation remains an indirect visibility lever. Admittedly, it's not traditional ranking, but access to this premium carousel generates qualified traffic. [To be verified]: the real impact of AMP on CTR and total traffic might offset the lack of a direct effect on ranking.

E-commerce sites, on the other hand, often abandoned AMP after realizing that the desktop version remained the absolute priority. The technical constraints of AMP (limited JavaScript, restricted CSS) create stripped-down versions that convert less effectively, with no compensating SEO gain.

What should be done with investments made in AMP optimization?

Let’s be honest: if you spent months perfecting your AMP pages while neglecting the desktop version, you optimized the wrong target. The SEO ROI of these efforts is nil if the desktop page remains mediocre.

That being said, AMP still holds value for mobile loading speed and user experience in certain contexts. But it's no longer a direct SEO lever. Reallocate your resources towards desktop optimization: that's where Google reads your ranking signals.

Why doesn't Google communicate more clearly about this mechanism?

Good question. The official documentation remains vague on the distinction between "ranking benefit" and "visibility benefit". Google has an interest in having sites adopt AMP for infrastructure and speed reasons, but it avoids explicitly stating that it doesn’t help ranking.

This ambiguity has created massive confusion: thousands of sites implemented AMP believing they would gain positions. [To be verified]: public data shows no direct ranking advantage linked to AMP, yet Google has never launched a massive clarification campaign. Silence worked in favor of technology adoption.

What should be prioritized for optimization after this statement?

Your classic desktop page, period. Title tags, meta descriptions, Hn structure, internal linking, editorial content, outgoing links; everything must be perfect on the desktop version. That’s what Googlebot crawls to extract ranking signals.

If you’ve neglected this version while focusing on AMP, you have a technical SEO debt. Conduct a full audit: duplicate content, crawl depth, desktop loading speed, Core Web Vitals on desktop. AMP can remain in place for fast delivery, but it should no longer monopolize your optimization resources.

How to verify that the canonical structure is correctly set up?

Inspect the source code of your AMP pages. The rel=canonical tag must point to the desktop version, not to the AMP URL itself. Common mistake: some sites set up a circular canonical (AMP → AMP), which disrupts Google’s indexing logic.

Use Search Console to check that Google is properly indexing desktop URLs, not AMP URLs. If you see URLs like amp.example.com or example.com/amp/ indexed as primary pages, you have a configuration issue. Correct the canonicals and request reindexing.

Should AMP be completely abandoned or retained?

It depends on your model. If you are a news site or blog that derives a significant portion of traffic from the Top Stories carousel, keep AMP for access to that premium placement. But don’t get carried away: it's not traditional organic ranking.

If you’re an e-commerce site, corporate, SaaS, or local service, AMP probably adds no value. The technical constraints limit the user experience and conversion. In that case, focus on a desktop/mobile responsive version that is ultra-fast through lazy loading, CDN, and image optimization. You will achieve better results.

• Audit and optimize the desktop version: content, tags, linking, speed
• Verify that rel=canonical tags in AMP point to the desktop page
• Check in Search Console that Google indexes desktop URLs, not AMP
• Reallocate optimization resources from the AMP budget to the desktop
• Assess the relevance of keeping AMP based on your model (news vs. e-commerce)
• Improve Core Web Vitals on the desktop version to compensate for the potential abandonment of AMP