Google Starts Highlighting AMP Pages In Its Mobile Search Results
Smartphones and networks are constantly getting faster, but somehow the mobile web now feels slower than it ever did. That's largely thanks to all the ads and trackers that most sites now use (and maybe the abundance of large GIFs, too).
Context & Ripple Effects
AMP arrived as a set of loading constraints — restricted JavaScript, banned iframes, new AMP-specific elements — and Google's move to highlight those pages in mobile search is the distribution carrot attached to them. The company had already started surfacing AMP articles inside its iOS search app, so this extends an existing pattern from app to mobile web results.
The stakes become clear downstream: within months Google said links would route straight to the AMP version when one exists, and adoption hit 2B pages across 900K domains. But publishers were already reporting that an AMP pageview earned roughly half of what a full mobile pageview did, because the format's standardized ad units limit their inventory.
First-order effects
- Publishers who adopted AMP's constrained format gain prominent placement in Google's mobile results, while non-adopters risk losing visibility on the surface where most news traffic originates.
Second-order effects
- Publishers face a direct revenue trade-off: the same standardized ad units that make AMP fast cap monetization, pushing large outlets to weigh search traffic volume against per-pageview yield.
Third-order effects
- If the pattern holds, Google effectively sets web formatting standards through search distribution rather than standards bodies — publishers build to the platform's spec because the platform controls the audience, a dynamic that prefigures today's debates over who controls how content is served in search.
The trend: Search platforms are using ranking and presentation privileges to dictate how the mobile web is built, trading publisher monetization control for speed.