What Is AMP In SEO

AMP stands for Accelerated Mobile Pages, an open-source HTML framework Google launched on October 7, 2015, to make mobile pages load near-instantly. For several years it was a near-prerequisite for appearing in Google’s Top Stories carousel on mobile, which gave it outsized importance in SEO conversations, even for sites that were not news publishers.

That requirement is gone. Google removed the AMP-only rule for Top Stories eligibility in June 2021, and the framework is no longer treated as a direct ranking factor. You may have heard that AMP is dead in 2025, and in the SEO sense that is mostly accurate. The real question for most teams is no longer what AMP does, but whether rebuilding templates in it still pays off, or whether those engineering hours are better spent on Core Web Vitals, the page-speed signals Google actually uses in ranking today.

How AMP Actually Works Under the Hood

AMP is built on a stripped-down version of HTML that swaps standard elements for custom tags. Standard <img> becomes <amp-img>, <video> becomes <amp-video>, and tracking pixels go through <amp-analytics>. The framework also bans almost all custom JavaScript and caps inline CSS at 75 KB. Those restrictions are what force the resulting pages to render so quickly on slow mobile connections.

Beyond the code restrictions, Google ran a pre-rendering and caching layer called the AMP Cache. Valid AMP pages were stored on Google’s edge servers and served from cache.googleapis.com, geographically close to each visitor. Combined with the restrictions above, this produced page loads under a second on a typical 4G connection, the original performance target Google set when the project launched. None of that is magic. It is what you get when you remove the slow parts of the web and serve the result from a CDN the size of Google’s, and for a few years that combination was hard to beat on a phone.

Why Google Created AMP and Why Publishers Adopted It

Mobile web pages in 2015 routinely took 10 to 20 seconds to load on a 4G connection. Research at the time showed roughly 75% of mobile users would abandon a page that took more than 4 seconds to become interactive, which put most publisher sites in a losing position from the first tap.

Google launched AMP on October 7, 2015 as an open-source project to fix that. By early 2016, the framework had become a hard requirement for the Top Stories carousel, the premium block of news articles that appeared above standard mobile search results. Publishers had little choice but to comply if they wanted that placement.

The Washington Post, The Guardian, and CNN rebuilt their article templates in AMP to capture the spot, and a popular WordPress plugin made the format accessible to smaller publishers. Within two years, AMP had gone from a technical experiment to a default expectation for any serious news site, and the count of AMP pages in Google’s index climbed into the hundreds of millions.

The 2021 Turning Point: Google Drops the AMP Requirement

In May 2020, Google announced its Page Experience signals, a set of user-centric metrics that would feed into the search ranking systems. The following June, on June 17, 2021, the company removed the AMP requirement for Top Stories eligibility, meaning any fast page meeting the new Core Web Vitals thresholds could now appear in the carousel. AMP stopped being a special door to that premium placement and became one of many ways to be fast.

The retreat was quick. WordPress dropped default AMP support in 2022, and major publishers including CNET, BBC, and Gizmodo publicly retired their AMP versions, citing the analytics complications and the steady drop in Top Stories traffic to AMP URLs. Google also removed the AMP-specific rich results report from Search Console, leaving publishers without a dedicated reporting surface. Within eighteen months, AMP had gone from must-have to optional to largely abandoned for most use cases.

Should You Still Use AMP in 2025? A Practical Decision Framework

When AMP Might Still Make Sense

AMP is still reasonable to keep for large news publishers who pull meaningful traffic from Google’s Top Stories carousel and lack the engineering capacity to hit Core Web Vitals thresholds on their own CMS template, specifically LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. If your team is small, your CMS is unwieldy, and your Top Stories impressions still come mostly from AMP URLs, an existing AMP setup is a defensible thing to keep running, and Clickside can help you stress-test that decision with a quick mobile audit. It is not, however, a sensible thing to build from scratch in 2025.

When You Should Skip AMP

AMP pages restrict custom JavaScript, which blocks most modern ad networks and any on-page personalization, and the limited tag set makes analytics, A/B testing, and conversion tracking more complicated than on a standard page. Modern frameworks like Next.js and Astro already deliver sub-second mobile loads on standard HTML, which makes the case for AMP even thinner. The real downsides in practice:

• Restricted JavaScript blocks most modern ad networks and on-page personalization
• Limited tag set makes analytics, A/B testing, and conversion tracking harder to implement
• No ranking or rich-result preference over a fast standard HTML page

The Better Modern Alternative

Spend that engineering effort on Core Web Vitals instead, since they are the page-speed signals Google actually uses in ranking in 2025, and a fast standard page will outperform an AMP page in every metric that matters.

The Bottom Line on AMP and SEO

AMP is still a valid open-source framework, but in 2025 it is rarely worth implementing for SEO, since Google dropped the ranking advantage four years ago and the engineering cost of maintaining a separate AMP template almost never beats the cost of just making your standard mobile pages fast. Run your top mobile templates through PageSpeed Insights and fix the worst LCP and INP issues first, because that is where the actual ranking signal lives now, and Clickside routinely helps teams interpret what those numbers actually mean for their site.