Google Search: direct links to publisher AMP pages

Google has adjusted how AMP pages are served in Search: clicks from Google Search will now take users directly to publisher-hosted AMP URLs. Previously, searchers often landed in the Google AMP viewer with cached copies. For publishers, SEO teams, and editorial departments, the change mainly means more control over analytics, tracking, and the technical maintenance of AMP content – without any change to ranking logic.

The announcement comes at a time when AMP is no longer central in many newsrooms. Still, the change matters because it simplifies the data flow between Google Search, the publisher domain, and measurement tools. Anyone still running AMP variants or maintaining older implementations should understand the new delivery model and check whether reports, consent management, and conversion tracking work correctly.

What changes for AMP clicks in Google Search

Until now, Google Search could serve AMP content through a viewer that displayed cached versions of the page. From now on, Search connects users directly with AMP host pages on the publisher domain. Google states that users will be taken straight to publisher-hosted AMP pages instead of going through the intermediary viewer.

For end users, the switch often feels subtle: pages still load quickly, and the visible Google frame disappears in many cases. For site operators, the main change is where traffic originates in the logs. Referrers, session starts, cookie context, and tag manager events will run more consistently through the publisher's own domain instead of partly ending in the viewer context. That makes it easier to attribute organic clicks to content, authors, and conversion paths.

Rankings and Discover remain unchanged, Google says

Google explicitly stresses that nothing changes in how AMP content is evaluated in organic results. AMP pages should continue to rank like any other webpage. Serving in Google Search and Google Discover also remains the same, according to the company. For SEO teams, that is the key takeaway: this is a delivery and infrastructure change, not a new ranking signal or an AMP comeback.

Anyone who turned off AMP in recent years or never adopted it does not need to fear ranking upheaval. Those who still use AMP can treat the change as simplification, not as added optimization pressure. At the same time, AMP is not a shortcut to better positions – preferential treatment in areas such as Top Stories has been gone for a long time. Visibility still depends on relevance, user signals, and technical quality, not on the format label alone.

Why Google is making the switch

According to Google, the adjustment should make life easier for publishers. Simpler analytics management and tracking are the main goals. The company also promises lower maintenance effort when creating and maintaining AMP pages. The open AMPhtml specification remains supported; Google points to updated documentation in its Search developer updates. For developers, that means existing AMP templates do not need to be shut down immediately, but they should be checked for outdated viewer dependencies.

AMP in the context of publisher strategies in 2026

AMP was once heavily promoted as a fast mobile format for news sites. Over time, the format lost strategic importance: many large publishers turned off AMP because the added value compared with responsive HTML and modern Core Web Vitals optimization shrank. Google's adjustment of viewer delivery fits this maturity stage – AMP remains technically available but is not a central lever for visibility.

SEO editorial teams benefit from a sober view: does the project still need parallel AMP URLs, or is a performant canonical version enough? The new direct delivery makes operations less friction-heavy but does not replace a broader content or technical strategy. Those who keep AMP mainly gain clearer measurement data and fewer special cases in reporting. Editorial teams should also verify whether paywalls, newsletter modules, and ad units on AMP pages work identically under the new delivery model.

Technical and editorial impact in detail

In practice, the change mainly affects three layers: server logging, client-side tracking, and editorial workflows. Server logs will consistently show the publisher domain as the target host. That simplifies analysis in BI tools that previously had to filter out viewer URLs. On the client side, consent layers and A/B tests can fire more reliably because users no longer start in a Google-hosted viewer context.

For international publishers with multiple language versions, it remains important to maintain clean hreflang and canonical relationships between AMP and HTML variants. The delivery change does not replace technical SEO work on structured data, load times, or internal linking. However, it reduces friction in performance measurement – an often underestimated benefit for data-driven editorial teams.

Practical checklist for SEO and analytics teams

After rollout, teams should first check whether Search Console data and server logs show consistent sessions for AMP URLs. Tag manager containers, consent banners, and paywall scripts must fire as intended on directly accessed AMP pages. Internal dashboards that previously excluded viewer traffic can be simplified. A short before-and-after comparison over seven to fourteen days provides reliable signals on whether measurement gaps have closed.

• Monitor AMP URLs in Search Console for click and impression trends.
• Check analytics properties for correct hostnames and referrers.
• Validate canonical tags and hreflang between AMP and HTML versions.
• Review existing AMP templates for outdated viewer assumptions.
• Document whether AMP will continue to be operated long term.

Publishers that keep AMP only for historical reasons can use the change as a prompt to reassess their technical footprint. Those who retain the format gain a pragmatic step toward cleaner measurement through direct linking – without new ranking promises from Google.