Google Retires AMP Viewer: Search Now Links Directly to Publisher-Hosted AMP Pages

Google has quietly implemented a significant update to how it handles Accelerated Mobile Pages (AMP) within its search results. Moving forward, Google Search will bypass its proprietary, Google-hosted AMP Viewer and cache, directing mobile searchers straight to the publisher’s own hosted AMP pages.

This change marks a quiet but monumental shift in Google’s long-term mobile web strategy. For nearly a decade, the search giant relied on its own Content Delivery Network (CDN) to cache and serve AMP content directly from Google-owned URLs. While designed to make the mobile web lightning-fast, this practice drew fierce criticism from publishers, developers, and antitrust regulators who argued that Google was effectively walling off the open web.

With this latest update, Google is handing back control of the delivery infrastructure to publishers while maintaining its support for the underlying open-source AMP HTML framework.

Main Facts: What is Changing in Google Search?

Under the newly updated system, when a user clicks on an AMP-enabled search result on a mobile device, Google Search will no longer render that page inside the Google AMP Viewer (which displayed a Google-hosted URL, such as google.com/amp/s/...). Instead, the browser will navigate directly to the publisher’s canonical or AMP-specific URL (e.g., publisher.com/article/amp).

According to documentation and statements provided by Google, the core elements of the update include:

• Direct Redirection: Users are sent directly to the publisher’s domain to load the AMP document, eliminating the intermediate Google-hosted viewer.
• No Ranking Adjustments: Google has explicitly stated that this technical modification does not alter how AMP pages are ranked or served within Google Search and Google Discover.
• Simplified Infrastructure: Publishers no longer need to navigate the complexities of syncing user sessions between Google’s cache domains and their own primary domains.
• Open-Source Commitment: Google remains committed to supporting the open-source AMPhtml format, even as its own proprietary hosting and viewing mechanisms are phased out of the primary search loop.

Chronology: The Rise, Reign, and Realignment of AMP

To understand the significance of this shift, it is essential to trace the history of the Accelerated Mobile Pages project from its inception as a web-altering standard to its current status as an optional legacy framework.

[Oct 2015] Google launches AMP Project to counter Facebook Instant Articles
    │
[Feb 2016] AMP officially integrates into Google Mobile Search Results
    │
[2016–2020] Peak AMP: Top Stories carousel requires AMP; publishers feel forced to adopt
    │
[Nov 2020] Google announces Page Experience Update; Core Web Vitals to replace AMP requirement
    │
[Jun 2021] Core Web Vitals roll out; AMP is no longer mandatory for Top Stories carousel
    │
[2021–2024] Mass exodus of major publishers (e.g., Search Engine Land) disabling AMP
    │
[Present] Google retires AMP Viewer, routing search traffic directly to publisher-hosted AMPs

2015: The Dawn of the Mobile Speed Era

In October 2015, Google introduced the AMP Project as an open-source initiative. The goal was to drastically improve the performance of the mobile web, which at the time was plagued by slow load times, heavy ad scripts, and poor user experiences. AMP was positioned as an open alternative to proprietary, closed-platform reading formats like Facebook Instant Articles and Apple News.

2016–2020: Carrots, Sticks, and Peak Dominance

In February 2016, Google officially integrated AMP into its mobile search results. To incentivize adoption, Google introduced the "Top Stories" carousel at the very top of mobile search results, making AMP compliance a strict prerequisite for entry.

For news publishers, this was an offer they could not refuse. The Top Stories carousel drove massive amounts of mobile traffic, forcing nearly every major media outlet to implement AMP. During this period, AMP pages were heavily cached on Google’s servers to ensure instantaneous loading, giving rise to the Google AMP Viewer.

2020–2021: The Turning Point and Core Web Vitals

By 2020, the web development community had grown increasingly vocal about the drawbacks of AMP. Critics argued that Google was using its search monopoly to dictate web standards and keep users within its ecosystem.

In response to pressure and evolving web technologies, Google announced the Page Experience Update in late 2020. Rolled out in mid-2021, this update introduced Core Web Vitals—a set of standardized metrics measuring loading speed, interactivity, and visual stability. Crucially, Google removed the requirement that pages must be in AMP format to appear in the Top Stories carousel. Any web page meeting the speed and usability thresholds of Core Web Vitals could now compete for prime search real estate.

2021–Present: The Great AMP Exodus

Once the Top Stories requirement was lifted, a wave of publishers began turning off AMP. Maintaining two parallel versions of a website (standard responsive HTML and AMP HTML) was technically burdensome and expensive. Many publishers discovered that their standard mobile sites, optimized for Core Web Vitals, performed just as well—if not better—than their AMP counterparts in terms of speed, user engagement, and ad monetization.

This latest update, where Google retires its viewer and cache-routing system, represents the final chapter in the mainstreaming of AMP, transitioning it from a heavily subsidized search requirement to just another open-source template language.

Supporting Data: Why Publishers Abandoned the Format

