Google AMP: new docs and direct routing
Google has updated its official AMP documentation for search engines and publishers. The focus is on simplification: outdated references to the AMP viewer, the AMP cache, and signed exchanges have been removed. At the same time, Google Search is changing how users are routed from search results to AMP pages. Instead of passing through intermediate steps in the Google ecosystem, clicks will now go directly to the publisher's AMP host page. For teams that still use AMP, this means less technical maintenance and clearer expectations around rankings and crawling.
Accelerated Mobile Pages, or AMP, long served as a standard for especially fast mobile content. Publishers delivered validated AMP HTML variants while Google accelerated delivery through cache and viewer mechanisms. Over time, maintenance requirements grew: cache updates, signed-exchange configurations, and inconsistent documentation made operations harder. The current update clears these legacy elements from Search documentation and realigns user routing.
What changed in the AMP documentation
The revised pages under Crawling and Indexing focus on what publishers actually need to implement today. References to the AMP viewer, the central AMP cache, and signed exchanges as mandatory integration paths have been removed. These components played a central role in earlier AMP strategies when Google often served cached copies. Teams that use the documentation as a technical reference should mirror internal playbooks and checklists against the new version so outdated instructions no longer sit in editorial or dev workflows.
For SEO and tech teams, the documentation remains the authoritative source for valid AMP implementations, canonical handling, and indexing behavior. Cleanup reduces misinterpretation: teams no longer invest in cache paths or exchange setups that are no longer relevant for current Google Search operations. That lowers onboarding costs and speeds up audits of existing AMP templates.
New routing in Google Search
The most important operational change concerns the click path from organic results. Previously, users could land via Google-internal AMP delivery; going forward, they will be redirected directly to the publisher's AMP URL. This change simplifies the user experience and makes the publisher's domain the clear entry point again. For analytics, consent management, and tag implementations, this can have measurable impact because sessions start more consistently on the origin domain.
Google explicitly states that AMP content can continue to rank like any other web page. This is not the end of AMP as a format, but a modernization of how it connects to Search. Publishers that keep AMP for performance or editorial reasons should not expect a ranking disadvantage, provided pages remain technically valid, fast, and strong in content.
Less maintenance for publishers
A central promise of the announcement is reduced maintenance effort. Publishers no longer need to actively update the AMP cache or configure signed exchanges to stay compatible with the new delivery logic. That especially relieves newsrooms and large portals running hundreds of AMP variants in parallel. Resources can instead flow into Core Web Vitals, structured data, and content quality.
Practical impact on technical SEO
Despite simplification, classic SEO fundamentals remain valid. AMP pages still need a clean link to the canonical HTML version, correct meta data, and error-free indexability. Teams should check in Search Console whether AMP URLs are still captured without crawling errors and whether mobile usability remains stable. Because users land directly on publisher hosts, origin delivery performance gains importance: slow servers or aggressive ad blocks immediately affect perceived speed.
| Area | Before | Now |
|---|---|---|
| Documentation | Notes on viewer, cache, signed exchange | Focus on publisher host and valid AMP |
| Click from search | Often via Google AMP delivery | Direct link to publisher AMP page |
| Maintenance | Cache updates and exchange setup | No extra cache or exchange maintenance |
| Ranking | AMP as a rankable format | Still rankable like other pages |
Recommendations for publishers and SEO teams
If you still use AMP productively, update internal documentation and monitoring setups first. Remove checklist items on signed exchanges and cache maintenance from runbooks. Then verify whether tracking and consent solutions correctly capture direct entry on your domain. Comparing organic CTR before and after rollout helps spot unexpected jumps early, even though Google is not announcing a ranking change.
Publishers that have already phased out AMP mainly benefit from clearer official guidance: Search documentation better reflects today's operations and reduces confusion in stakeholder discussions. For new projects, it is worth asking whether AMP still adds value compared with modern responsive design and server-side performance optimization. The decision should depend on measurable load times, editorial effort, and conversion data, not outdated cache assumptions.
- Keep AMP documentation current and update internal guides.
- Check Search Console for crawling and AMP errors after the routing update.
- Validate tracking and consent for direct publisher URLs.
- Treat origin AMP page performance as the new bottleneck.
- Weigh AMP use strategically against responsive HTML and Core Web Vitals.
The update marks another step in normalizing AMP within Google Search. The format and rankings remain, but technical overhead drops. Teams that align processes now with the new documentation and direct routing avoid unnecessary maintenance and focus SEO work more strongly on content, speed, and reliable indexing.
