Google AMP Is
Bad for the Web
Google's Accelerated Mobile Pages promised a faster web. What it delivered was a clever mechanism to pull publishers off their own domains and into Google's ecosystem — and call it a feature.
Fast-loading pages are a legitimate goal. Nobody disputes that. The question is whether achieving them requires handing your content over to Google — served under Google's domain, cached on Google's servers, inside Google's walled garden.
It doesn't. Clean, semantic HTML and well-structured CSS can deliver fast, functional, beautifully designed pages without the trade-offs AMP demands. The web already has the tools. AMP was never really about speed.
What AMP Actually Does
When Google launched Accelerated Mobile Pages, the pitch was simple: implement AMP and your pages load faster on mobile. That part is true. But the mechanism matters.
AMP content is not served from your server. It is cached and delivered from Google's own infrastructure, under Google's own domain. A reader clicking your article in search results is not visiting your site. They are visiting Google's copy of your site, hosted at a Google URL.
For users, the distinction is invisible. For publishers, it is significant. Traffic metrics are distorted. Brand URLs disappear. Canonical authority shifts. The publisher does the work; Google owns the relationship.
The Search Ranking Lever
Google has officially stated that AMP support does not directly affect search rankings. That is technically accurate and practically misleading.
Google has been explicit that pages which render slowly on mobile devices will be penalized in search rankings. AMP pages, served from Google's cache, render fast by design. The logical conclusion for publishers was unavoidable: implement AMP or risk falling behind competitors who did.
There is also the carousel. Google's Top Stories carousel — prime real estate at the top of mobile search results — was, for years, exclusively available to AMP-enabled content. For major publishers, that placement represents enormous traffic. The incentive structure could not have been clearer.
Domain Authority Erosion
When content is served from Google's cache under a Google URL, publishers lose direct brand exposure and risk diluting the canonical authority their own domains have built over time.
Ecosystem Lock-In
AMP creates dependency on Google's infrastructure and validation rules. Publishers who build around it become structurally reliant on a single platform's continued goodwill and priorities.
A Problem That Didn't Need AMP
Slow mobile pages are caused by bloated JavaScript, unoptimized images, and render-blocking resources. Those are solvable with good engineering — not a proprietary framework controlled by a search monopoly.
The Open Web Argument
"When your content is served from someone else's domain, you are a tenant — not an owner."
Facebook's Instant Articles made the same trade. Load fast, inside our app, on our terms. Publishers signed up, traffic numbers looked good, and then the algorithm changed. The lesson was expensive.
AMP follows the same logic. The open web's core principle is that a URL points to a resource on the origin server — the publisher's server. AMP breaks that contract quietly, with a loading spinner and a speed test to justify it.
The good news is that the web has largely moved on. Google opened Top Stories to non-AMP pages in 2021. Core Web Vitals replaced AMP as the performance standard that actually affects ranking. Publishers who invested heavily in AMP are now quietly unwinding it.
Write Clean HTML
Semantic, minimal markup loads fast and is accessible by default. Complexity is usually the problem, not the solution.
Optimize Your Images
Properly sized, compressed images in modern formats like WebP account for the majority of performance gains on most pages.
Audit Your JavaScript
Most render-blocking performance issues trace back to unnecessary or poorly loaded scripts. Defer, lazy-load, and cut what isn't earning its place.
Measure With Core Web Vitals
Google's own performance standards — LCP, CLS, FID — give you a clear, actionable target without requiring any proprietary framework.
The Bottom Line
AMP solved a real problem — slow mobile pages — with a solution that served Google's interests far more than it served publishers or the open web. The technical case for it has weakened as better performance standards emerged. The strategic case for it was always thin.
Fast pages are achievable without surrendering your domain, your traffic data, or your independence to a platform whose priorities will inevitably shift. The web already has everything you need.
Build fast pages. Own your URLs. Keep your content on your servers. The open web is worth defending — and it doesn't require Google's permission.
BriteWire is a digital studio based in Bozeman, Montana. Google opened the Top Stories carousel to non-AMP pages in June 2021.