Is it really worth investing in AMP for a business website?

Does AMP still provide a competitive edge in SEO?

When Google launched AMP in 2016, the message was clear: this technology was presented as nearly essential for mobile performance. The project promised lightning-fast loading times thanks to simplified HTML and Google's cache.

Eight years later, the official statement marks a radical tone shift. Google now acknowledges that AMP is one option among others to optimize mobile speed, not a requirement. This retreat is explained by the evolution of Core Web Vitals and web technologies: PWA, native lazy loading, HTTP/3, and high-performing CDNs allow for comparable results without the structural constraints of AMP.

What does "depends on specific resources and needs" really mean?

This deliberately vague phrasing hides a practitioner reality: AMP requires a significant technical investment. You must maintain two versions of your pages (canonical and AMP), adhere to strict HTML constraints, manage limited JavaScript, and often rethink your analytics infrastructure.

For an e-commerce site with rich functionalities, this investment quickly becomes a resource sinkhole. For an editorial blog or a media site with primarily textual content, the equation can be different — but even there, alternatives exist. Google implicitly admits that a well-natively optimized site can compete with AMP without these constraints.

Are business websites the right use case for AMP?

Let’s be honest: traditional business sites (B2B, services, corporate) generally do not match the ideal profile for AMP. These sites often require complex forms, elaborate marketing tracking systems, CRM integrations, and interactive content.

AMP imposes technical restrictions that conflict with these needs. Companies that have massively invested in AMP now find themselves with significant technical debt for an SEO gain that is no longer distinguishing. The specific mention of "business websites" in this statement is not trivial — it's a signal that Google recognizes the poor fit for this segment.

• AMP is no longer a differentiating ranking criterion since the introduction of Core Web Vitals as ranking factors
• AMP badges in SERPs have gradually disappeared, reducing the visual impact of this technology
• A well-optimized responsive site (image compression, lazy load, critical CSS) can achieve equivalent performance
• Dual maintenance (canonical + AMP) represents a recurring cost often underestimated during project phases
• AMP's JavaScript limitations hinder advanced marketing and analytics functionalities

Does this statement indicate a gradual abandonment of AMP by Google?

The cautious and conditional tone of this statement sharply contrasts with the aggressive evangelism of the earlier years. Google no longer says "use AMP," but rather "it can be beneficial if...". This semantic shift is not insignificant. Since Core Web Vitals allow any site to achieve good performance without AMP, the project has lost its structural competitive advantage.

Several signals point to disengagement: WordPress has removed the official AMP plugin from its core, many major media sites have abandoned AMP, and Google has stopped actively pushing this technology in its communications. [To be confirmed]: no recent public data confirms a measurable SEO impact of AMP versus a classic fast mobile site.

Are AMP's speed gains still relevant in light of current technologies?

The initial promise of AMP was based on a slow mobile web, lagging 3G networks, and poorly adapted desktop sites. That reality has changed. HTTP/2 and HTTP/3 multiply parallel requests, edge computing CDNs reduce latency, native lazy loading avoids unnecessary loading, and WebP/AVIF formats drastically compress images.

A well-architected site today can achieve Lighthouse scores of 90+ on mobile without AMP. Google's AMP cache offered an advantage — but at what cost? You lose control over hosting, the displayed URL (until recently), and the complete user experience. For a business site where brand consistency and the user journey are critical, this trade-off becomes unacceptable.

When is AMP still justified?

There are still scenarios where AMP may make sense — but they are much more limited than initially advertised. Purely editorial sites with simple textual content, without complex programmatic monetization, can benefit from AMP if their technical stack makes native optimization difficult.

Some legacy CMS or infrastructure constraints sometimes make native mobile optimization complex. In these situations, AMP can serve as a workaround — but this is to admit that you are treating the symptom rather than the cause. A high-traffic news site, with primarily textual content and images, may still justify AMP. But even there, the trend is towards gradual disinvestment.

How do you evaluate if AMP deserves investment for your business site?

Start with a candid mobile performance audit. Measure your actual Core Web Vitals (CrUX data, not synthetic) on your strategic pages. If your LCP exceeds 2.5s, your FID is 100ms or your CLS is 0.1, you have a performance issue — but AMP is probably not the best solution.

First, identify the quick wins: image compression, lazy load, eliminating blocking JavaScript, optimizing critical CSS, effective caching. These optimizations enhance your canonical site for all users, not just those coming from Google. If, after these optimizations, you're still in the red, then only consider AMP as a last resort — or better yet, reconsider your overall technical architecture.

What mistakes should you avoid regarding the AMP decision?

The classic mistake: implementing AMP because a competitor has done it or an automated audit recommends it. AMP is not a SEO badge to tick off; it's an architectural choice with profound implications. Don't dive in without assessing the real long-term maintenance costs.

Another common trap: believing that AMP compensates for a poorly designed desktop site. If your canonical version is slow, poorly coded, overloaded with third-party scripts, AMP becomes a bandaid on a wooden leg. You're masking the problem without solving it, and you're creating additional technical debt. Finally, don’t underestimate the impact on your analytics and marketing stack: many tools don’t work or function poorly in AMP.

What strategy should you adopt today?

If you don't have AMP yet: don’t invest in it. Focus your resources on the native mobile optimization of your site. Use the budgets you would have allocated to AMP to improve your infrastructure: high-performing CDN, automated image optimization, code splitting, strategic preload/prefetch.

If you already have AMP in production: assess its actual contribution to traffic and conversions. Compare business metrics (conversion rate, engagement, revenue) between your AMP and canonical pages. If the gap is marginal or negative, plan for a gradual exit. Start by disabling AMP on low-traffic sections, measure the impact, and then extend if the results confirm the hypothesis.

• Audit the actual Core Web Vitals (CrUX) on mobile for your strategic pages
• Measure the performance gap between the canonical version and direct competitors
• Assess the cost of development and maintenance of AMP versus native optimization
• Test the impact on critical analytics and marketing tools before full deployment
• If AMP exists, compare business metrics (conversion, engagement) between AMP and canonical
• Plan a gradual exit strategy if the ROI is negative or marginal