CMS Plugins for Google AMP (Accelerated Mobile Pages)

AMP in 2026: The Short Version

Accelerated Mobile Pages (AMP) was Google’s answer to slow mobile web in 2015 — a stripped-down HTML framework that rendered fast and got preferential placement in Google’s Top Stories carousel. For a few years it was close to mandatory for publishers.

That’s no longer the case. In June 2021, Google’s Page Experience update removed AMP as a requirement for Top Stories and ended its privileged position in search results. Core Web Vitals (LCP, INP, CLS) replaced AMP as the way Google measures mobile performance — and a standard responsive site that passes Core Web Vitals now gets the same treatment as an AMP page, without the framework restrictions.

Most major publishers have since abandoned AMP. The Washington Post, The Guardian, Vox Media, CNN, and BuzzFeed all moved back to responsive sites over 2021-2023, citing both performance parity with optimized responsive and roughly 20% higher ad revenue on non-AMP pages. The AMP plugin ecosystem has contracted along with demand.

That said, AMP isn’t gone. The framework still works; Google still supports the cache; and the CMS plugins listed below still function. If you’re running a high-volume news site, a content-heavy blog on limited infrastructure, or any page where response time genuinely can’t be guaranteed through normal optimization, AMP remains a reasonable option. This guide covers what AMP is, the current plugin landscape for WordPress, Joomla, and Drupal, and — crucially — when to skip AMP entirely and focus on Core Web Vitals instead.

What Is AMP?

AMP is an open-source HTML framework, originally developed by Google with a group of major publishers, that enforces a strict subset of HTML and JavaScript to guarantee fast-rendering pages. It has three components:

• AMP HTML — standard HTML with restricted tags and AMP-specific components. Inline styles are disallowed; external JavaScript is prohibited except for a whitelisted set of AMP-approved scripts.
• AMP JS library — a small runtime that manages resource loading and enforces the performance rules.
• AMP Cache — a Google-hosted content delivery cache that serves validated AMP pages from Google’s infrastructure.

The tradeoff has always been obvious: speed in exchange for control. You give up your own JavaScript, your own fonts, and a lot of visual flexibility; you get guaranteed fast rendering. In 2015 that was a compelling deal. In 2026, with HTTP/3, CDNs, modern image formats (AVIF/WebP), and Core Web Vitals as the new ranking benchmark, the same outcome is reachable on a normal responsive site.

What Happened to AMP?

The short version: Google’s relationship with AMP shifted, publishers did the math on ad revenue, and readers never really preferred it.

• June 2021 — Page Experience update. Google removed AMP as a requirement for Top Stories placement. Any page that passes Core Web Vitals is eligible, whether it’s AMP or not.
• February 2022 — AMP lightning badge removed from search results. The visual indicator that used to mark AMP results is gone.
• 2021-2023 — Major publisher exodus. Washington Post (summer 2021), Vox Media, The Guardian, CNN, BuzzFeed, and Complex Networks all rebuilt responsive mobile sites and dropped AMP.
• Publisher revenue data. Multiple media executives reported that non-AMP pages earned ~20% more ad revenue than AMP equivalents — because AMP restricts the ad formats and tracking scripts publishers rely on.
• User experience parity. With Core Web Vitals as the mobile-performance baseline, a responsive site that hits LCP < 2.5s, INP < 200ms, and CLS < 0.1 performs as well as AMP to the user and to Google.

AMP is no longer dead — Google maintains the project and the plugins below still work — but it’s firmly a niche tool in 2026 rather than a default.

Should You Still Use AMP in 2026?

Reasonable cases for keeping or adding AMP:

