Google Ends AMP Cache Serving: Publishers Gain Control

Google Ends AMP Cache Serving: What Changed on July 1

As of July 1, Google Search stopped serving AMP pages from its own cache. Clicking an AMP result now directs users to the publisher's AMP host page, bypassing the Google AMP viewer and cache entirely. Google also removed references to the AMP viewer, AMP Cache, and signed exchanges from its documentation. This marks the final step in a gradual retreat from AMP that began in 2021, when Google dropped AMP as a requirement for Top Stories and removed the lightning-bolt icon.

This change directly affects how AMP content is delivered, not how it ranks. Google explicitly states that AMP content 'will continue to rank just like any other web page.'

Strategic Analysis: Who Gains, Who Loses, and What Shifts

Publishers with Strong Non-AMP Mobile Sites Win

Publishers who invested in standard web technologies—responsive design, lazy loading, CDN optimization—now see their bet pay off. They no longer need to maintain AMP versions to get the same search visibility. The removal of the AMP cache eliminates a layer of complexity and cost. These publishers can redirect resources toward improving core web vitals and user experience on their own domains.

AMP-Heavy Publishers Face a Dilemma

Publishers who built their mobile strategy around AMP lose the speed advantage that the cache provided. Without the Google cache, AMP pages load from the publisher's own server, potentially erasing the performance gap that justified AMP adoption. These publishers must now decide whether to maintain AMP as a parallel framework or migrate to standard web technologies. The sunk cost of AMP infrastructure becomes a liability.

Google's Strategic Retreat

Google's removal of AMP cache signals a broader shift away from proprietary web frameworks. The company is reducing its role as a content intermediary, likely in response to regulatory pressure and publisher pushback. By decoupling AMP from search benefits, Google aligns with the open web narrative while still controlling search rankings. The AMP project itself loses relevance, and Google may eventually deprecate AMP entirely.

User Experience Improves

Users now get direct access to publisher content without the intermediary AMP viewer. This reduces URL confusion and potential privacy concerns associated with Google-hosted pages. Page load times may vary depending on publisher optimization, but the removal of the cache eliminates a single point of failure.

Outlook & Next Steps: What Executives Should Do Now

Publishers should audit their AMP usage immediately. If AMP pages account for significant traffic, test their performance without the cache. Consider migrating to standard web technologies if AMP maintenance costs outweigh benefits. Monitor Google's documentation for further AMP deprecation signals. The next 30 days are critical for reallocating resources away from AMP toward holistic mobile optimization.

Final Take

Google's move is a clear signal: AMP is no longer a strategic advantage. Publishers who treat this as a technical adjustment miss the point. The real opportunity is to reclaim control over mobile performance and reduce dependency on Google's infrastructure. Those who act decisively will strengthen their competitive position; those who cling to AMP risk stranded assets.

Source: Search Engine Journal