What Is Accelerated Mobile Pages (AMP)?
Written byFlavio Amiel Founder, Roborank
Accelerated Mobile Pages (AMP) is an open-source HTML framework, launched by Google in 2015, for building mobile pages that load almost instantly using restricted markup, a controlled JavaScript library, and cached delivery. Once a requirement for Google’s Top Stories carousel, AMP lost its ranking advantages in 2021 and is now largely a legacy technology.
- AMP was announced by Google on October 7, 2015, and AMP versions of pages began appearing in mobile search results in February 2016.
- AMP restricts HTML, requires its own JavaScript library, and pages can be served from a cache (such as the Google AMP Cache) for near-instant loading.
- The project moved to the OpenJS Foundation on October 10, 2019, rather than remaining solely Google-controlled.
- In April 2021 Google removed the AMP badge icon from search results, and the June 2021 Page Experience update dropped AMP as a requirement to appear in Top Stories.
- Since 2021, non-AMP pages that pass Core Web Vitals and page-experience criteria are eligible for the same placements, removing AMP’s main SEO incentive.
How Accelerated Mobile Pages Works
AMP is an open-source HTML framework built for one goal: making mobile pages load almost instantly. It achieves that by taking away choices. AMP HTML is a restricted subset of standard HTML — many tags are disallowed and all styling must be inline and size-capped. Custom JavaScript is banned in favor of a single required AMP runtime library that manages resource loading so nothing on the page can block rendering. Layouts must declare element dimensions up front, which eliminates the reflows that jank a normal page during load.
The final speed multiplier is caching. Because AMP pages follow a strict, validatable format, platforms can safely pre-cache and preload them. Google’s AMP Cache, for instance, could serve a stored copy of an article from Google’s own infrastructure, which is why AMP results in Search often appeared to open the moment they were tapped. The tradeoff for that speed was rigidity and a second version of every page to maintain alongside the canonical one.
From Requirement to Legacy
AMP’s adoption curve was driven by access, not affection. The timeline is well documented:
- October 7, 2015 — Google announces AMP; AMP pages start appearing in mobile results in February 2016.
- October 10, 2019 — the project moves to the OpenJS Foundation, loosening sole Google control.
- April 2021 — Google removes the AMP badge icon that had distinguished AMP results.
- June 2021 — the Page Experience update drops AMP as a requirement for the Top Stories carousel.
That June 2021 change is the hinge. For years, only AMP pages could appear in the mobile Top Stories carousel, a placement valuable enough to justify the maintenance burden. Once Google tied eligibility to Core Web Vitals and other page experience signals instead, any sufficiently fast page qualified.
Example of Accelerated Mobile Pages
The decisive documented event is Google’s Page Experience update, detailed on the Search Central blog in April 2021 and rolled out to mobile starting in mid-June 2021. Google announced that the Top Stories feature in Search “will be updated to include all news content, as long as it meets the news content policies” — explicitly removing the previous rule that restricted the carousel to AMP pages. A few months earlier, in April 2021, Google had already stopped marking AMP results with a distinguishing icon.
The consequence is verifiable in the incentives, not just the announcement. Before June 2021, a publisher’s honest answer to “why do you run AMP?” was usually “because Top Stories requires it.” After June 2021, that answer no longer held: a non-AMP article that passed Core Web Vitals became equally eligible. Several publishers subsequently documented dropping AMP with little or no traffic loss. The lesson generalizes past AMP itself — when a platform gates a valuable placement behind a specific technology, adoption reflects the gate, not the merits, and the moment the gate opens the real value of the technology gets tested on its own. For AMP, that test moved it firmly into legacy status.
AMP is the clearest cautionary tale in technical SEO: a format the whole industry adopted not because it was good architecture but because Google gated a valuable placement behind it. For years the honest reason to run AMP was "Top Stories requires it," full stop. When Google removed that gate in 2021, the true cost-benefit surfaced — a second parallel version of every article to build and maintain, a restricted subset of HTML, and analytics and monetization that never quite worked like the canonical page. My advice in 2026 is straightforward: don’t start new AMP work, and if you carry a legacy AMP setup, plan its retirement by making your canonical pages fast enough to pass Core Web Vitals on their own. Speed is still the goal. AMP is no longer the required path to it.
Frequently Asked Questions
Is AMP still necessary for SEO in 2026?
What was Accelerated Mobile Pages designed to do?
Does AMP still get preferential treatment in Google Search?
Should I remove AMP from my site?
The Bottom Line
Accelerated Mobile Pages was Google’s answer to slow mobile web pages: a locked-down HTML framework, a mandatory JavaScript runtime, and cache-served delivery that made articles load in an instant. Its real leverage was access to the Top Stories carousel, and when Google removed that gate in 2021 in favor of page-experience signals, AMP’s rationale collapsed. It still works, but it is now legacy — a technology to maintain reluctantly or migrate away from, not one to adopt.
Sources
- Accelerated Mobile Pages — Wikipedia
- A more detailed look at the Page Experience update — Google Search Central
Rank & Cash — the weekly SEO breakdown
One practical teardown a week on ranking in search and getting cited by AI. No fluff.