First, please read the AMP Project’s frequently asked questions.
The official AMP plugin is free to use and always will be. Any extensions that our team develops are also free.
How does the plugin work?
The plugin converts your existing content to AMP valid content where possible. It inserts boilerplate AMP code into your sites header and provides you with development tools to ensure AMP validity is maintained.
Why are there different modes, and what do they do?
The different modes provide you with flexibility to choose how you prefer to implement AMP, with options to utilize your existing WordPress theme or to enable AMP only on particular post types or templates. You can see a summary of the different modes below:
– Standard: This mode ensures you are adopting an AMP first approach. Your website is AMP by default and there is no /?amp at the end of your URLs. Standard mode works best for websites using an AMP compatible theme, which while also using AMP compatible plugins and content.
– Transitional: This mode ensures you have AMP URLs running alongside your regular (non AMP) URLs. This mode should be selected if you are using an AMP compatible theme but are not ready for a 100% AMP website (via AMP standard).
– Reader Mode: This mode works best if you are using a theme which is not AMP compatible. Users can make use of AMP valid templates to serve individual pages and posts which run alongside your regular non AMP website. Non-singular templates like your blog index page, category page, and author page are not available in this mode. Your non-AMP URLs are not affected. If using reader mode be sure to checkout the “Classic Templates” page.
You can find out more about the different modes available on the “Serving Strategies” page.
How can I view my AMP content?
To view the AMP version of any of your pages and posts use any of the methods below:
– Use the AMP validator Chrome extension: Install the AMP validator browser extension and easily identify any AMP URLs or non AMP URLs which have an AMP version available.
– Use the plugin’s toolbar menu item: If you have the toolbar active (Users > Your Profile > Toolbar) you can click on the “View AMP version” link.
– Appending to the URL: append any post or page url with a /?amp at the end, as long as there is an AMP version available. This can be seen by looking for an link[rel=amphtml] element in the page as well.
My website isn’t working as normal when I check the AMP version. What can I do?
For plugins, themes or features which are not compatible you have options:
– Contact the developer: In many cases plugins can be easily modified for AMP compatibility using amp-bind or creating fallbacks.
– Look for an AMP compatible alternative: More and more plugins are becoming AMP compatible. Find some on our ecosystem page. Look for a compatible alternative which offers the same functionality.
– Use an AMP Component: AMP components can be used in place of plugins.
I’m using AMP in transitional or reader more, so I have 2 versions for some of my content. Which version will visitors land on?
It depends on where your traffic is coming from. From a mobile search will most likely be directed to your AMP URLs. A future version of the plugin may add the ability to automatically redirect mobile visitors to the AMP version.
If you’re using “Standard” mode AMP (formerly “Native”) or “Transitional” mode AMP (formerly “Paired”), this will generally apply any changes you make in the Customizer. When using Legacy Templating, in your Customizer’s “AMP” panel, you can edit the “Header Text Color,” “Header Background & Link Color,” and “Color Scheme.”
For information about handling of shortcodes, check out the page Native WordPress Embed And Shortcode Support.
Many plugins are adding AMP support already. If you handling analytics yourself, please see the page about Analytics.
The best place to start is to open a new discussion in the plugin’s support forum with details on what the specific validation error is.
This could happen if the AMP plugin has not been activated. It could also happen because there are AMP validation errors, which causes the redirect to prevent invalid AMP from being served. Check these two possibilities to determine the culprit.
This is likely to be caused by not having a featured image added to your post. If you don’t have a featured image to be added we recommend creating a generic image which can be used with each post lacking one.
That will make your post appear more attractive on Google itself without requiring you to find a new, unique image. Featured images are currently necessary for Google to index your AMP pages, so if you have one to include in every post, that will not only resolve this issue, but it will also help with SEO!
This may be caused by another plugin interfering with the AMP rendering of your posts. If you’ve installed a few new plugins, try deactivating them one at a time to see if that makes a difference. Certain settings can interfere with the loading of the page, so once you narrow it down, try adjusting the settings and extensions as well on other plugins.
You can remove default schema markup like this:
remove_action( 'amp_post_template_head', 'amp_post_template_add_schemaorg_metadata' );
All looks great, how can I contribute to the plugin?
Check out the AMP plugin’s help forums here. 🙂 You might find your question has already been answered, or you can post a new one.