Was AMP ever a Google ranking factor? No. Google has said this directly, more than once, in its own words: AMP was never a direct factor in organic rankings. The evidence grade on this claim is debunked. What made AMP look like an SEO advantage was a mix of two real things that had nothing to do with a ranking bonus: faster delivery, and, for a while, access to the mobile Top Stories carousel. Those were genuine benefits. They just were not the benefit people assumed.
If you are weighing whether an old AMP recommendation still deserves budget, this is the distinction that matters, and it is worth working through slowly rather than taking on faith either way.
What the AMP ranking claim actually said
AMP stands for Accelerated Mobile Pages, a web page format Google introduced to deliver faster, more consistent pages on mobile. For this question, you do not need the technical details of how AMP builds a page. You need to know whether using the format itself earned a page a ranking bonus.
Google's answer has stayed the same since the format launched: no. The AMP ranking factor idea collapses two separate questions into one. The first question is whether Google uses AMP as an input to how it orders search results. It does not. The second question is whether AMP could help a page perform better in ways that mattered to search visibility, like loading faster or landing in a prominent feature. It could, historically, and that is a different claim entirely.
"Does AMP help SEO" is the broader, more honest version of this question. It allows for an answer like "sometimes, indirectly, for reasons that have nothing to do with the format being rewarded." "Is AMP a ranking factor" only has one honest answer, and it is no.
Why AMP looked like an SEO advantage
Four things happened close together, and they got blended into one story.
The first is that AMP and faster loading showed up at the same time. When Google rolled AMP out more broadly in September 2016, it paired the announcement with concrete performance claims: a median load time of less than one second for AMP pages served from Google Search, and data use the company described as ten times lower than the non-AMP equivalent. Google was clear that this was a performance story, not a ranking change. The problem is that performance and ranking got tangled in people's heads anyway, because faster pages often did better for reasons search engines genuinely do reward, like lower bounce and better user experience signals downstream.
The second is Top Stories eligibility. Starting in February 2016, only AMP pages could appear in the mobile Top Stories carousel. That is a real, legitimate reason a news publisher adopted AMP: it opened a door that non-AMP pages could not walk through. But eligibility for a specific search feature is not the same thing as a general ranking preference. A publisher could gain visibility through Top Stories while getting zero extra weight in ordinary organic rankings, and that is exactly what Google says happened.
The third is the AMP label itself. When Google rolled AMP support wider in 2016, mobile search started showing a small label on pages built with the format. A visible label next to a result is the kind of thing that can shape a searcher's behavior, but Google's own announcement at the time said plainly: "This doesn't change Search results." The label marked a technical property of the page, not a ranking signal.
The fourth is the easiest one to get wrong: traffic increases got mistaken for ranking proof. A publisher adopts AMP, sees more traffic, and assumes the only variable that changed was the ranking position of their pages. In reality, a traffic change can come from a faster experience, a new feature slot, seasonality, or a dozen other things happening at once. A traffic increase can be real while the explanation attached to it is wrong.
What the traffic evidence really showed
The strongest empirical counterweight to the ranking myth is not another Google statement. It is a 2018 research collaboration between Chartbeat, a publisher analytics company, and The Daily Beast, which ran two different studies worth separating out.
The first was a randomized experiment inside The Daily Beast's own publishing workflow: newly published articles were split, with half served as AMP and half in the standard format. That controlled test did not find clear statistical evidence of higher Google-driven page views for the AMP version. One publisher's experiment is not proof of what every publisher would see, but it is a real data point against the idea that AMP reliably drove more search traffic on its own.
The second study looked across 159 publishers, including The Daily Beast and 158 other Chartbeat-enabled sites that adopted AMP in 2017, spanning ten countries and a mix of local and national news, sports, and lifestyle content. This was a before-and-after time-series analysis, not a controlled experiment, and it found an average traffic effect of plus 22%, with wide variation across individual publishers. Only 34% of the publishers in the sample showed a statistically significant traffic increase at the 95% confidence level. The study found no significant correlation between the size of the effect and factors like when a site implemented AMP, how much traffic it already had, or what kind of content it published.
Read that carefully and it tells you something more useful than a single number. An average traffic lift existed across this sample, but most individual publishers did not show a result strong enough to call statistically significant, and the characteristics researchers checked did not explain why some sites moved and others didn't. That is a pattern consistent with AMP sometimes helping through faster delivery or feature access, inconsistently, for reasons that varied by site, which is a very different story from "AMP boosts rankings."
It is also worth being precise about what this study measured. It measured traffic, not ranking position. A traffic increase could come from more impressions in a feature slot, better click-through from a faster-loading preview, or other causes that never touch where a page sits in ordinary search results. None of that traffic data tells you anything directly about Google's ranking algorithm.
What Google actually said about AMP and speed
Google did not leave this ambiguous, and the statements span a decade.
In April 2010, Google's Amit Singhal and Matt Cutts announced that site speed had become a new signal in search ranking, affecting fewer than 1% of queries at the time and applying only to English searches on Google.com. This predates AMP by years. Speed, as a ranking consideration, has its own separate history, and it is worth holding onto that fact because it is easy to assume AMP introduced speed into Google's algorithm. It didn't. Speed was already there.
In August 2016, when Google previewed wider AMP support across search results, engineer Nick Zukoski wrote: "To clarify, this is not a ranking change for sites." That same month's expanded rollout came with the performance claims mentioned earlier, framed explicitly as a product story, not a ranking one.
In November 2017, Product Manager Ashish Mehta put it even more plainly: "AMP is not a ranking signal and there is no change in terms of the ranking policy with respect to AMP." That announcement also introduced a content-parity policy, effective February 2018, requiring AMP pages to match their canonical versions closely. Pages that failed could lose Top Stories eligibility. Google was explicit that this was about feature eligibility, not search ranking.
In January 2018, Google announced the mobile Speed Update, rolling out fully by that July. The update targeted pages delivering the slowest mobile experience, affecting a small percentage of queries, and it applied, in Google's own words, "the same standard to all pages, regardless of the technology used to build the page." A slow page with great, relevant content could still rank well, because relevance remained a much stronger signal than speed. This is the clearest possible statement that the speed standard was technology-neutral. It rewarded fast pages, whatever software built them, not AMP pages specifically.
In December 2020, Google Product Manager Rudy Galfi wrote the most direct version of the answer, in an article called "The benefits of AMP": "AMP has never been a ranking factor in organic search results on Google." The same article acknowledged the Top Stories restriction, putting both facts side by side: no ranking bonus, but a real feature-access requirement that existed for years. That pairing is the clearest single source for the distinction this whole question turns on.
By April and June 2021, Google announced it was removing the AMP requirement for Top Stories, rolling the change out through that summer. That is worth reading correctly: Google removed an eligibility requirement for a specific feature. It did not remove a ranking factor, because by Google's own repeated statements, there was never a ranking factor to remove. Google's documentation, most recently updated in 2026, still describes AMP pages as indexed and evaluated under the same standard as any other page, regardless of the technology behind them.
The verdict and what to do differently
The AMP mobile ranking myth, that using the format alone earned a page a ranking bonus, is debunked. This is not a close call or an ongoing debate. Google said it in 2016, said it again in 2017, said it most explicitly in 2020, and its current documentation still treats AMP pages the same as any other HTML page for ranking purposes.
What would change this verdict is a specific, explicit statement from Google naming AMP itself as a ranking input, or evidence strong enough to isolate format preference from speed, content quality, and feature access as separate variables. Nothing in the historical or current record meets that bar, and a single new before-and-after traffic study wouldn't either.
So what should you actually do if an old brief, an agency, or a legacy playbook still frames AMP as an SEO requirement? Separate the pitch into its real components. Ask whether the claim is about a ranking preference, a performance improvement, or eligibility for a specific search feature, because those are three different things with three different levels of evidence behind them. If someone tells you "Google ranks AMP pages higher," that claim is false on its face. If someone tells you "a faster version of this page might perform better," that is a separate, testable claim worth evaluating on its own terms, the same way you'd evaluate any page speed project. And if you already have AMP running and it is not causing problems, debunking the ranking myth is not, by itself, a reason to rip it out. The absence of a ranking bonus does not tell you anything about the operational cost or benefit of your current setup.
The broader habit worth taking from this is to ask what actually improved before crediting the technology label for it. A faster page, a new feature slot, and a ranking change are three different outcomes, and conflating them is how SEO myths like this one get started and keep circulating for a decade after the source has said otherwise.
