What Is Accelerated Mobile Pages (AMP)? (2026)

Accelerated Mobile Pages (AMP) was once considered essential for any publisher wanting visibility in Google’s Top Stories carousel - but the landscape has changed significantly since its 2015 launch. In 2021, Google removed the AMP requirement for Top Stories, and by 2026 the technology has settled into a much narrower role than its early advocates predicted. If you are wondering whether AMP is still worth implementing, or what happened to the advantage it once offered, this guide gives you the full picture.

TL;DR: Key Takeaways

AMP (Accelerated Mobile Pages) is an open-source framework created by Google to enable near-instant loading of mobile web pages.
AMP pages are stripped-down HTML versions of web pages cached and served directly from Google’s CDN.
In 2021, Google removed the AMP requirement for Top Stories on mobile, reducing AMP’s competitive advantage for news publishers.
By 2026, AMP is no longer a significant SEO ranking advantage. Passing Core Web Vitals with standard optimized HTML pages is equivalent.
AMP remains relevant for publishers already using it, but new sites generally do not need to implement AMP to be competitive.

What Is Accelerated Mobile Pages (AMP)?

Accelerated Mobile Pages (AMP) is an open-source web framework originally created by Google and Twitter in 2015. It is designed to make web pages load extremely fast on mobile devices by using a restricted version of HTML, streamlined CSS, and a JavaScript framework that prioritizes speed above all else.

AMP pages load near-instantly because they are pre-cached on Google’s servers (the AMP CDN). When a user taps an AMP result in Google search, the page is already loaded in the background: the experience feels nearly instant because the content is served from Google’s infrastructure rather than the publisher’s server.

This article is for publishers, developers, and SEO practitioners who want to understand what AMP is, whether it is still relevant in 2026, and what to do instead if they choose not to implement it.

How AMP Works

AMP achieves its speed through several technical mechanisms:

AMP HTML

A subset of HTML with custom tags and restricted features. Many standard HTML elements are replaced with AMP-specific equivalents: <amp-img> instead of <img>, <amp-video> instead of <video>. This forces a minimal, fast-loading markup structure.

Asynchronous JavaScript Only

AMP restricts synchronous (render-blocking) JavaScript, which is a primary cause of slow page loads. All AMP JavaScript loads asynchronously and third-party scripts are heavily restricted.

CSS Inline and Size-Limited

All CSS must be inline (in the <head> section) and is limited to 75KB. This eliminates render-blocking external CSS files.

Pre-Calculation and Pre-Loading

The AMP runtime pre-calculates page layout before any resources load, eliminating layout shifts. Resources are loaded in priority order based on what is visible in the viewport.

Google AMP Cache

Google pre-fetches and caches AMP pages on its global CDN. When users search on Google, AMP results are pre-loaded in the background. Tapping an AMP result delivers the pre-cached version instantly.

The result: AMP pages typically load in under 1 second on mobile, compared to the industry average of 3 to 7 seconds for non-AMP pages in 2015 (when AMP was introduced).

History of AMP

2015: Google and Twitter announce the AMP Project as an open-source initiative to improve mobile web speed.

2016: AMP launches in Google search with the “AMP lightning bolt” icon next to AMP results in the Top Stories carousel on mobile.

2016 to 2020: Google gives AMP pages preferential placement in the Top Stories carousel for mobile users. News publishers that do not have AMP are effectively excluded from Top Stories, driving widespread adoption among major publishers.

2021: Google announces the page experience update, with Core Web Vitals as the metric for evaluating page speed. Critically, Google removes the AMP requirement for Top Stories: any page that passes Core Web Vitals can now appear in Top Stories, with or without AMP.

2022 onwards: AMP’s strategic importance diminishes significantly. Google depreciates some AMP-specific features and the project transitions to a more independent open-source governance model.

2026: AMP remains in use by many publishers who implemented it years ago, but new implementations are rare. Core Web Vitals optimization with standard HTML has become the primary performance strategy.

AMP and SEO: What Changed in 2021 and Beyond

The most important AMP-related SEO change happened in June 2021 when Google’s page experience update launched. Before this update:

AMP was required to appear in the Top Stories carousel on Google mobile search
The “AMP lightning bolt” icon in search results was a visible differentiator

After the update:

Any page that passes Core Web Vitals can appear in Top Stories
The AMP lightning bolt icon was removed from search results
AMP is no longer a direct ranking factor

This change fundamentally altered AMP’s value proposition. The primary reason publishers adopted AMP (Top Stories eligibility) no longer requires AMP. A fast, well-optimized standard HTML page achieves the same result.

Benefits of AMP

Extremely fast load times: AMP pages consistently achieve sub-second load times due to restricted markup and Google cache delivery.

Reduced server load: Because Google serves cached AMP pages, traffic spikes (from viral articles) put less load on your own infrastructure.

Automatic Core Web Vitals compliance: Well-implemented AMP pages almost always pass Core Web Vitals by design, given their structural restrictions.

Pre-fetching in search: Google still pre-fetches AMP pages in mobile search results, giving AMP pages a slight perceived speed advantage even after the 2021 update.

