Understand Errors in Version 1.0.0

First of all, if you have not updated to version 1.0.0 of the AMP plugin please do so. This version added paired and native theme support where your AMP pages will have navigation, support for your homepage, tags, archives, pages, and posts, along with reading structured data correctly, related posts, and comments.

Understanding Errors

When you activate AMP in WordPress and choose between Paired or Native mode, you are going to see “errors” in your dashboard under AMP > Error Index.

These are NOT plugin errors. These are errors that the plugin found on your page that prevented them from being served as AMP pages and were sanitized to make the page AMP compliant.

For each error, it simply means that AMP blocked that script so that the page could be made AMP compliant.

So what to do with these errors?

First, use the Google validator to make sure that your post are being seen as AMP compliant. If they are, visually look at your AMP using using ?amp appended at the end of the URL. If you are satisfied with what you see, then you can ACCEPT these errors and you are done.

If you are not happy with what you see, it is important to remember that not all programming within your pages will be AMP compliant programming. For instance, if you have a newsletter signup embedded in a post via a shortcode, it will likely be sanitized to make the page AMP compliant. If this is unacceptable to you, then you will have to find other ways around that content or AMP is not for you.

If you are going to use AMP on WordPress, then you still have to think about programming your pages to be AMP compliant. This is not mandated by this plugin, this is mandated by core AMP.

Disclaimer: I am NOT a part of the AMP project or affiliated with this plugin.