Title: Google AMP Errors
Last modified: February 14, 2022

---

# Google AMP Errors

 *  Resolved [daveydo](https://wordpress.org/support/users/daveydo/)
 * (@daveydo)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/google-amp-errors-5/)
 * On Feb 12 Google stumbled through my site and sent the following message:
    “`
   Errors can prevent your page or feature from appearing in Search results. The
   following errors were found on your site: Disallowed attribute or attribute value
   present in HTML tag. Only amp-boilerplate and amp-custom ‘style’ tags are allowed,
   and only in the document head. Custom JavaScript is not allowed. We recommend
   that you fix these issues when possible to enable the best experience and coverage
   in Google Search.`” Ran Pagespeed Insights and Defiants FastorSlow to recheck
   load results and compare to those prior to latest AMP update. Desktop was OK 
   remaining in the high 90’s however Mobile changed from low 90’s to mid 70’s range.
   Just sending you my experience as info not complaint. Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)

 *  [Fellyph Cintra](https://wordpress.org/support/users/fellyph/)
 * (@fellyph)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/google-amp-errors-5/#post-15362497)
 * Hi [@daveydo](https://wordpress.org/support/users/daveydo/),
 * Thanks for contacting us, could you share your UUID? So we can provide better
   feedback.
 *  Thread Starter [daveydo](https://wordpress.org/support/users/daveydo/)
 * (@daveydo)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/google-amp-errors-5/#post-15364778)
 * Thank you for your info. Hope I got it right. If not, let me know what’s missing.
   Not a tech type person.
    My UUID is: ampwp-209e0982-8eba-5a28-907b-d4045a461352
 * data sent a few minutes ago.
 *  [Fellyph Cintra](https://wordpress.org/support/users/fellyph/)
 * (@fellyph)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/google-amp-errors-5/#post-15368151)
 * Hi [@daveydo](https://wordpress.org/support/users/daveydo/),
 * Thanks for sharing your UUID, I have checked the plugins installed and the error
   can be caused by the W3 total cache if you have installed the CSS modification
   or lazy loading for images, you can disable those options to check if the issue
   still happens.
 *  Thread Starter [daveydo](https://wordpress.org/support/users/daveydo/)
 * (@daveydo)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/google-amp-errors-5/#post-15368291)
 * Thank you Fellyph for your assessment. I had a gut feeling it may be that plugin.
   The most important thing was that the AMP plugin was working the way you want
   before I change my caching strategy. Thanks again and make yourself a great day!
 *  [Fellyph Cintra](https://wordpress.org/support/users/fellyph/)
 * (@fellyph)
 * [4 years, 3 months ago](https://wordpress.org/support/topic/google-amp-errors-5/#post-15368388)
 * Hi [@daveydo](https://wordpress.org/support/users/daveydo/),
 * You can check [our documentation](https://amp-wp.org/documentation/getting-started/amp-site-setup/page-caching-with-amp-and-wordpress/)
   to have more background and also you can try out other cache plugin.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Google AMP Errors’ is closed to new replies.

 * ![](https://ps.w.org/amp/assets/icon.svg?rev=2527602)
 * [AMP](https://wordpress.org/plugins/amp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/amp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/amp/)
 * [Active Topics](https://wordpress.org/support/plugin/amp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/amp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/amp/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Fellyph Cintra](https://wordpress.org/support/users/fellyph/)
 * Last activity: [4 years, 3 months ago](https://wordpress.org/support/topic/google-amp-errors-5/#post-15368388)
 * Status: resolved