Easy Content API: AMP stories and email are specialized formats that extend beyond web pages and still have relevant use cases for some publishers.

Drawbacks of AMP

Development and maintenance overhead: Maintaining both a standard HTML version and an AMP version of your content requires duplicate work and increases the risk of content drift between versions.

Design restrictions: AMP’s restrictions on HTML, CSS, and JavaScript limit design flexibility. Complex interactive elements, custom animations, and advanced tracking require AMP-specific workarounds or are simply not possible.

Loss of URL ownership in cached results: When users access AMP pages through Google search, the URL bar historically showed a Google cache URL rather than your domain URL. While AMP has addressed this somewhat with Web Packaging, the issue affected brand trust for some publishers.

Restricted analytics and tracking: Most third-party JavaScript is not allowed in AMP, which can complicate advertising, A/B testing, personalization, and advanced analytics implementations.

Reduced ad revenue in some cases: Publisher reports from 2017 to 2020 indicated AMP pages sometimes earned lower ad RPMs due to reduced advertiser demand for AMP inventory.

Should You Still Use AMP in 2026?

The answer depends on your situation:

If You Already Have AMP Implemented

There is generally no urgent reason to remove existing AMP. If your implementation is stable, your pages pass Core Web Vitals, and your team is not spending significant time maintaining AMP, keeping it causes no harm. You may still see benefits from Google’s AMP pre-fetching.

If You Are Building a New Site or CMS

In 2026, AMP is not necessary for new implementations. Instead, invest your development time in:

Achieving Core Web Vitals pass (LCP, INP, CLS) on standard HTML pages
Image optimization (WebP, lazy loading, proper sizing)
Eliminating render-blocking resources
Using a fast hosting provider or CDN

A well-optimized standard HTML page can achieve equivalent load performance to AMP for most use cases.

For News Publishers Seeking Top Stories Visibility

Passing Core Web Vitals is now the requirement for Top Stories eligibility. AMP is one way to achieve this, but not the only way. Evaluate whether your standard pages already pass Core Web Vitals before investing in AMP.

For Heavy JavaScript Single-Page Applications

AMP is not a practical solution for SPAs. Focus on server-side rendering, progressive enhancement, and Core Web Vitals optimization instead.

AMP Alternatives: Core Web Vitals and Fast HTML

If you are not using AMP and want to achieve maximum mobile page speed, focus on these areas:

Core Web Vitals Optimization

Google’s three Core Web Vitals are the primary performance ranking signals:

Largest Contentful Paint (LCP): Target under 2.5 seconds
Interaction to Next Paint (INP): Target under 200 milliseconds
Cumulative Layout Shift (CLS): Target under 0.1

Test with Google PageSpeed Insights (free) and the Core Web Vitals report in Google Search Console.

Image Optimization

Images are typically the largest contributors to page weight. Optimize by:

Converting to WebP format
Setting explicit width and height attributes to prevent layout shifts
Using lazy loading for images below the fold
Serving appropriately sized images using responsive image syntax (srcset)

Eliminate Render-Blocking Resources

Defer non-critical JavaScript and CSS. Load critical CSS inline in the <head>. Use the async or defer attribute on JavaScript files.

Use a CDN and Fast Hosting

A content delivery network (CDN) serves assets from servers geographically close to each visitor, reducing latency. Upgrading to a faster hosting provider can dramatically improve server response time (TTFB).

See our broader discussion of technical SEO in our guide on SEO rankings.

Frequently Asked Questions

Is AMP still used in 2026?

Yes, by many publishers who implemented it in 2016 to 2020. However, new AMP implementations are rare, and the technology is no longer recommended as a first-choice solution for page speed. Core Web Vitals optimization on standard HTML is the current best practice.

Does AMP help with SEO rankings in 2026?

Not directly. AMP is no longer a ranking signal or a requirement for any SERP feature. Passing Core Web Vitals (which AMP helps achieve) is a ranking signal, but standard optimized HTML pages achieve the same Core Web Vitals scores without AMP.

Do I need AMP to appear in Google Top Stories?

No. Since June 2021, any page that passes Core Web Vitals (and meets Google’s news content guidelines) is eligible for Top Stories. AMP is not required.

Can AMP hurt my SEO?

Not directly. However, poorly implemented AMP (especially if the AMP and canonical versions have different content) can create duplicate content issues and confuse search engines about which version to rank.

What is the AMP cache URL issue?

When users click an AMP result from Google search, the URL historically showed a Google AMP cache URL (google.com/amp/...) rather than your actual domain URL. This was a brand trust concern for many publishers. Google addressed this partially with technologies like Web Packaging/Signed Exchanges, but adoption has been limited.

Conclusion

AMP was a transformative technology when it launched in 2015, offering publishers a path to near-instant mobile load times and preferential placement in Google search results. Its importance has diminished significantly since Google removed the AMP requirement for Top Stories in 2021.

In 2026, AMP is a stable but declining technology. Existing implementations can remain in place without harm, but new sites and publishers should focus on achieving Core Web Vitals compliance through standard HTML optimization rather than implementing AMP.

The goal, achieving fast, excellent user experiences on mobile, has not changed. The recommended path to get there has.