• You already use it and have it dialed in. Ripping out working AMP infrastructure for no reason is a waste. If your AMP pages validate and your analytics stack works, leave them.
• You run a high-volume news site where every hundred-millisecond of mobile load time matters. AMP’s guaranteed fast rendering is still a simpler path than hand-tuning CWV across hundreds of articles.
• Your hosting or theme can’t reliably hit Core Web Vitals. For shared-hosted WordPress sites on heavy themes with dozens of plugins, AMP’s forced slim profile is sometimes the path of least resistance.
• You’re optimizing for feed readers, email newsletters, or non-Google surfaces that still use AMP format (AMP for Email has its own footprint in Gmail).

Reasonable cases for skipping AMP:

• You’re starting a new site. Invest the same engineering time in Core Web Vitals optimization of your responsive site — you get the same Google treatment plus more flexibility and better ad revenue.
• Your current CWV scores already pass. The AMP layer adds nothing.
• You run e-commerce with complex product pages, interactive UI, or paywall/subscription logic. AMP’s restrictions hurt conversion too much.
• Ad revenue is primary. The 20% non-AMP revenue uplift that moved major publishers applies to smaller publishers too.

WordPress AMP Plugins

Two plugins dominate WordPress AMP implementations:

AMP (Official Plugin by Automattic et al.)

The official AMP plugin — maintained by contributors from Automattic, Google, and the AMP Project — remains the most actively developed AMP solution for WordPress in 2026. It offers three template modes:

• Standard — your entire site is AMP. Recommended for AMP-first sites.
• Transitional — your site has paired AMP and non-AMP versions of the same URL.
• Reader — AMP pages use a minimal AMP-compatible theme separate from your main site theme.

The plugin handles AMP validation, automatic component substitution (YouTube embeds, image galleries, forms), and compatibility with Gutenberg blocks. Good choice for sites where you want first-class AMP support without manually writing AMP HTML. Free; compatible with WordPress 6.x and with most modern themes and major SEO plugins (Yoast, Rank Math).

AMP for WP

AMP for WP (by Ahmed Kaludi and Mohammed Kaludi) was historically the most-installed AMP plugin and included features the official plugin lacked: a WYSIWYG AMP customizer, WooCommerce support, and a drag-and-drop page builder. It’s still available and broadly functional, though development pace has slowed compared to its 2018-2020 peak. Review the last-updated date in the WordPress plugin directory before choosing between this and the official plugin; for new installations in 2026 the official plugin is the safer pick.

Joomla AMP Extensions

JAMP — Joomla Accelerated Mobile Pages

JAMP is the most comprehensive Joomla AMP extension. It automatically converts Joomla articles to AMP HTML, handles metadata (Open Graph, Twitter Card, Schema.org), manages AMP sidebars and menus, supports AMP Analytics, and provides a robust exclusions system to help pages pass AMP validation when third-party extensions are in play. JAMP covers native single-article views by default and can be configured for EasyBlog, Kunena, and SP Page Builder. Customization covers theme, colors, logos, fonts (including Google Fonts), and custom CSS.

wbAMP (Community Edition)

wbAMP’s community edition auto-generates AMP versions of Joomla pages, advertises them to search engines via rel="amphtml", and supports multiple document types. It’s available in 9 languages and features whitelist-based AMP validation, automatic image sizing, and warnings for misconfigurations. A commercial edition adds more granular component control. wbAMP is the lighter-weight alternative to JAMP for simpler Joomla sites.

Drupal AMP Module

AMP Module for Drupal

The AMP module for Drupal (which works on Drupal 7, 8, 9, and 10) converts node pages into AMP-compliant output. Once installed, AMP-enabled node types become available at ?amp-suffixed URLs with special AMP formatters for image, text, and video fields. The module uses the AMP PHP library to analyze HTML entered in rich-text fields and correct it for AMP compliance where possible — converting images, iframes, and embedded tweets/YouTube/Instagram into their AMP equivalents automatically.

Like all Drupal themes, the AMP module can be extended via a sub-theme, which gives publishers full control over the AMP presentation without losing the automatic conversion benefits. Drupal-based news sites that have chosen to retain AMP typically use this module; it remains actively maintained though updates are less frequent than they were in 2018-2020.

AMP and SEO: What Actually Matters