The decline of AMP has been documented across the web ecosystem. The decision by major digital publications to abandon the framework was driven by quantifiable business metrics, monetization challenges, and technical overhead.

The Monetization Deficit

A primary driver of the AMP exodus was the difficulty publishers faced when trying to monetize cached pages. Because AMP restricted custom JavaScript to ensure speed, publishers could not easily run their preferred header bidding wrappers, complex ad units, or paywall systems.

A study of digital publishers revealed that many experienced lower effective Cost Per Mille (eCPM) rates on AMP pages compared to their standard responsive mobile sites. The inability to deploy sophisticated ad tech directly impacted programmatic ad revenues.

Analytics Fragmentation

Tracking user behavior across the Google AMP Cache was notoriously difficult. When a user visited an AMP page via the Google Viewer, the session originated on google.com. If the user then clicked a link leading to the publisher’s main site, the session shifted to publisher.com.

[Google Search Link clicked]
         │
         ▼
[Google AMP Viewer] ──(Session 1: google.com/amp)
         │
         ▼ (User clicks internal link)
         │
[Publisher Website] ──(Session 2: publisher.com)

This split required complex "session stitching" setups to prevent analytics platforms (such as Google Analytics) from counting a single user journey as two separate, disconnected visits. This fragmentation distorted bounce rates, session durations, and conversion tracking.

The Case of Search Engine Land

The industry’s shift away from the framework is highlighted by major search marketing publications themselves. Search Engine Land officially disabled AMP across its domain in 2021. In their post-mortem analysis, the publication noted that modern responsive design, paired with optimized hosting and clean code, rendered the duplicate AMP infrastructure redundant. They suffered no loss in search visibility or mobile rankings after turning off the format, a trend mirrored by thousands of enterprise sites over the last four years.

Official Responses and Technical Details

In updating its developer documentation, Google clarified the technical realities of this transition, assuring publishers that search rankings would remain unaffected.

No Change to Search Rankings

Google has emphasized that this update is purely infrastructural. A Google spokesperson confirmed:

"Serving and ranking of AMP content in Google Search and Google Discover will remain the same. Google Search remains unchanged in terms of how it ranks AMP pages within the search results."

Publishers who still use AMP will not see a drop in their search visibility, impressions, or click-through rates as a direct result of this change.

Google’s Continued Support for AMPhtml

Despite dismantling the proprietary viewer pipeline, Google maintains that it is not abandoning the underlying technology. The company confirmed its ongoing support for the open-source AMPhtml project, stating that the format remains a viable, highly optimized pathway for creators who want to build fast-loading websites without managing extensive performance optimization workflows themselves.

Simplification of Developer Guidelines

Google updated its official developer documentation to reflect the retirement of the viewer. The updated guidelines focus on helping developers maintain clean, validated AMP pages that can be indexed and served directly from their host servers. The documentation notes that this change should make it easier for sites to create, validate, and maintain AMP pages going forward, as they no longer have to design layouts with the constraints of Google’s iframe-based viewer in mind.

Practical Implications for Publishers and SEOs

For digital marketers, publishers, and search engine optimization (SEO) professionals, this update simplifies web operations and clarifies the future of mobile web development.

1. Direct Traffic and Brand Ownership

The retirement of the AMP Viewer resolves a long-standing branding issue. When users share links to articles they find on mobile search, they will now copy and share the publisher’s direct URL rather than a Google-hosted AMP URL. This keeps users firmly within the publisher’s ecosystem, reinforcing brand attribution and site authority.

2. Streamlined Analytics and Tracking

With users landing directly on the publisher’s server, the need for complex session stitching is gone. Traffic metrics will be cleaner, bounce rates will be more accurate, and conversion funnels will be far easier to analyze. Marketers can now track user behavior from the initial search click through to deeper site engagement without accounting for third-party cache interruptions.

3. Reduced Need for AMP Maintenance

For organizations still running dual-template websites (standard HTML + AMP HTML), this update is a strong signal to re-evaluate their setup. Because Google Search no longer relies on its specialized viewer to load these pages instantly, publishers can achieve identical or superior performance by optimizing their primary responsive site to meet Core Web Vitals standards.

For many, the most logical path forward will be to deprecate their AMP templates entirely, redirecting those URLs to their standard responsive pages. This reduces development costs, simplifies content management workflows, and consolidates SEO authority onto a single, unified codebase.

Conclusion: The End of an Era for the Hosted Mobile Web

Google’s decision to bypass the AMP Viewer and send search traffic directly to publisher-hosted pages represents the quiet conclusion of a contentious chapter in web history. What began as a well-intentioned, albeit aggressive, attempt to force the mobile web to load faster has yielded to a more decentralized model.

Today’s mobile web is fast not because of proprietary caching frameworks, but because modern web standards, browser engines, and optimization techniques have caught up. By stepping back from hosting and serving publisher content under its own banner, Google has restored the natural flow of the open web—reconnecting searchers directly with the creators who publish the content.