This plugin adds support for the Accelerated Mobile Pages (AMP) Project, which is an an open source initiative that aims to provide mobile optimized content that can load instantly everywhere.
With the plugin active, all posts on your site will have dynamically generated AMP-compatible versions, accessible by appending
/amp/ to the end your post URLs. For example, if your post URL is
http://example.com/2016/01/01/amp-on/, you can access the AMP version at
http://example.com/2016/01/01/amp-on/amp/. If you do not have pretty permalinks enabled, you can do the same thing by appending
Note #1: that Pages and archives are not currently supported. Pages support is being worked on.
Note #2: this plugin only creates AMP content but does not automatically display it to your users when they visit from a mobile device. That is handled by AMP consumers such as Google Search. For more details, see the AMP Project FAQ.
Follow along with or contribute to the development of this plugin at https://github.com/Automattic/amp-wp
- Upload the folder to the
- Activate the plugin through the ‘Plugins’ menu in WordPress
- You may need to refresh your permalinks by going to
Settings > Permalinksand tapping the
- How do I customize the AMP output for my site?
You can tweak a few things like colours from the AMP Customizer. From the Dashboard, go to
Appearance > AMP.
For deeper level customizations, please see the readme at https://github.com/Automattic/amp-wp/blob/master/readme.md
- What about ads and shortcodes and such?
Check out https://github.com/Automattic/amp-wp/blob/master/readme.md#handling-media
- What about analytics?
Many plugins are adding AMP support already. If you handling analytics yourself, please see https://github.com/Automattic/amp-wp/blob/master/readme.md#analytics
- Google Webmaster Tools is reporting validation errors for my site. How do I fix them?
The best place to start is to open a new discussion in the support forum with details on what the specific validation error is.
- Why aren’t Pages supported yet
A wise green Yoda once said, “Patience you must have, my young padawan.” We’re working on it 🙂
Very dissapointing that Automatic appear not to be updating this plugin.
There is no adsense support so if you start using AMP you will need to edit the code yourself to reintroduce your Adsense code – very unsatisfactory.
Also, the plugin adds a link at the bottom of every page to wordpress.org – WHY?!
Come on Automatic get your act together
It was fine until a few days ago, it started to fail… causing my web to slow down. 4 days ago I left a message of support, and no answer. I’m going to deactivate it for the moment…
The plugin created a beautiful /amp version of all my blog posts, but unfortunately these pages did not trigger on mobile, and it slightly off-centered many elements site-wide, which can not be fixed.
It DID work just fine on another site I built which uses a different theme, so the theme might have something to do with it. Again, though it didn’t mess up the layout of this second site, it still does not trigger the amp versions of the pages (maybe this takes time?).
I use this plugin and Yoast’s Glue AMP Plugin. Automattic (this plugin creator) has been an amazing part of my web experience in the past.
3/22/07 update: Now just under 20% of my posts have critical issues. I think the fact that I added text (a phone number) in the Yoast glue plugin where the design header is may have caused the critical error issue.
Update after I initially post this: When I manual do the Google AMP test on a few randomly chosen on AMP URLS (for which Webmaster tools said they had errors just 1 hour ago), Google says each Valid AMP page.
Per Google Webmaster Tools yesterday, 60% of my AMP posts had critical issues. Prior to the update above, I expect this % to rise.
Each post has these 5 critical issues
Issue Severity Pages with issues
1 AMP markup missing or incorrect Critical
3 Prohibited or invalid use of HTML Tag Critical
4 Syntax error Critical
5 Invalid usage of AMP tags Critical
Worse yet, the Google search AMP tester froze when seeing if this page is AMP friendly.
I use a Genesis WP framework that I virtually haven’t altered, so if there is a site that this plugin should work on, it would be mine. However, it doesn’t.
I would be willing to pay for a premium version of this plugin that has support. This plugin’s support requests in the past 5 or so months haven’t been responded to.
I am grateful that the authors of this plugin took the time to make it. However, it concerns me that the WP plugin repository says this plugin (and Yoast’s Glue for AMP plugin) hasn’t been updated in 5 months or so.
To set google analytics statistics and amp ad code ( adsense) on the page, use this helper plugin – Head, Footer and Post Injections
Work with WP 4.7.3 and SSL support, PHP 7.1
Pass validation on AMP validator
Compatible with WP fastest cache
I installed all the necessary codes according to the instructions from Google and everything works, all the pages are tested in the validator, zero errors.
Many thanks to the authors of the plugin.
Never install the plug-in side, when checking other known like (AMP for WP – Accelerated Mobile Pages, AMP Supremacy, WP AMP – Accelerated Mobile Pages for WordPress, Better AMP – WordPress Complete AMP) got in the validator errors.
These errors are not eliminated by other plugins, they just pile up, the result of your pages disappear from the google.
Contributors & Developers
“AMP” is open source software. The following people have contributed to this plugin.Contributors
“AMP” has been translated into these 10 locales: French, Turkish, German, Brazilian Portuguese, Spanish, Italian, Dutch, Chinese (Taiwan), English (UK), English (Australia). Thank you to the translators for their contributions.
Interested in development?
- Fix: Prevent validation errors for
htmltag (h/t Maxime2 and everyone else that reported this error)
- Fix: Handle variable name conflict that was causing content_max_width to be ignored (h/t mimancillas)
- Fix: Prevent errors when nodes don’t have attributes (h/t stephenmax)
- Fix: Back-compat for 4.5 (add sanitize_hex_color function, h/t xotihcan)
- Fix: Handle gif featured images (h/t protocolil)
- Documentation updates (props troyxmccall)
- Fix: Don’t fire the_content for featured image output
- Fix: Don’t show comment link when disabled and no comments on post (h/t neotrope)
- Fix: strip
!importantfrom inline styles (h/t compointdesigner and enriccardonagmailcom)
- New template: spiffy, shiny, and has the fresh theme smell (props allancole and the Automattic Theme Team).
- Warning: The template update has potential breaking changes. Please see https://wordpress.org/support/topic/v0-4-whats-new-and-possible-breaking-changes/
- AMP Customizer: Pick your colours and make the template your own (props DrewAPicture and 10up)
- Fix: support for inline styles (props coreymckrill).
- Fix: no more fatal errors when tags not supported by post type (props david-binda)
- Fix: no more unnecessary
- Fix: sanitize children of removed nodes (like empty
<a>tags) (props Maxime2).
- Fix: no more broken YouTube URLs with multiple ?s.
- Fix: properly handle tel and sms schemes (h/t soundstrategies).
- Fix: remove amp endpoint on deactivate.
- New filter:
amp_pre_get_permalinkif you want a completely custom AMP permalink.
0.3.3 (Aug 18, 2016)
- Handle many more validation errors (props bcampeau and alleyinteractive).
- New filter:
- New template: Nav bar is now it’s own template part (props jdevalk).
- Better ratio for YouTube embeds.
- Fix: better timezone handling (props rinatkhaziev).
- Fix: better handling of non-int dimensions (like
- Fix: better handling of empty dimensions.
autoplayis a bool-like value.
- Fix: breakage when using the
query_stringhook (h/t mkuplens).
- Fix: don’t break really large Twitter IDs.
- Fix: don’t break Instagram shortcodes when using URLs with querystrings.
- Readme improvements (props nickjohnford, sotayamashita)
0.3.2 (Mar 4, 2016)
- Jetpack Stats support.
- Better version of Merriweather and use system fonts for sans-serif (props mattmiklic).
- Move font to stylesheet so it can be more easily overridden (props mattmiklic).
- Fix: Template loading issues on Windows. (Thanks to everyone who reported this, especially w33zy for pointing out the
- Fix: don’t run AMP on post comment feeds (props kraftbj).
- Fix: un-break pagination when using a static home page with multiple pages.
- Fix: force amp-iframe to use https to validate correctly (props mister-ben).
- Fix: validation for
- Fix: clipped images in galleries (thanks tobaco).
0.3.1 (Feb 24, 2016)
- Allow custom query var (props vaurdan).
- Fix AMP URLs for non-pretty permalinks (props rakuishi).
- Fix for password-protected posts.
- Fix dimension extraction for schema-less or relative image URLs.
- Better fallback for images with no dimensions.
- Validation fixes for
atags (props kraftbj).
- Updated AMP boilerplate.
ontags for elements (props Steven Evatt).
- Prefixed class names.
0.3 (Feb 18, 2016)
- Fetch dimensions for hotlinked images.
- Add amp-facebook support.
- Add some new actions and filters (e.g.
- Fix validation errors for [gallery] shortcodes.
- Fix issues with path validation on Windows.
- Fix issues with really squeezed layout.
- Breaking change:
style.cssno longer contains the ` tag. If you have a custom stylesheet, you need to update it to remove the tag.
- Breaking change:
single.phpno longer includes the AMP boilerplate styles. They are instead added via the
amp_post_template_headhook. If you have a custom template, please remove the boilerplate styles.
0.2 (Jan 28, 2016)
- Lots and lots and lots of compatibility and validation fixes
- Lots and lots and lots of improvements for customization
- Initial version