Short answer: AMP (Accelerated Mobile Pages) is an open source HTML framework, launched by Google in 2015, for building lightweight pages that load fast on mobile. It is not a Google ranking factor, and since June 2021 it is no longer required for Top Stories. Google indexes valid AMP pages like any other page, so for most sites today a fast, responsive page that passes Core Web Vitals does the same job with less maintenance.
This guide is for site owners, bloggers and developers who have seen AMP in a plugin setting, a Search Console report or an old SEO checklist and want to know what it is, whether it still helps, and what to do with existing AMP pages. By the end you will be able to decide whether to keep, add or retire AMP, and how to do each safely.
What is AMP?
AMP stands for Accelerated Mobile Pages. Google announced the project in October 2015, partly as a response to Facebook Instant Articles and Apple News, which were keeping readers inside their apps. The idea was simple: if publishers built pages using a restricted, predictable subset of HTML, those pages could be cached and preloaded and would open almost instantly from search results.
An AMP page is made of three parts:
- AMP HTML: normal HTML with some tags replaced by AMP components (for example
<amp-img>instead of<img>) and a cap on how much CSS you can include. - AMP JS: a single library that controls how resources load. Your own custom JavaScript is heavily restricted, which is where much of the speed comes from.
- AMP caches: content delivery networks, such as Google’s AMP Cache, that store a validated copy of the page and serve it from their own servers.
Most AMP pages are “paired”: a normal (canonical) page lives at one URL and an AMP version lives at another, often ending in /amp/. The canonical page points to the AMP version with a rel="amphtml" link, and the AMP page points back with a canonical tag. A site can also be “standalone” AMP, where the AMP page is the only version.
Does AMP help SEO in 2026?
Not directly. AMP has never been a ranking factor in its own right. Google’s documentation says it indexes AMP pages just like other web pages and that its usual best practices apply to them too (Google Search Central). What AMP used to give you was access to placements:
- Top Stories carousel: until 2021, non-AMP news articles were not eligible. With the page experience update, Top Stories stopped using AMP as an eligibility factor from June 2021, and the lightning-bolt AMP badge started to go away (Search Engine Land).
- Instant loading from results: AMP pages could be preloaded from Google’s cache. Fast non-AMP pages now compete on the same footing through Core Web Vitals.
So the honest answer is that AMP can still help indirectly if it is the only way you can make a slow site fast. But the ranking systems reward a good page experience, not the AMP framework. If your normal pages already pass Core Web Vitals on mobile, AMP adds little except a second version of every URL to maintain.
Why adoption has fallen
The HTTP Archive’s Web Almanac found the AMP HTML attribute on just 0.19% of mobile home pages and 0.07% of desktop home pages in 2022, both down on the previous year (Web Almanac). Once AMP stopped being a ticket to Top Stories, many publishers decided the design limits, split analytics and double maintenance were no longer worth it.
Rather have an expert do this for you?
Hand it over and get back to running your business.
AMP vs a fast responsive page
When I run a mobile SEO review, this is the comparison I walk owners through. The question is not “is AMP fast?” (it usually is) but “is it worth running two versions of every page to get that speed?”
| Factor | AMP page | Optimised responsive page |
|---|---|---|
| Speed | Fast by default, because the framework blocks most heavy code | Fast only if you do the work: image sizing, caching, lean scripts |
| Ranking benefit | None for AMP itself | Same: rankings look at content quality and page experience |
| Top Stories eligibility | Eligible | Eligible since June 2021 |
| Design freedom | Limited CSS, AMP components only, restricted custom JavaScript | Full control |
| Forms, chat, pop-ups, tracking | Need AMP-specific components; many third-party tools do not work | Work as normal |
| Analytics | Needs separate AMP analytics setup; sessions can split between cache and your domain | One setup |
| Maintenance | Two templates, validation errors to monitor | One template |
| Who serves the page | Often an AMP cache rather than your server | Your server or CDN |
Pros and cons of AMP
Where AMP still earns its place
- Publishers on a slow, locked-down CMS. If you cannot fix the main templates (a legacy platform, an agency-controlled theme), an AMP layer can give mobile readers a fast article page quickly.
- High-volume news and blog content. Articles are mostly text and images, which is exactly what AMP handles well.
- Slow mobile networks. In markets where many readers browse on patchy mobile data, a very light page matters. I see this with Pakistani news and recipe sites, where a heavy theme with several ad scripts can take a long time to become usable on a mid-range Android phone.
The costs owners underestimate
- Lost conversions. Lead forms, WhatsApp buttons, live chat and booking widgets often break or disappear on AMP versions. I have audited sites where the AMP version of a service page had no working enquiry form at all.
- Content drift. Google expects users to see the same content and complete the same actions on the AMP page as on the canonical page, where possible. In practice the AMP template often lags behind: missing tables, FAQs, schema or author boxes.
- Messy reporting. Traffic served from a cache can appear as a separate referrer or split sessions unless analytics is configured for AMP.
- Brand and design limits. Stripped-down templates can look generic, and some JavaScript-driven features simply cannot be built. If your site depends on scripts, my guide to JavaScript SEO is a better place to start.
Should you use AMP? A quick decision
Answer these questions in order. It reflects the decision process I use with clients, and every result ends in a concrete next step.
Should you keep, add or remove AMP?
Does your site already publish AMP versions of its pages?
Do your normal (non-AMP) pages pass Core Web Vitals on mobile in Search Console or PageSpeed Insights field data?
Can you realistically fix the speed of your normal templates in the next few months (theme, hosting, scripts)?
Are you a news or content publisher whose main templates are slow and cannot be changed?
Result: plan to retire AMP. Your main pages are already fast, so AMP is only adding maintenance and splitting your data. Follow the removal steps below: remove the amphtml links, redirect AMP URLs to the canonical pages, then watch Search Console.
Result: fix the main site first, then retire AMP. Keep AMP running while you improve the canonical templates. Once they pass Core Web Vitals on mobile, remove AMP with redirects.
Result: keep AMP for now, but keep it in step. Make sure AMP pages are valid, carry the same content, schema and calls to action as the canonical pages, and check the AMP report in Search Console monthly. Revisit when you rebuild the site.
Result: AMP is a reasonable short-term option. It can give readers a fast article page while the main platform stays slow. Treat it as a stopgap and budget for a faster theme or CMS.
Result: do not add AMP. Put the effort into one fast responsive page: compressed images, good caching, fewer third-party scripts. That helps every visitor and every search engine, not only Google on mobile.
To check where you stand, run your key templates through my free PageSpeed checker and compare the AMP and non-AMP versions of the same URL.
How to implement AMP correctly
If the decision above says AMP makes sense for you, set it up properly. A half-working AMP layer is worse than none.
- Choose paired or standalone. Paired AMP is the usual choice on existing sites. Host AMP URLs on your own domain, for example under
/amp/or a subdomain, not on an unrelated domain. - Use a maintained tool. On WordPress, the official AMP plugin offers three template modes, explained below. Other platforms usually have an equivalent integration.
- Keep content parity. The AMP version should carry the same main content, images, structured data, author information and conversion paths as the canonical page.
- Link the pair.
rel="amphtml"on the canonical page,rel="canonical"on the AMP page. - Validate. Google says AMP pages must be valid to work as expected. Test with Google’s AMP Test tool and monitor the AMP report in Search Console.
- Set up AMP analytics. Configure your analytics for AMP so cache-served visits are attributed correctly.
WordPress AMP plugin modes
| Mode | How it works | When I would use it |
|---|---|---|
| Standard | One theme, one version of the site, and that version is AMP | Rarely; only if the whole theme is AMP-compatible and you accept its limits everywhere |
| Transitional | One theme, with an AMP and a non-AMP version of each page | When you want AMP for articles but keep full functionality on the main site |
| Reader | A separate, simpler theme for AMP pages | Quick setup for blogs, but watch closely for missing content and broken forms |
How to remove AMP without losing traffic
Most of the AMP work I do now is removal. Google’s documentation sets out the steps (Google’s AMP removal guide), and the order matters:
- Make the canonical pages fast first. Otherwise mobile users go from a fast AMP page to a slow one. My non-technical speed guide covers the main fixes.
- Remove the
rel="amphtml"link from every canonical page so Google stops discovering AMP versions. - Redirect every AMP URL to its canonical page with a 301 (or 302). On WordPress, deactivating the plugin alone often leaves
/amp/URLs returning errors, so add the redirect rule yourself. Test a sample with the redirect checker. - Do not blank the AMP files. Google treats empty documents as invalid and can keep showing the last valid cached version.
- Monitor. Watch the indexed AMP pages line fall in the Search Console AMP report, and compare mobile clicks for the affected URLs before and after.
Better ways to get AMP-level speed
Everything AMP enforces, you can do on your own templates. These are the fixes that usually close the gap:
- Images: correct dimensions, modern formats, lazy loading below the fold.
- Hosting and caching: page caching plus a CDN. See my guide to hosting, caching and CDNs.
- Third-party scripts: audit ad, chat and tracking scripts; they are the most common reason a page fails Interaction to Next Paint.
- Lean CSS and fonts: remove unused CSS and limit font weights.
- Discover and news visibility: large images, strong titles and fast pages matter more than the framework. My guide to optimising for Google Discover goes into detail.
For a broader look at front-end performance, read my web performance optimisation guide. Speed is one part of improving your search results, not a substitute for useful content.
Frequently asked questions
Is AMP a Google ranking factor?
No. Google indexes AMP pages like other pages and applies the same best practices. Page experience, including Core Web Vitals, is considered by its ranking systems, and a fast non-AMP page can do just as well.
Do I need AMP to appear in Google Top Stories?
No. Since the page experience update rolled out from June 2021, Top Stories no longer uses AMP as an eligibility requirement. News content needs to be timely, helpful and follow Google News policies.
Is Google AMP dead?
The framework still exists as an open source project and Google still supports AMP pages in Search, but adoption is small and falling. For most new sites there is no reason to start with it.
What happens if I disable the AMP plugin in WordPress?
Your /amp/ URLs may start returning errors while Google still has them indexed. Remove the amphtml links and redirect each AMP URL to its canonical page so visitors and link value land in the right place.
Does AMP cause duplicate content problems?
Not when it is set up correctly. The AMP page declares the normal page as canonical, so Google treats them as a pair. Problems start when the canonical tag is missing or points to the wrong URL.
Is AMP good for e-commerce sites?
Usually not. Carts, filters, personalisation and payment flows depend on JavaScript that AMP restricts. A fast responsive store is the safer route.
Sources
- Google Search Central, “Understand how AMP works in Search results” (last updated 2026).
- Google Search Central, “Remove AMP pages from Google Search” (2026).
- Search Engine Land, “Google page experience update now slowly rolling out” (2021).
- HTTP Archive, “Web Almanac 2022: SEO chapter” (2022).
- web.dev (Google), “Web Vitals” (2024).
If you are unsure whether your AMP pages are helping or quietly costing you leads, my website speed optimisation service includes an AMP review and a safe removal plan where it makes sense. You can also get in touch with a specific question.
Request received
Thank you! Saad will contact you within the next 24 hours.
Keep an eye on your phone and inbox.