Google ended the AMP Viewer handoff. Your origin now owns the visit

Implementation brief · SEO

The AMP visit moved. The ranking standard did not

Google removed the Viewer and Cache handoff on 1 July 2026. The useful response is an origin acceptance test, not a new ranking theory.

1. Search now opens the publisher host directlyThe visible AMP URL and the delivered response belong to the publisher, without a Google Viewer or Cache layer in the documented path.
2. AMP did not receive a ranking demotionGoogle says AMP content continues to rank like any other page. Technology does not replace the ordinary quality standard.
3. The origin visit is now the decisive evidencePerformance, consent, analytics, advertising and session continuity must work on the publisher response that the reader actually receives.
4. Canonical parity remains an editorial contractAn AMP variant still needs valid markup, a sensible URL and the same content and actions as its corresponding canonical page.

Google's July 2026 AMP update is easy to misread as either a funeral or a comeback. It is neither. Google Search changed the route between a result and an AMP document: the click now goes directly to the publisher's AMP host page. References to the AMP Viewer, AMP Cache and signed exchange were removed from Search documentation because those delivery mechanisms are no longer part of the documented handoff.

The ranking claim stayed deliberately boring. Google indexes AMP pages like other web pages and applies the same standard regardless of the technology used to build them. What changed is operational ownership. A cached success can no longer stand in for the visit that matters, because the reader reaches the publisher origin and encounters its response headers, consent state, analytics, ad stack and performance budget directly.

The cached success case no longer proves the origin visit

Under the previous model, a team could maintain several partially overlapping proofs. The AMP document had to be valid, the canonical relationship had to be coherent, the Cache had to refresh, and a signed exchange could preserve the publisher URL while Google served the content. Debugging often began by asking which layer supplied the response.

The direct-host model removes that ambiguity from the reader path. A click that fails because of a redirect loop, an edge rule, an absent consent script or an origin-only JavaScript error is now a publisher failure without a delivery intermediary to absorb it. Conversely, the same route makes first-party server logs and real-user measurements easier to interpret because they describe the visit Search actually initiated.

The ranking contract stayed still while delivery moved

Google's current AMP guidance says the pages are indexed like other pages and judged by the same standard. That sentence blocks two convenient but unsupported conclusions. Direct hosting does not create a ranking boost, and the removal of the Viewer does not amount to an AMP penalty. Search still needs a crawlable, indexable and useful document; the rendering technology does not exempt it from those requirements.

The distinction matters during migration reporting. If impressions move after the delivery change, the update itself is not enough to explain why. A release can also alter canonicals, redirects, structured data, content parity, page speed or measurement. Treat 1 July as the beginning of a new observation window, not as a causal label that can be attached to every change in traffic.

First-party evidence becomes the migration test

A useful acceptance test follows one real click from response to revenue instead of checking the AMP validator alone. The first proof is transport: the Search result resolves to the intended publisher host, returns a healthy status and does not add an unnecessary redirect chain. The second is experience: the page reaches its meaningful content within the expected performance budget and remains usable on mobile.

The third proof is continuity. Consent must initialize before dependent tags, analytics must preserve the landing context, advertising must render without hiding the article, and subscriptions or sign-in must survive the direct arrival. None of those properties is a ranking factor merely because it appears in this test. Together they prove that the route Google now uses is commercially and editorially complete.