Title: AMP validation errors when using plugin
Last modified: February 15, 2019
---
# AMP validation errors when using plugin
* Resolved [wellmadedigital](https://wordpress.org/support/users/wellmadedigital/)
* (@wellmadedigital)
* [7 years, 3 months ago](https://wordpress.org/support/topic/amp-validation-errors-when-using-plugin/)
* When using the free version of this plugin, we get the following error on every
page except the home page when validating AMP:
* `The tag 'noscript enclosure for boilerplate' appears more than once in the document.`
* Has anyone else had this issue? It’s absolutely related to this plugin, because
when we deactivate it, the issue is solved. I’m not sure if it’s a configuration
error on our end since this plugin states support for the AMP for WP plugin,
which we’re also using.
* Thanks for the feedback!
* The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Famp-validation-errors-when-using-plugin%2F%3Foutput_format%3Dmd&locale=en_US)
to see the link]_
Viewing 3 replies - 1 through 3 (of 3 total)
* Plugin Author [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
* (@jsmoriss)
* [7 years, 3 months ago](https://wordpress.org/support/topic/amp-validation-errors-when-using-plugin/#post-11212063)
* WPSSO Core uses `` containers to add second-level Schema
markup.
* You can activate the WPSSO JSON add-on to add Schema markup as JSON-LD blocks
instead of noscript containers, or you can disable the use of noscript containers
by unchecking the SSO > General > Google > Meta Property Containers option.
* js.
* Plugin Author [JS Morisset](https://wordpress.org/support/users/jsmoriss/)
* (@jsmoriss)
* [7 years, 3 months ago](https://wordpress.org/support/topic/amp-validation-errors-when-using-plugin/#post-11212098)
* FYI – When an AMP plugin is active, and the current webpage is an AMP page, the
AMP_QUERY_VAR constant should be defined when viewing that page, and WPSSO Core
should not add `` containers to that webpage.
* I just double checked an AMP webpage created by the accelerated-mobile-pages
plugin, and there are no `` containers apart from the one
added by the accelerated-mobile-pages plugin itself. Are you sure that you’re
validating the AMP webpage url?
* Which AMP plugin are you using exactly? [https://wordpress.org/plugins/amp/](https://wordpress.org/plugins/amp/)
or [https://wordpress.org/plugins/accelerated-mobile-pages/](https://wordpress.org/plugins/accelerated-mobile-pages/)
or another AMP plugin?
* js.
* Thread Starter [wellmadedigital](https://wordpress.org/support/users/wellmadedigital/)
* (@wellmadedigital)
* [7 years, 3 months ago](https://wordpress.org/support/topic/amp-validation-errors-when-using-plugin/#post-11212172)
* Thanks for the rapid response, [@jsmoriss](https://wordpress.org/support/users/jsmoriss/)!
* Your first answer was spot on: it was the Meta Property containers option that
was causing the AMP validation error when working in conjunction with [https://wordpress.org/plugins/accelerated-mobile-pages/](https://wordpress.org/plugins/accelerated-mobile-pages/).
Deactivating it looks like it worked, and our AMP pages are returning as valid
again.
Viewing 3 replies - 1 through 3 (of 3 total)
The topic ‘AMP validation errors when using plugin’ is closed to new replies.
* 
* [WPSSO Core - Complete Schema Markup and Meta Tags](https://wordpress.org/plugins/wpsso/)
* [Frequently Asked Questions](https://wordpress.org/plugins/wpsso/#faq)
* [Support Threads](https://wordpress.org/support/plugin/wpsso/)
* [Active Topics](https://wordpress.org/support/plugin/wpsso/active/)
* [Unresolved Topics](https://wordpress.org/support/plugin/wpsso/unresolved/)
* [Reviews](https://wordpress.org/support/plugin/wpsso/reviews/)
* 3 replies
* 2 participants
* Last reply from: [wellmadedigital](https://wordpress.org/support/users/wellmadedigital/)
* Last activity: [7 years, 3 months ago](https://wordpress.org/support/topic/amp-validation-errors-when-using-plugin/#post-11212172)
* Status: resolved