Google AMP accused of stealing publishers traffic, by directing search traffic to cached snapshots of sites at Google-hosted URLs
I run my blog on WordPress with a custom theme. 6 month ago I've added support for Accelerate Mobile Pages (AMP) in order to provide better user for mobile devices.
Context & Ripple Effects
Alex Kras's post is an early publisher-side counterpoint arriving months after WordPress.com began serving AMP automatically and self-hosted sites could switch it on with a plugin — exactly the setup he runs. His complaint targets what AMP has been since its 2015 launch: a constrained page format whose restrictions on Javascript and tags like iframes produce fast pages that can live at Google-hosted URLs rather than the publisher's own domain.
The accusation reads differently with hindsight the corpus supplies: [[a:932701|Chartbeat later found only a third of the 159 publishers adopting AMP in 2017 saw clear statistical evidence of a traffic increase]], and [[a:1158829|an unredacted antitrust complaint alleges Google gave AMP a comparative boost by delaying non-AMP ads by a second]]. The Verge's retrospective frames the whole program as having spent down publishers' trust in Google.
First-order effects
- Publishers who enabled AMP through WordPress's automatic support or plugin see mobile search visitors land on Google-hosted cached snapshots, so the visit accrues to Google's URL and analytics rather than their own property.
- Kras and similarly situated independent publishers face a tradeoff between AMP's promised speed benefit and ceding the destination of their search traffic.
Second-order effects
- Measurement vendors like Chartbeat become the arbiters of whether AMP pays, and their finding that most adopters lacked clear traffic gains pressures publishers to re-evaluate the format they switched on wholesale via WordPress.
- The alleged throttling of non-AMP ads gives advertisers and publishers grounds to treat AMP participation as coerced rather than chosen, feeding the antitrust case against Google.
Third-order effects
- If hosting publisher content at the intermediary's URL becomes standard for 'fast' delivery, the open web's addressability erodes toward platform-controlled access surfaces — the pattern the corpus traces from AMP's constraints through the trust collapse The Verge documents.
- Sustained publisher grievances of this kind push search distribution itself into regulatory scope, as the unredacted complaint shows AMP becoming evidence in antitrust proceedings rather than merely a web standard.
The trend: Platform-hosted 'faster' versions of publisher content mark an early chapter in intermediaries capturing the access surface to the open web, with AMP as the template case.