Is the AMP experience really the ideal user journey according to Google?

What is Google really looking for with this statement about AMP?

Google is describing its ideal user journey: a first page that loads instantly thanks to AMP, followed by smooth navigation to the next steps—product consultation, adding to cart, payment. The argument relies on two pillars: the technical high performance of AMP and its portability across different contexts.

Specifically, this vision assumes that the user enters through an AMP page (often from mobile search results or Google Discover), then continues browsing without friction. Google emphasizes AMP's ability to maintain this smoothness across the entire conversion funnel, not just on the landing page.

Why does Google emphasize portability so much?

Portability refers to the ability of an AMP page to function in differing environments: classic search results, AMP carousels, Google News, web stories, third-party apps. Google presents this versatility as an asset for publishers and e-commerce businesses.

The underlying idea? A single technical version can serve multiple entry points without requiring specific development. However, this promise assumes your infrastructure supports AMP throughout the journey, which is not always the case in reality.

Does this ideal experience work for all types of sites?

Google discusses a complete journey including product selection and purchase. This mainly concerns e-commerce and transactional sites, less so purely informational sites or complex services requiring rich interfaces.

For media that monetizes through advertising, AMP can indeed speed up article reading. For an online store with product configurators or complex checkout processes, the technical constraints of AMP can become a barrier to conversion rather than an accelerator.

• Instant Performance: AMP promises near-zero loading time on the first click
• Multi-context Portability: the same technical version for multiple Google entry points
• Complete Journey: Google encourages AMP throughout the funnel, not just on the landing page
• Suitable Scope: works better for simple e-commerce and media than for complex interfaces
• Technical Investment: requires partial or complete redesign of the front-end architecture

Does this vision correspond to what we observe in the field?

Let’s be honest: few sites have actually deployed AMP across their entire conversion funnel. Most are limited to article pages or product sheets, redirecting to the classic site once a form or cart comes into play. Google describes an ideal that even its own services do not always apply end-to-end.

Performance data show that AMP indeed speeds up the time to first paint, but the subsequent journey depends on implementation. If you disrupt the experience by switching to a non-AMP version midway, you lose the fluidity that Google promotes here.

What are the gray areas in this statement?

Google does not clarify how to concretely measure this ideal user experience. Are we talking about Core Web Vitals? Bounce rates? Time spent on the site? Without clear metrics, it's difficult to know if your AMP implementation truly reaches this ideal. [To be verified]

Another point: portability is presented as an advantage, but it imposes strict constraints on JavaScript code, CSS styles, and user interactions. For many sites, these technical limitations outweigh the promised benefits, especially since Core Web Vitals also reward optimized non-AMP pages.

When does this recommendation not apply?

If your site offers complex configurators, interactive tools, or multi-step conversion funnels with third-party scripts (payment, chat, customization), AMP becomes more of a constraint than a solution. The framework's limitations can break essential features.

B2B sites with long forms, SaaS platforms, or comparison sites requiring client-side calculations often lose more in functionality than they gain in speed. In these contexts, it is better to optimize your existing stack rather than force AMP everywhere.

Should you still invest in AMP for your site?

The answer depends on your business model and industry. If you are a pure media player with simple article pages and a need for visibility in Google News or Discover, AMP still makes sense. For e-commerce with basic product sheets and few interactions, it may be worth the investment.

On the other hand, if your conversion funnel relies on advanced features or if you have already optimized your Core Web Vitals outside of AMP, the investment becomes debatable. Focus your resources instead on lazy loading, code splitting, and server optimization.

What mistakes should you avoid if you choose AMP?

The worst mistake: deploying AMP only on entry pages, then breaking the experience by redirecting to the classic site on the second click. You then lose the fluidity that Google values, creating unnecessary friction in the user journey.

Another pitfall: underestimating maintenance costs. AMP requires double template management (AMP version + classic version), which multiplies points of failure. Every functional evolution must be applied to both versions, with specific tests for each environment.

How can you verify that your implementation is compliant?

Use the official AMP validator for each type of page. A single non-compliant script can break the eligibility of the entire section. Also test navigation between AMP pages to verify that pre-rendering works and transitions remain instant.

Measure Core Web Vitals specifically on your AMP pages via Search Console and compare them to your classic pages. If the performance gap is not significant, the AMP investment loses its main argument. Also monitor conversion rates: a super-fast page that converts poorly is useless.

• Assess if your conversion funnel is compatible with AMP's technical constraints
• Plan for AMP implementation throughout the journey, not just on the landing page
• Validate every page with the official tool and test inter-page navigation
• Measure Core Web Vitals and conversion rates before/after deployment
• Compare the maintenance cost of AMP vs classic performance optimization
• Avoid the abrupt switch between AMP and non-AMP versions mid-journey