Google Phases Out AMP Cache: A Long-Overdue but Welcome Cleanup

On July 1, 2026, Google made a quiet but significant change to how it handles Accelerated Mobile Pages (AMP). Starting that day, Google Search began redirecting users directly to the publisher-hosted AMP versions of pages instead of serving them through Google’s own AMP Cache.

This marks the practical end of the AMP Cache era — a move many in the industry viewed as long overdue.

---

What Happened and Why It Matters

For years, AMP pages served from Google’s cache (typically under `google.com/amp/` or `cdn.ampproject.org` domains) delivered lightning-fast mobile experiences. In the early days, having a valid AMP version was essentially a requirement to appear in the prominent Top Stories carousel on mobile search results.

Google later relaxed this in 2021 as part of the Page Experience update, allowing high-quality non-AMP pages to compete on equal footing.

The latest change goes further: Google has removed references to the AMP viewer, AMP Cache, and Signed Exchanges from its official documentation. Publishers no longer need to maintain cache updates or configure complex Signed Exchanges. Google simply points users straight to the AMP page hosted on the publisher’s own domain.

Key benefits for legitimate publishers:

• Reduced maintenance overhead;
• No more cache invalidation headaches;
• Simpler technical stack;
• AMP content continues to rank normally alongside regular web pages.

In short, Google is stepping back from its role as an intermediary cache provider for AMP while keeping the format itself viable for those who still want to use it.

---

The Mobile Reality That Made AMP So Powerful

In a world where mobile accounts for 60-80% of web traffic in many markets — and Android dominates globally — AMP offered a genuine performance edge.

Fast-loading pages on a trusted `google.com` subdomain translated into better user experience, higher engagement, and, in some cases, improved visibility.

For mainstream news sites and publishers focused on user experience, this was mostly about speed and compliance. However, a different group saw something else entirely.

---

The Gray-Area Use Case That Is Now Gone

In certain regulated or restricted geographies, savvy operators discovered that AMP pages served from Google’s infrastructure could bypass some blocks and restrictions that affected direct publisher domains. On Android devices in particular, these pages often loaded from a `google.com` subdomain, providing better uptime and a perception of legitimacy.

This created a reliable workaround in verticals where direct access was frequently disrupted — including affiliate marketing, especially in the casino and betting space.

One illustrative (and quite extreme) example comes from a site heavily focused on casino affiliate traffic. Over a three-month period, the site recorded 143,000 total clicks from Google Search. Of those, 113,000 — or roughly 80% — came through AMP pages. That level of dependency shows just how powerful the AMP cache workaround had become for certain operators.

Those who understood the mechanics early built significant traffic and revenue streams around it. For them, AMP wasn’t just a performance optimization — it was a strategic asset in an environment where conventional domains faced constant friction.

Also read:

• The Great AI Sabotage: Why 44% of Gen Z Employees are Quietly Breaking the Machines
• Amazon Caught in Secret Price Manipulation Scheme with Levi’s, Walmart, Target, Home Depot and More
• "I Would Have Cured Cancer First": Why Google DeepMind’s CEO Thinks the AI Race is a Mistake
• 2026 AI Creator Toolkit: The Best Neural Networks for Stunning Creatives, Digital Avatars & Reel Editing (Curated by QUASA)

---

The End of an Era

With the cache now disabled for new connections from Google Search, that particular advantage has disappeared. Publishers who relied on AMP primarily for the cache’s delivery benefits will see those benefits evaporate. Many had already begun moving away from AMP years ago once the Top Stories requirement was lifted and modern web performance techniques (Core Web Vitals, responsive design, better hosting) proved sufficient.

The decision is clean and logical:

• It reduces Google’s operational burden.
• It gives publishers full control over their content delivery.
• It aligns with the broader industry shift toward standard, high-performance web pages rather than proprietary formats.

For honest publishers optimizing for users, this change is largely neutral or even positive — one less thing to maintain.

For those who built business models around the specific quirks of the AMP cache in restricted environments, the free ride is over.

The mobile web has matured. Performance matters more than ever, but it no longer requires a Google-managed cache or special format to achieve. The era of AMP as a backdoor optimization tool has quietly closed.