Google Ends Cache-Served AMP Pages in Search

Google has quietly but significantly changed how it delivers AMP content in Search results. As of July 1, 2026, clicking an AMP result now takes users directly to a domain's own AMP host page rather than a version served through Google's infrastructure.

The shift closes a chapter on a serving model that shaped how publishers built and managed mobile web pages for years. For SEO professionals and web developers still maintaining AMP pages, this update simplifies the technical landscape and removes a layer of Google-controlled delivery that many found limiting. Understanding how this fits into the broader evolution of Google's technical requirements is essential for anyone responsible for site performance and search visibility.

---

What Changed and Why It Matters

The old AMP delivery path is gone

Previously, clicking an AMP result in Google Search triggered a specific delivery path. Google served the page from its AMP Cache and displayed it inside the AMP viewer with a google.com URL. Publishers who wanted their own domain URL shown in the browser bar had to configure signed exchanges — a technically complex workaround that added overhead to site management.

That entire serving path is now gone. Google has removed all references to the AMP viewer, AMP Cache, and signed exchanges from its official AMP documentation. When a user now clicks an AMP result in Search, the browser navigates directly to the domain's AMP host page and the AMP URL is visible as expected.

This mirrors a change Google News on mobile had already made, where traffic was routed directly to publisher domains rather than through AMP URLs. Search has now caught up.

Why this is a meaningful shift for publishers

The removal of the AMP Cache serving path is not a minor housekeeping update. For years, the google.com URL in the browser bar created friction for publishers around brand recognition, analytics attribution, and user trust. Visitors landing on a page served under a Google URL had no immediate indication they were on a publisher's own domain — a persistent frustration for site owners who had invested in building recognisable web presences.

The signed exchanges workaround that existed to address this problem required technical implementation effort that was disproportionate to the problem it solved. Its removal reduces complexity without removing any meaningful capability.

---

How AMP Lost Its Privileged Status

The gradual unwinding began in 2021

This update did not arrive without warning. The gradual unwinding of AMP's privileged status in Google Search began in 2021 when Google dropped AMP as a requirement for inclusion in the Top Stories carousel. That move was significant because Top Stories placement had been one of the primary incentives pushing publishers to adopt AMP in the first place.

Google also retired the AMP lightning bolt icon from search results that same year, removing the visual signal that had made AMP pages immediately identifiable to users. At that point, AMP became just another technical format rather than a fast-track to premium search real estate.

The July 2026 change completes the dismantling

The July 1 change represents the final piece of that dismantling. Google is no longer in the business of hosting and serving your AMP pages. That responsibility now rests entirely with the domain owner.

This progression reflects a consistent pattern in how Google has evolved its relationship with prescriptive web technologies. Rather than mandating specific implementations, the company has shifted toward rewarding measurable outcomes — page speed, stability, and accessibility — regardless of the underlying technical format. For teams already focused on technical SEO best practices and site architecture, this direction will feel familiar.

---

What This Means for Your Site

Immediate implications for AMP configurations

The most immediate practical takeaway is straightforward. You no longer need to configure the AMP Cache or set up signed exchanges to ensure your own domain URL appears when users click through from Search. That technical burden simply no longer exists.

Critically, Google has confirmed that AMP content will continue to rank normally. The change affects delivery, not ranking signals. AMP pages will be evaluated the same way any other web page is evaluated in Search. Publishers do not need to make urgent changes to avoid a ranking penalty — but the case for continuing to invest in AMP maintenance has weakened considerably.

For publishers sitting on the fence about whether to continue maintaining AMP pages at all, this update reframes the decision. As Search Engine Journal's reporting notes, "the choice is now just like any other technical decision." AMP is no longer a Google-preferred format with special delivery infrastructure behind it. It is a page format that either serves your users well or it does not.

For those who have already moved away from AMP in favour of modern performance frameworks or Core Web Vitals optimisation and strategies to increase organic traffic, this update validates that direction. For those still running AMP, the pages remain functional and indexed — they just arrive in the browser the same way every other page does.

Reassessing AMP as part of your broader SEO strategy

With AMP's infrastructure advantages fully removed, the format must now justify itself on its own merits. The relevant questions are practical ones: Are your AMP pages genuinely faster than their standard counterparts? Are they delivering a better experience on mobile? Is the maintenance overhead proportionate to the performance gains you can measure?

If the answers are uncertain, it is worth conducting a structured performance audit before making a decision either way. Google's tools for growing your business through search include resources that can help benchmark page performance and identify where investment is most likely to improve search outcomes.

The official AMP Project documentation remains a useful reference point for publishers still running AMP implementations and looking to understand what is and is not still supported.

Three ways to act on this information

• Audit your AMP setup. If your site still uses signed exchanges or relies on AMP Cache configurations, review whether those configurations need to be maintained or can be simplified now that Google no longer uses that serving path.

• Reassess your AMP strategy. With AMP's infrastructure advantages fully removed, evaluate whether your AMP pages are delivering genuine performance benefits or simply adding maintenance overhead. The decision should be based on page speed and user experience data rather than search incentives.

• Monitor traffic patterns. The shift to direct domain routing may affect how analytics tools attribute AMP traffic. Review your reporting setup to ensure sessions originating from AMP results in Search are being captured accurately under your domain.

The broader lesson for web teams

Google's phased withdrawal from AMP serving reflects a broader pattern in its relationship with prescriptive web formats. The company has consistently moved toward rewarding outcomes — fast, stable, accessible pages — rather than mandating specific technical implementations. For web teams, the lesson is durable: build for performance and users first, and let the format follow from that decision.