Is AMP really suitable for e-commerce sites?

Why does Google warn against AMP for e-commerce?

Mueller's statement points out a structural issue: AMP was designed to streamline content consumption, not to handle complex interactions. Forms, dynamic carts, and payment processes require advanced JavaScript and API calls that the AMP framework intentionally restricts.

Specifically, a merchant site loses the majority of its arsenal: product personalization, advanced filters, real-time shipping cost calculations, promo code validation. These features require a responsiveness that AMP cannot guarantee without cumbersome technical workarounds that negate its initial benefits.

What e-commerce features are blocked or degraded?

AMP forms technically exist via the amp-form component, but their capabilities remain limited. It's impossible to natively integrate a product configurator, a synchronized wishlist system, or dynamic cross-sell suggestions based on user behavior.

The conversion funnel is thus compromised. A user landing on an AMP product page will have to switch to the standard version to complete their purchase, creating a break in experience that is measurable in analytics. This transition from AMP to the standard site results in a loss of context and a documented spike in abandonment seen across the majority of tested implementations.

Does AMP hold any interest for online stores?

Yes, but only within a strictly defined scope: auxiliary editorial pages. An integrated blog, buying guides, and product comparisons can benefit from AMP without friction. This informational content does not require any transactional interaction.

Some brands maintain a hybrid strategy: standard optimized product sheets, editorial content in AMP to capture traffic on informational queries. This approach works if the architecture allows for a clear distinction without duplication or confusion for crawlers.

• Forms and complex interactions: incomplete or degraded support within the AMP ecosystem
• Conversion funnel: systematic break between AMP page and standard purchase process
• Viable use cases: non-transactional editorial content (guides, blog, comparisons)
• Hybrid strategy: possible but requires rigorous technical architecture to avoid conflicts
• Questionable ROI: development investment often exceeds the speed gains achieved through traditional optimization

Does this warning reflect on-the-ground observations?

Absolutely. E-commerce case studies show that AMP generates a conversion rate lower by 15 to 40% depending on the sector. The main cause is not the technology itself but the inability to reproduce the complete user experience. A customer who cannot add directly to the cart or customize their product leaves the page.

Major retailers that tested AMP in 2017-2018 have largely abandoned it. eBay, for instance, quickly pivoted to a PWA (Progressive Web App) optimization that offers speed AND features. The return on investment from AMP for e-commerce has proven negative in 80% of documented cases.

What alternatives offer a better performance-feature compromise?

Progressive Web Apps outperform AMP on all e-commerce metrics. They allow for fast loading through service workers, installation on the mobile home screen, and retain all JavaScript capabilities. Lancôme multiplied its mobile conversion rate by 17 by migrating to PWA.

Traditional optimization remains remarkably effective: intelligent lazy loading, code splitting, Brotli compression, well-configured CDN. A properly optimized standard site achieves excellent Core Web Vitals without the constraints of AMP. This approach costs less in development and maintenance while preserving business flexibility.

In what specific cases does AMP still make sense for commerce?

Only for pure players with a simple catalog and externalized purchase process. A dropshipper who systematically redirects to a third-party platform (Amazon, eBay) can technically use AMP for their product presentation pages, as the payment occurs elsewhere.

Some digital content marketplaces (ebooks, online courses) use AMP for sales pages since the funnel boils down to a single button. Yet even in these niches, the speed gains do not always compensate for the rigidity of the format. [To be verified]: Google has never published numerical data proving a sustainable ranking advantage of AMP outside the news carousel.

What should you do if your e-commerce site is already using AMP?

First, audit your AMP traffic via Google Analytics by segmenting by client type. If this traffic converts significantly less than the standard (difference over 10%), a gradual phase-out of AMP is necessary. Also compare the time spent and the number of pages viewed: a marked gap indicates a diminished experience.

Prepare a clean technical migration: remove amphtml tags from the standard HTML, take down AMP sitemaps from Search Console, and maintain 301 redirects from your AMP URLs to the standard versions for at least 6 months. Google takes several weeks to recrawl and completely deindex AMP versions.

What mistakes should you avoid when optimizing performance without AMP?

Do not replace AMP with a site that is equally slow. A poorly optimized standard site will be penalized by the Core Web Vitals, negating any benefit of abandoning AMP. Invest in a serious technical audit: crawl budget, resource size, critical loading order of scripts.

Avoid the trap of visual over-optimization: an LCP of 1.2 seconds is meaningless if your interactivity (FID/INP) is disastrous. E-commerce users click, filter, add to cart: interactivity takes priority over First Paint. Balance your efforts across all metrics without fixating on just one.

How can you validate that your post-AMP strategy is working?

Monitor three KPIs for 90 days: mobile conversion rate, add-to-cart rate, and average session duration. If these metrics progress or stabilize after abandoning AMP, your decision is validated. A temporary drop of 5-10% is normal during the transition.

Use Search Console to track indexing errors post-migration. Orphaned AMP pages that persist in the Google index dilute your crawl budget and create confusion. Force their removal via the URL removal tool if necessary.

• Audit AMP vs standard traffic and conversion over at least 30 days
• Implement native lazy loading and code splitting on the standard version
• Configure service workers for smart resource caching
• Gradually remove amphtml tags and AMP sitemaps
• Maintain 301 redirects from AMP URLs for 6 months
• Monitor Core Web Vitals weekly through CrUX and RUM