The original version of this article claimed “AMP enabled pages rank higher in search engine results pages. That is simply a fact.” That’s not accurate, and Google has said so directly. Clearing up what’s actually true:

• AMP is not a ranking factor. Google has stated this repeatedly since 2021. Page experience signals (now Core Web Vitals + HTTPS + mobile-friendly + no intrusive interstitials) are.
• AMP doesn’t guarantee Top Stories placement anymore. Since June 2021, any page that passes Core Web Vitals is eligible. AMP is neither necessary nor sufficient.
• AMP can still help in practice — by making it easier to pass Core Web Vitals. The ranking benefit comes from passing CWV, not from being AMP per se.
• Non-AMP sites with good CWV often out-rank AMP sites with poor CWV. Optimization wins either way.

If your goal is mobile-search performance in 2026, focus on Core Web Vitals first. For the full playbook see our guide on page speed best practices, and for how schema markup ties into modern search and AI Overviews, see what is structured data.

Modern Alternatives to AMP

If you’re on the fence about AMP, these alternatives replace what AMP used to offer:

• Core Web Vitals optimization on responsive site. The default answer in 2026. Target LCP < 2.5s (tightened to 2.0s after March 2026 core update), INP < 200ms (< 150ms for ranking stability), CLS < 0.1.
• Modern image formats + responsive images. AVIF and WebP cut image weight 30-50% with no quality loss. <img loading="lazy"> handles below-the-fold images natively without a framework.
• A good CDN (Cloudflare, Fastly, BunnyCDN) — covers edge caching, Brotli compression, and modern-format conversion.
• WordPress performance plugins — WP Rocket, W3 Total Cache, FastPixel, and LiteSpeed Cache all handle the performance work AMP used to force.
• Progressive Web Apps (PWAs) for sites that want app-like behavior. Service workers, offline caching, and installability on home screens — none of which AMP offers.
• AMP for Email (a separate AMP variant) still has a real use case in Gmail for interactive newsletter content. That’s narrower than the web-AMP discussion above.

Frequently Asked Questions

Is AMP dead in 2026?

No, but it’s a niche tool rather than a default. Google still maintains AMP and the plugins above still work. But AMP is no longer required for Top Stories, no longer shown with a special badge in search results, and no longer a ranking factor. Most major publishers have switched back to responsive sites. New projects should start with responsive + Core Web Vitals optimization unless there’s a specific reason to add AMP.

Does AMP help SEO in 2026?

Indirectly, at best. AMP makes it easier to pass Core Web Vitals, and passing CWV is what actually influences rankings. A non-AMP site that passes CWV gets the same benefit. Google has explicitly stated AMP is not a direct ranking factor.

Why did Washington Post and other publishers drop AMP?Two reasons. First, Google removed AMP’s privileged Top Stories position in June 2021, which had been the primary incentive to maintain AMP. Second, non-AMP pages generate roughly 20% more ad revenue because AMP restricts the ad formats, tracking scripts, and custom layouts publishers rely on. Removing AMP also simplified paywall logic for subscription-based sites.

Should I use AMP on a new WordPress site in 2026?

Probably not. Unless you’re on very constrained hosting or running a high-volume news site, a well-optimized responsive site with Core Web Vitals compliance will serve you better. If you do want AMP, use the official AMP plugin (by Automattic/Google) rather than third-party alternatives — it’s the most actively maintained option.

Bottom Line

AMP isn’t dead, but it’s been demoted. What used to be the near-mandatory fast path for mobile publishing is now one option among several. If you’re already running AMP and it works, there’s no urgency to tear it out. If you’re starting fresh or considering adding it, pass first. In 2026 the Core Web Vitals route — responsive site, modern image formats, a CDN, aggressive caching, thoughtful JavaScript — gets you to the same place Google cares about, with more flexibility and a meaningful revenue upside. The plugins above still function for the cases where AMP genuinely makes sense, but those cases are narrower than they were in 2017.