Skip to main content
Zhihe Growth 中文
Platform updates · Google Search

Google Changes AMP Navigation: Implications of Direct Publisher-Domain Access

On July 1, 2026, Google announced that Search would send users directly to publisher-hosted AMP pages and removed outdated AMP Viewer, AMP Cache and signed exchange guidance. The change concerns delivery, domains and analytics, not an extra ranking benefit for AMP.

Author: Zhihe Growth Research Center Original publication: Date of event/observation: Sources checked: 2026-07-22

Key Takeaway

The change does not inherently increase AMP rankings or AI citation weight. Existing AMP sites should check final landing URLs, analytics continuity, canonicals and dependencies on the old cache or delivery path. Sites without AMP do not need to adopt it solely for GEO.

What's the official change?

Google Search Central's July 1, 2026 documentation update removed outdated AMP Viewer, AMP Cache and signed exchange references. It explained that Search would link directly to publishers' AMP hosts and continue ranking AMP content like other pages. Publishers therefore need to verify the URLs, certificates, performance and analytics of their own delivery path.

Delivery and indexability are separate. Pages still need appropriate status codes, crawl access, correct canonicals and complete usable content. AMP is a delivery format, not an AI-search format or a substitute for visible HTML, entity information and evidence. Keep AMP and non-AMP facts, titles and structured data consistent.

Event Date 2026-07-01
Delivery change Search links directly to publisher-hosted AMP pages
Ranking treatment AMP content continues to rank like other web pages

Implications for International Brands

For international brands, the immediate concern is domain ownership and attribution. Direct visits can simplify management of landing URLs, referrers, consent, first-party cookies and conversion paths. Compare session sources, engagement, cross-domain events and conversions before and after the change; measurement changes are not necessarily changes in search demand.

Direct delivery also makes origin responsibilities more apparent: speed, availability, images, fonts, regional networks, HTTPS and error handling. Problems previously obscured by caching may become visible. Test real target regions, devices and cold-cache behavior rather than relying only on laboratory scores.

URL governance remains important. Conflicting canonicals across language, mobile, parameterized and AMP versions may lead Google to select an unexpected URL. Do not omit restrictions, sources or dates from AMP knowledge and evidence pages; successful retrieval of incomplete content still yields incomplete facts.

Zhihe Growth's Assessment

Zhihe Growth views this as an infrastructure change, not a new GEO shortcut. Sites with reliable responsive pages should prioritize server performance, visible content, images, international CDN delivery and language consistency before adding another AMP maintenance path.

Sites with substantial AMP content should audit search landing pages, canonicals, structured data, analytics tags, advertising, consent, cache headers and errors. Retain AMP where it delivers demonstrable user or template-management value, not because its name implies an AI-search advantage.

Implementation Checklist

  1. 1. Sample AMP landing URLs from Google Search and check their final HTTPS host.
  2. 2. Compare AMP and non-AMP canonicals, titles, content, structured data and update dates; resolve factual differences.
  3. 3. Test origins, CDNs, images and fonts in target markets, not only with local Lighthouse runs.
  4. 4. Check GA4, advertising and consent behavior and attribution on direct visits; annotate measurement changes.
  5. 5. Review old AMP Cache, signed exchange and cross-domain dependencies; remove only those confirmed unnecessary.
  6. 6. Before retiring AMP, prepare URL mappings, 301 redirects, sitemap changes and Search Console monitoring.

Limitations

The announcement addresses delivery and documentation, not promised crawl frequency, rankings, click-through rates or AI citations. Display still depends on indexing, quality, relevance and page status.

The original article's review date was July 22, 2026. Whether to retain AMP depends on traffic, template costs, regional performance and business functions; the announcement alone does not justify a universal migration decision.

Official sources