AMP プロジェクトは、すべての人にとってウェブをより良くすることを目的としたオープンソースイニシアチブです。AMP は、配布プラットフォーム全体で一貫して高速で美しく、高性能のウェブエクスペリエンスを可能にします。 WordPress の公式 AMP プラグインは、堅牢な機能ときめ細かい発行者コントロールにより、WordPress サイト用の完全に統合された AMP パブリッシングをサポートします。


  • Compatibility Tool: to assist the development of AMP experiences by enabling AMP debugging with detailed information about validation errors that may exist, the markup/scripts causing them, and the specific components on site (e.g theme, plugin, core) responsible for that page content.
  • CSS Tree Shaking : サイトで定義した CSS ルールが、1AMP ページあたりに許容される CSS 容量制限を超えた場合の処理を支援します。
  • コアテーマ対応: 4つのデフォルトテーマ (Twenty Fifteen、Twenty Sixteen、Twenty Seventeen、Twenty Nineteen) に対して AMP の機能を完全に有効化します。
  • Gutenberg 対応: Gutenberg と完全に連携した AMP コンテンツ作成を可能にします。
  • AMP-first Experiences support: プラットフォームの柔軟性やコンテンツの忠実性を損なうこと無くサイト全体の AMP エクスペリエンスを可能にします。
  • Many Optimizations: A myriad of code, performance, and developer experience improvements: from customization flexibility, to better UI flows, internationalization, accessibility, etc.

The plugin can be configured to follow one of three different template modes: Native, Transitional, and Reader. When configured to operate in Reader and Transitional modes, a given post/page will have a canonical URL as well as a corresponding (paired) AMP URL. The AMP plugin is not serving as a mobile theme; it does not redirect mobile devices to the AMP version. Instead, the AMP version is served to mobile visitors when they find the content on platforms such as Twitter, Pinterest, Google Search, and others.

With the official AMP plugin for WordPress, the WordPress ecosystem is provided with the capabilities and tools it needs to build world-class AMP experiences without deviating from its standard, flexible, and well-known content creation workflow.

Getting Started

To learn more about the plugin and start leveraging its capabilities to power your AMP content creation 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.


  • Theme support enables you to reuse the active theme's templates and stylesheets; all WordPress features (menus, widgets, comments) are available in AMP.
  • Many themes can be served as AMP without any changes; the default experience is as if JavaScript is turned off in the browser since scripts are removed.
  • Reader mode templates are still available, but they are are limited. Not only do they differ from the active theme, any validation errors are silently sanitized.
  • Switch from Reader mode to Transitional or Native mode in AMP settings screen. You may need to disable the admin bar in AMP if your theme has a larger amount of CSS.
  • Make the entire site available in AMP or pick specific post types and templates; you can also opt-out on per-post basis.
  • Plugin checks for AMP validity and will indicate when either: no issues are found, new issues need moderation, or issues block AMP from being served.
  • The editor will surface validation issues during content authoring. The specific blocks with validation errors are indicated.
  • Validated URLs include the list of validation errors encountered, giving control over whether sanitization for a validation error is accepted or rejected.
  • Styles added by themes and plugins are automatically concatenated, minified, and tree-shaken to try to keep the total under 50KB of inline CSS.
  • A WP-CLI command is provided to check the URLs on a site for AMP validity. Results are available in the admin for inspection.


  1. フォルダーを /wp-content/plugins/ ディレクトリにアップロードします。
  2. WordPress の「プラグイン」メニューからプラグインを有効化します。
  3. If you currently use older versions of the plugin in Reader mode, it is strongly encouraged to migrate to Transitional or Native mode. Depending on your theme/plugins, some development work may be required.


broke blogs

I've tried this plugin on two different occasions. Each time the traffic went way down and eventually the sites broke. I had to deinstall it and the blogs went back up each time. One site has a custom theme and the other a paid one. Google recommends this and I'd like to use it, but it's just not working.

AMP – The original, the best!

When I work with WordPress, I like to use standard and maintainable plugin, so in the future, when I going to update, the error will be near to 0. So I choose AMP. The only little problem of this plugin is (was) connection with Google Tag Manager, but it is solved. Now you can record the users access, in AMP page and in non AMP page. Cool! The support is very very very wonderful. When you write into support plugin, you think: "maybe he/she doesn't respond", but isn't like this. Same day I had a code to solve this problem. Very cool! Nice plugin, nice support, nice code. Thank you.

AMP issues detected by Google search console

I activated the AMP using your guide. In the them panel–> mobile settings, I activated the Mobile + AMP use- Now, all my websites, all with newspaper have an issue with the search console of google. The issues in the google search console are: 1) The tag ‘noscript enclosure for boilerplate’ appears more than once in the document. 2) Only amp-boilerplate and amp-custom ‘style’ tags are allowed, and only in the document head. What is wrong? The performance are actually improved, but in 24h I received this issue. Can you help me? Thank you

Great Plug & Play AMP Plugin

I have used this on many different themes both for my own projects, as well as clients at the agency I work for. This plugin is great out of the box, but also highly extensible. We've had a really good experience with this overall.

Version 1.0.2 good but above version bad in the sense

Version 1.0.2 is good that's what I am using but one error (CSS code working good in non-amp but same not working fine in amp before "Version 1.0.2" was all fine but not others are fine, FIX IT) NEXT after "Version 1.0.2" there's one error it's creating 3-4 lines unnecessary spaces between "featured image and the top text of the post" which is very unattractive. FIX THIS MOST IMPORTANT. Others fine till now Waiting for fixing considering above issues in your next update I am still using the previous "Version 1.0.2" (which still contains CSS difference error for the amp and non-amp) Most important note for any Plugin Users Before updating any plugin make the backup (Updraft plus back up plugin is the best as a free tool) and restore (if plugin updated then restore only plugins, not a whole site to do faster recovery) if the problem exists. Or Use "WP rollback" wp plugin to roll back to the previous version of any updated plugin. that's what prevents me from breaking up my site. (Using this restoring from the backup plugin is not needed)

It broke my blog

I installed the plugin, activated it, reviewed the settings and emptied the cache so that it would take effect. I checked with the AMP Validator and hell yeah it was a valid AMP page. But my blog was broken. The header image became a background image. And scrolling down I could see the menu as a element (bullets and all) and the images of the posts that appear in the front page. Nothing else, no text, no widgets, nothing. Absolutely useless.


AMP はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献しています。


“AMP” は18ロケールに翻訳されています。 翻訳者のみなさん、翻訳へのご協力ありがとうございます。

“AMP” をあなたの言語に翻訳しましょう。

開発に興味がありますか ?

コードを閲覧するか、SVN リポジトリをチェックするか、開発ログRSS で購読してみてください。


For the plugin’s changelog, please see the Releases page on GitHub.