Google ending cache-served AMP makes publisher URLs the evidence surface
Google Search now sends AMP clicks to the publisher’s own AMP host page instead of Google’s AMP viewer, AMP Cache or signed-exchange serving path. AMP still ranks, but ownership of the served URL, measurement and evidence layer moves back to the publisher.
Editor’s Note by Dageno: Dageno AI’s editorial team structurally distilled Search Engine Journal’s article “Google Ends Cache-Served AMP Pages In Search” to help GEO and AI visibility teams understand why direct publisher URLs matter for source ownership, attribution and retrieval-ready content.
Understand the article in 60 seconds
- Google removed the AMP viewer, AMP Cache and signed exchange serving path from Search. Publishers now receive searchers on their own AMP host URLs.
- AMP content can still rank like other web pages. The change is about serving and attribution, not an instruction to delete AMP.
- For GEO, the publisher-hosted page becomes the canonical evidence surface that AI systems and analytics teams can inspect directly.
- Teams should revisit AMP templates, structured data, internal links and measurement because the page users see is now the same page evidence systems evaluate.
The change moves the visible evidence layer back to publishers
SEJ reports that Google Search now routes AMP clicks directly to the domain’s AMP host page. Previously, Google could serve cached AMP through an AMP viewer with a Google URL, while signed exchanges helped preserve the original URL in some cases.
For GEO, this matters because the page that receives the user is also the page that can carry entity signals, analytics tags, consent behavior, internal links and source trust.
AMP still ranks, but the old cache-serving mental model is gone
The article is careful: AMP is not being removed as a format and AMP pages can still rank like any other page. What changed is the serving path from Google Search.
That distinction prevents bad strategy. The question is not whether AMP is dead. The question is whether AMP pages are maintained as first-party evidence assets rather than legacy speed templates.
Direct routing improves attribution only if tracking is clean
A direct publisher URL can make measurement simpler, but only if analytics, consent, canonical tags and redirect behavior are correct. Otherwise teams may still misread AMP traffic, AI-assisted search behavior and downstream conversions.
AI visibility teams should annotate the July 1 routing change and compare AMP landing behavior before and after the switch.
The history of AMP shows why platform dependencies should be monitored
Google dropped AMP as a Top Stories requirement in 2021 and retired the lightning-bolt icon. Google News on mobile had already begun bypassing AMP URLs. This Search change continues the same direction.
The GEO lesson is that platform delivery layers can change while content assets remain. Teams need monitoring that separates format eligibility, serving path and answer visibility.
Publisher-owned pages need stronger evidence design
Once users and crawlers land on the publisher host, thin AMP templates become a bigger liability. The page should expose authorship, dates, product facts, internal context, related assets and structured data.
AI systems need extractable evidence. Direct routing means the publisher can control that evidence more completely, but it also removes excuses for incomplete pages.
What direct AMP routing changes for AI visibility
The user-facing URL is the publisher’s AMP host page.
Entity and source trust signals should live on the page itself.
Analytics sees more first-party landing behavior.
Teams can connect search, AI referral and conversion quality more cleanly.
AMP pages can no longer rely on Google-hosted presentation.
Evidence density, links and schema become first-party responsibilities.
Google can change delivery layers without changing rank eligibility.
Monitoring should separate rankings, clicks and citation surfaces.
AMP pages should be managed as first-party evidence assets
| Team / owner | What changes | Signal to monitor |
|---|---|---|
| SEO team | Audit canonical, AMP HTML, schema and indexability after direct routing. | AMP impressions, clicks and index coverage. |
| GEO team | Test whether AMP pages are cited or summarized in AI answer surfaces. | Citation rate for AMP versus canonical pages. |
| Analytics team | Compare pre- and post-change sessions, source attribution and engagement. | Landing-page quality and assisted conversions. |
| Content team | Upgrade AMP templates with authorship, context and related internal links. | Pages with sufficient extractable facts. |
| Publisher operations | Remove legacy assumptions about Google-hosted AMP presentation. | Rendering, consent and ad behavior on AMP host URLs. |
Signals that show whether direct AMP routing is helping or hiding value
- AMP host page crawl status
- Search clicks before and after July 1
- Canonical and AMP URL attribution split
- AI citation rate for AMP assets
- Engagement and conversion quality by AMP landing page
Turn AI visibility signals into execution.
Dageno AI is a complete execution platform from data monitoring → strategy → content generation → result attribution. Use it to monitor AI answer surfaces, find strategy gaps, generate content actions and connect visibility shifts to business impact.
Alexa for Shopping