Google sends AMP clicks to publisher URLs
Google has updated how it routes search users to AMP content in Google Search. Previously, clicks from organic results often landed on cached AMP pages delivered through the so-called AMP viewer. Going forward, Google will redirect users directly to publisher-hosted AMP URLs. The change affects the critical moment between a SERP click and the actual page view – and therefore measurement, branding, and technical maintenance of AMP projects.
Accelerated Mobile Pages have long been a central tool for fast mobile news and content delivery. Publishers created valid AMP variants of their articles while Google, in many cases, served a cached copy via its own domain. For users, it felt like a seamless jump into a lean article; for site owners, it meant a split infrastructure of canonical URL, AMP HTML, and viewer logic. SEO leads therefore had to monitor two parallel delivery paths at all times.
What specifically changes in the click path
The decisive difference lies in the destination URL after a click from search. Instead of a cached presentation in the AMP viewer, Google now opens the original AMP page on the publisher's domain. Users immediately see the environment controlled by the provider – including header, navigation, consent banner, and custom tracking implementation, provided these are correctly embedded on the AMP variant.
For SEO teams, this means traffic flows more strongly to their own infrastructure. Domain authority, internal linking, and publisher branding can benefit because less visibility remains inside the Google viewer. At the same time, pressure increases to keep AMP pages technically stable, fast, and measurable, since errors or slow response times are no longer hidden behind a Google cache layer. News teams with a high mobile share should prioritize the switch in their technical SEO roadmaps.
Google's rationale and strategic background
According to Google, the change simplifies maintenance of AMP content for publishers and reduces upkeep effort. The previous cache and viewer mechanism required alignment between the original AMP page, canonical tags, and the version cached by Google. Discrepancies could lead to inconsistencies in updates, consent dialogs, or ad integration. With direct delivery, an intermediate step that many editorial and technical teams could only influence indirectly is removed.
The decision fits a broader pattern: Google is giving publishers more control over the end-to-end experience while the special role of classic AMP pathways in the overall ecosystem declines. For years, many websites have invested in Core Web Vitals, server-side rendering, and lean mobile templates. AMP remains relevant for selected publishers but loses its special status when the standard URL delivers the same speed. The new redirect reflects that development.
Technical SEO checks after the change
Publishers should now review their AMP URLs systematically. This includes valid AMP markup, correct canonical linkage to the HTML version, working redirects, and consistent meta data. Load time of the directly served AMP page also gains weight because it no longer comes primarily from the Google cache. Server response times, CDN configuration, and image optimization should be reassessed in Search Console and PageSpeed reports.
A common mistake is an outdated AMP variant that diverges in content from the canonical HTML page. After the change, users and search engines notice this more quickly. Structured data, Open Graph tags, and internal links on AMP pages should also be compared regularly with the main version. Publishers using AMP ads or paywall logic must verify that all components work reliably on the directly served URL.
Impact on analytics, tracking, and conversions
When users land directly on the publisher domain, referrer patterns and session start points change. Teams must ensure AMP traffic is clearly captured in Google Analytics, Search Console, and tag management solutions. Consistent UTM parameters, clean separation of AMP and non-AMP sessions, and valid consent logic on the AMP page itself are especially important. Misconfigurations become visible faster because less traffic runs through the viewer.
For conversion tracking, the change means events that previously fired only after a viewer jump now start directly on the publisher domain. Marketing teams should run test clicks from mobile Google Search and verify whether sign-ups, newsletter forms, or commerce events are measured correctly. A/B tests on AMP content gain relevance because the user experience is closer to the real production environment.
| Aspect | Previously (AMP viewer) | Now (publisher AMP) |
|---|---|---|
| Destination after SERP click | Cached page in viewer | Publisher's original AMP URL |
| Branding | Stronger Google environment | Stronger publisher domain |
| Maintenance | Cache and viewer dependency | Direct publisher responsibility |
| Performance measurement | Partly cache-distorted | More realistic server and load times |
Recommendations for publishers and SEO leads
Editorial teams with active AMP inventories should set up an audit plan. Priority goes to top-traffic AMP URLs, errors in Search Console, and pages with high impressions from mobile search. In parallel, it is worth comparing AMP and canonical HTML for content, structured data, and internal linking. Publishers maintaining AMP only for legacy reasons can use the change as an opportunity to reassess real value against modern Core Web Vitals optimization on the standard URL.
- Check top AMP URLs for validity, speed, and canonical tags.
- Validate tracking and consent on directly served AMP pages.
- Monitor Search Console reports for AMP errors and mobile experience.
- Optimize CDN and server response after the viewer cache is removed.
- Reassess AMP strategy against regular mobile performance.
The change marks a clear break in AMP usage within Google Search. Publishers will host AMP more visibly on their own domain while Google scales back the previous cache-viewer step. For SEO and technical teams, this means more control but also more immediate responsibility for quality, measurability, and maintenance of every AMP URL.
