AMP
Page Experience (PX) is a set of ranking signals—including Core Web Vitals (CWV)—measuring the user experience of interacting with a web page. AMP is a powerful tool which applies many optimizations and best practices automatically on your site, making it easier for you to achieve good page experience for your visitors. The official AMP Plugin, supported by the AMP team, makes it easy to bring the power of AMP to your WordPress site, seamlessly integrating with the normal publishing flow and allowing the use of existing themes and plugins.
For more videos like this, check out the ongoing AMP for WordPress video series.
The plugin’s key features include:
- Automate the process of generating AMP-valid markup as much as possible, letting users follow the standard workflows they are used to in WordPress.
- Provide effective validation tools to help users deal with AMP incompatibilities when they happen, including mechanisms for identifying, contextualizing, and resolving issues caused by validation errors.
- Provide development support to make it easier for WordPress developers to build AMP-compatible ecosystem components and build websites and solutions with AMP-compatibility built-in.
- Support the serving of AMP pages to make it easier for site owners to take advantage of mobile redirection, AMP-to-AMP linking, and generation of optimized AMP by default (via PHP port of AMP Optimizer).
- Provide a turnkey solution for segments of WordPress creators to be able to go from zero to publishing AMP pages in no time, regardless of technical expertise or availability of resources.
The official AMP plugin for WordPress is a powerful tool that helps you build user-first WordPress sites, that is, sites that are fast, beautiful, secure, engaging, and accessible. A user-first site will deliver experiences that delight your users and therefore will increase user engagement and the success of your site. And, contrary to the popular belief of being only for mobile sites (it doesn’t stand for Accelerated Mobile Pages anymore!), AMP is a fully responsive web component framework, which means that you can provide AMP experiences for your users on both mobile and desktop devices.
AMP Plugin Audience: Everyone
This plugin can be used by both developers and non-developer users:
- If you are a developer or tech savvy user, you can take advantage of advanced developer tools provided by the AMP plugin to fix validation issues your site may have and reach full AMP compatibility.
- If you are not a developer or tech savvy user, or you just simply don’t want to deal with validation issues and tackling development tasks, the AMP plugin allows you to assemble fully AMP-compatible sites with different configurations taking advantage of AMP-compatible components. The plugin helps you to deal with validation issues by removing invalid AMP markup in cases where it is possible, or altogether suppressing AMP-incompatible plugins on AMP pages.
The bottom line is that regardless of your technical expertise, the AMP plugin can be useful to you.
Template Modes
The official AMP plugin enables site owners to serve AMP to their users in different ways, which are referred to as template modes: Standard, Transitional, and Reader. The differences between them are in terms of the number of themes used (one or two), and the number of versions of the site (non-AMP, AMP). Each template mode brings its own value proposition and serves the needs of different scenarios in the large and diverse WordPress ecosystem. And in all cases, the AMP plugin provides as much support as possible in terms of automating the generation of AMP pages, as well as keeping the option chosen AMP valid. In a nutshell, the available template modes are the following:
Standard Mode: This template mode is the ideal, as there is only one theme for serving requests and a single version of your site: the AMP version. Besides enabling all of your site to be AMP-first, this has the added benefit of reducing development and maintenance costs. This mode is the best choice for sites where the theme and plugins used in the site are fully AMP-compatible. It's also a good option if some components are not AMP-compatible but the site owner has the resources or the know-how to fix them. See our showcase of sites using Standard mode.
Transitional Mode: In this mode there is also a single theme used, but there can be two versions of each page: AMP and non-AMP. The active theme is used for serving the AMP and non-AMP versions of a given URL. This mode is a good choice if the site uses a theme that is not fully AMP compatible, but the functional differences between the AMP and non-AMP pages are acceptable (due to graceful degradation). In this case, users accessing the site from mobile devices can get the AMP version and get an optimized experience which also retains the look and feel of the non-AMP version. Check out our showcase of sites using Transitional mode.
Reader Mode: In this mode there are two different themes, one for AMP pages and another for non-AMP pages, and therefore there are also two versions of the site. This mode may be selected when the site is using an AMP-incompatible theme, but the level of incompatibilities is significant without graceful degradation. It’s also a good choice if you are not technically savvy (or simply do not want to deal with the incompatibilities) and therefore want simplified and robust workflows that allow you to take advantage of AMP with minimal effort.
Different modes would be recommended in different scenarios, depending on the specifics of your site and your role. As you configure the plugin, it will suggest the mode that might be best for you based on its assessment of the theme and plugins used on your site. And, independently of the mode used, you have the option of serving all or only a portion of your site as AMP. This gives you all the flexibility you need to get started enabling AMP on your site progressively.
AMP Ecosystem
It is possible today to assemble great looking user-first sites powered by the AMP plugin by picking and choosing themes and plugins from a growing AMP-compatible ecosystem. In this context, the AMP plugin acts as an orchestrator of the overall AMP content creation and publishing process; it serves as a validator and enforcer making it easier to not only get to AMP experiences, but to maintain them with confidence.
Many popular theme and plugin developers have taken efforts to support the official AMP plugin. If you are using a theme like Astra or Newspack, or if you are using plugins like Yoast or WP Forms — they will work out of the box! You can see the growing list of tested themes and plugins.
AMP Development
Although there is a growing ecosystem of AMP-compatible WordPress components, there is still a ways to go before majority AMP compatibility in the ecosystem. If you are a developer, or you have the resources to pursue development projects, you may want in some cases to develop custom plugin or theme to serve your specific needs. The official AMP plugin can be of great help to you by providing powerful and effective developer tools that shed light into the AMP development process as it is done in WordPress. This includes mechanisms for detailing the root causes of validation issues, the contextual space to understand them properly, and methods to deal with them during the process of achieving full AMP compatibility. Read more about Developer Tools.
Getting Started
To learn more about the plugin and start leveraging its capabilities to power your AMP publishing workflow, check the official AMP plugin product site.
If you are a developer, we encourage you to follow along or contribute to the development of this plugin on GitHub.
We have put up a comprehensive FAQ page and extensive documentation to help you start as smoothly as possible.
But if you need some help, we are right here to support you in the plugin’s support forum, as well as through GitHub issues (for technical bugs and feature requests). And our thriving AMP Expert ecosystem has indie freelancers to enterprise grade agencies in case you need commercial support!
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| s*o*e*v*r*u*l.com (WP 6.3.2) | F | Jul 19, 2026 | |
| p*a*m*t*c*i*t*a*.com (WP 6.3.2) | F | Jul 19, 2026 | |
| b*i*o*a.net (WP 6.3.2) | F | Jul 19, 2026 | |
| s*b*k*p.net (WP 6.3.2) | F | Jul 19, 2026 | |
| b*k*p*o*.com (WP 6.3.2) | F | Jul 19, 2026 | |
| b*k*p*o*.net (WP 6.3.2) | F | Jul 19, 2026 | |
| a*u*a*o*g.net (WP 6.3.2) | F | Jul 19, 2026 | |
| a*u*a*o*g.org (WP 6.3.2) | F | Jul 19, 2026 | |
| i*d*h*t.net (WP 6.3.2) | F | Jul 19, 2026 | |
| d*b*k*p*n*o.net (WP 6.3.2) | F | Jul 19, 2026 | |
| b*k*p*u*.net (WP 6.3.2) | F | Jul 19, 2026 | |
| b*k*p*u*.org (WP 6.3.2) | F | Jul 19, 2026 | |
| c*a*w*n*8.net (WP 6.3.2) | F | Jul 19, 2026 | |
| m*c*n*s*a*7*.net (WP 6.3.2) | F | Jul 19, 2026 | |
| m*c*n*s*a*d.net (WP 6.3.2) | F | Jul 19, 2026 | |
| m*c*n*s*a*3*.com (WP 6.3.2) | F | Jul 19, 2026 | |
| m*c*n*s*a*7.com (WP 6.3.2) | F | Jul 19, 2026 | |
| c*a*w*n*d.com (WP 6.3.2) | F | Jul 19, 2026 | |
| a*l*s*e*1*8.com (WP 6.3.2) | F | Jul 19, 2026 | |
| a*l*s*e*4*.com (WP 6.3.2) | F | Jul 19, 2026 | |
| a*a*t*a*i*i*i*a.com (WP 7.0.2) | F | Jul 19, 2026 | |
| k*n*u*g*8*.com (WP 7.0.2) | F | Jul 18, 2026 | |
| m*g*8*8*i*k.com (WP 7.0.2) | F | Jul 18, 2026 | |
| m*e*j*w*n*i*e.com | F | Jul 18, 2026 | |
| k*n*y*k*u*i*l*.com | F | Jul 18, 2026 | |
| d*m*s*e*y.com | F | Jul 18, 2026 | |
| d*c*s*r*e.com (WP 7.0.2) | D | Jul 18, 2026 | |
| m*l*e*s*a*d.c*.uk | D | Jul 18, 2026 | |
| k*l*a*r*a*t*.com | D | Jul 18, 2026 | |
| g*a*e*a*a*.org (WP 6.9.5) | F | Jul 18, 2026 | |
| s*u*h*c*.com | F | Jul 17, 2026 | |
| b*a*s*n*a*.com (WP 7.0.2) | F | Jul 17, 2026 | |
| e*t*o*e*.com (WP 5.8.13) | F | Jul 17, 2026 | |
| m*m*e*s*c*l*b*a*t*n*t*t*t*.org | F | Jul 17, 2026 | |
| s*u*v*d*k*c*.com | F | Jul 17, 2026 | |
| s*n*o*e*t*.com (WP 6.9.4) | F | Jul 17, 2026 | |
| m*n*n*m*x*a*l*y.com (WP 7.0.1) | F | Jul 17, 2026 | |
| d*w*w*n*e*a*p*r*.com (WP 6.7.1) | A | Jul 17, 2026 | |
| d*w*w*n*e*a*p*.com (WP 6.7.1) | A | Jul 17, 2026 | |
| d*w*w*n*e*a*p*a*u.com (WP 6.7.1) | A | Jul 17, 2026 | |
| d*w*w*n*e*a*p*6*.com (WP 6.7.1) | A | Jul 17, 2026 | |
| d*w*w*n*e*a*p*.com (WP 6.7.1) | A | Jul 17, 2026 | |
| k*r*l*n*p*i*k*v*.com (WP 7.0.1) | F | Jul 17, 2026 | |
| d*t*n*i*a*i*c*.com | F | Jul 17, 2026 | |
| b*a*s*a*j*w*l*r*.com | D | Jul 17, 2026 | |
| a*p*u*i*a.live (WP 6.7.1) | A | Jul 17, 2026 | |
| t*d*a.org (WP 7.0.1) | F | Jul 17, 2026 | |
| k*n*v*s.com (WP 7.0.1) | F | Jul 17, 2026 | |
| h*a*k*r.com | F | Jul 17, 2026 | |
| s*l*e*i*o*e*s.com (WP 7.0.1) | F | Jul 16, 2026 | |
| m*k*t*b*c*o*i*t*r*.c*.uk (WP 7.0.1) | F | Jul 16, 2026 | |
| r*t*r*-*a*n*.org (WP 6.4.8) | F | Jul 16, 2026 | |
| c*m*a*g*4*q*a*i*y.info (WP 6.7.1) | A | Jul 16, 2026 | |
| a*d*b*r*h.com | B | Jul 16, 2026 | |
| s*g*t*e*.com (WP 6.9.1) | F | Jul 16, 2026 | |
| e*e*y*h*n*e*s*f*e*d.com | F | Jul 16, 2026 | |
| e*e*y*t*g*p*r*n*i*g.com (WP 6.6.5) | D | Jul 16, 2026 | |
| m*y*0.com | F | Jul 16, 2026 | |
| e*g*l*o*i*o*l*n*o*d.com (WP 6.8.1) | F | Jul 15, 2026 | |
| a*d*o*c*n*.com | F | Jul 15, 2026 | |
| v*s*7*-*o*i*m*s*k.com (WP 6.5.2) | F | Jul 15, 2026 | |
| p*n*a*o*i*.live (WP 6.7.1) | A | Jul 15, 2026 | |
| s*o*o*9*s*k.baby (WP 6.7.1) | A | Jul 15, 2026 | |
| v*b*a*o.com | F | Jul 15, 2026 | |
| a*p*l*t*e*r*8*.info (WP 6.7.1) | A | Jul 15, 2026 | |
| a*p*a*s*e*.buzz (WP 6.7.1) | A | Jul 15, 2026 | |
| d*n*e*t*a*l*n*.com (WP 6.9.4) | F | Jul 15, 2026 | |
| a*p*u*i*a.store (WP 6.7.1) | A | Jul 15, 2026 | |
| r*d*l*r.com (WP 6.9.4) | F | Jul 15, 2026 | |
| a*p*i*t*n*.top (WP 6.7.1) | A | Jul 15, 2026 | |
| p*d*o*i*.live (WP 6.7.1) | A | Jul 15, 2026 | |
| a*p*k*.top (WP 6.7.1) | A | Jul 14, 2026 | |
| s*c*h*t*g*a*h*b*l*i*m.com | F | Jul 14, 2026 | |
| m*s*p*s.com | F | Jul 14, 2026 | |
| a*c*t*a*n*n*.com | F | Jul 14, 2026 | |
| j*s*b*b*j*s*.com (WP 7.0.1) | F | Jul 14, 2026 | |
| e*s*n*i*l*c*i*e.com | F | Jul 14, 2026 | |
| m*s*-*a*a*.com | F | Jul 13, 2026 | |
| a*e*n*p*p*i*e*.com | F | Jul 13, 2026 | |
| t*l*o*g*a*u*a.com (WP 7.0.1) | F | Jul 13, 2026 | |
| t*x*s*e*s*h*r*p*.com | D | Jul 13, 2026 | |
| t*x*s*t*l*.com | F | Jul 13, 2026 | |
| c*r*e*f*n*r*e.com | F | Jul 13, 2026 | |
| a*a*a*a*a*i*e.com (WP 7.0.1) | F | Jul 13, 2026 | |
| t*u*o*f*e*c*f*a*o*s.com | F | Jul 13, 2026 | |
| j*u*d*.com (WP 6.8.5) | F | Jul 12, 2026 | |
| t*t*l*y*e*r*c*.com | F | Jul 12, 2026 | |
| s*i*l*g*i*l.com (WP 7.0.1) | F | Jul 12, 2026 | |
| c*i*n*w*.com | F | Jul 12, 2026 | |
| n*o*n*i*n.org (WP 7.0.1) | F | Jul 12, 2026 | |
| r*n*y*o*k.com (WP 7.0) | C | Jul 12, 2026 | |
| r*m*n*h*.com (WP 6.9) | F | Jul 12, 2026 | |
| l*n*a*a*r*j*c*.com (WP 5.4.19) | F | Jul 12, 2026 | |
| a*u*o*o*.com (WP 6.9.4) | F | Jul 12, 2026 | |
| w*l*s*a*l*o*s.com | F | Jul 11, 2026 | |
| w*w*f*i*e*o*s*t*p.com (WP 6.9.4) | F | Jul 11, 2026 | |
| s*t*s*o*e*n*b*t.com (WP 6.0.12) | F | Jul 11, 2026 | |
| e*u*u*n*i*e*v.com (WP 7.0.1) | F | Jul 11, 2026 | |
| e*t*e*r*n*u*m*g*z*n*r*c.com (WP 7.0.1) | F | Jul 11, 2026 | |
| w*r*s*u*e*o*k*r.com (WP 6.9.4) | F | Jul 11, 2026 |