Google Sends AMP Traffic Directly
Google updated AMP documentation, saying Search now sends users directly to publisher-hosted AMP pages instead of legacy AMP delivery surfaces.
The News
Google Search Central updated its AMP documentation in July 2026, saying Google Search is changing how it connects users to AMP pages and will now take users directly to publisher AMP host pages. The documentation also removes outdated references to the AMP viewer, AMP Cache, and signed exchange. Google says AMP content will continue to rank like any other web page, making this a technical discovery change rather than a ranking-system announcement.
The OPTYX Analysis
This is a technical discovery signal because Google is simplifying the delivery path between indexed AMP URLs and the publisher-controlled destination. The mechanism is AMP delivery simplification, reducing dependence on Google-hosted viewer and cache assumptions that shaped analytics, canonical validation, signed exchange configurations, and cache update workflows. Strategically, Google is normalizing AMP into the broader web-document model instead of maintaining special delivery infrastructure. The change matters because AMP implementations still live inside large publisher stacks, template systems, and performance governance programs.
Enterprise Impact
The exposed operator is the publisher SEO lead, platform engineer, analytics owner, or CMS team still maintaining AMP templates. The opportunity is lower operational overhead where AMP cache refreshes, signed exchange handling, and viewer-specific tracking logic can be retired or simplified. The vulnerability is stale AMP instrumentation if referral parsing, canonical checks, consent scripts, ad tags, or pageview deduplication still assume Google-hosted AMP surfaces. Required next move is an AMP control audit covering analytics attribution, canonical parity, cache dependencies, template ownership, and retirement criteria for remaining AMP inventory.