Hi
I have followed the instructions step by step and I am getting multiple AMP errors in Google search console. Just to be clear these errors have only come about since installing the theme.
CSS syntax error in tag ‘style amp-custom’. = 18 error
An AMP component ‘script’ tag is present, but unused. = 8 errors
Referenced AMP URL is not an AMP = 1 error
The tag ‘noscript enclosure for boilerplate’ appears more than once in the document. = 128 errors
Only amp-boilerplate and amp-custom ‘style’ tags are allowed, and only in the document head. = 128 errors
Any support would be appreciated
anyone?
Hi,
Those look like the same errors mentioned here – https://wordpress.org/support/topic/amp-paired-two-errors/ – http://prntscr.com/mzeerr
The first error seems to be a script added by woocommerce, the other mentions that an AMP tag appears more than once. The first thing to do would be to deactivate plugins and keep testing to see if they still appear as errors.
Thanks
Simion this error is due to WPBakery Page Builder…
who uses js composer displays it…
you need to adjust js composer or the mobile theme to solve…
Thanks!
I don’t use WPBakery page builder though
Just been doing some more testing and the AMP error panel is saying the following is causing the issues
tagDiv Composer
tagDiv Cloud Library
Inline Related Posts
Jetpack by WordPress.com
Advanced Ads Pro
Akismet Anti-Spam
Advanced Ads
GDPR Cookie Consent
Advanced Ads – Slider
Advanced Ads – Responsive Ads
Advanced Ads – PopUp and Layer Ads
Google Analytics Dashboard for WP (GADWP)
WooCommerce
Let’s Review
Advanced Ads – Sticky Ads
Amazon Affiliate for WordPress
Advanced Ads – Ad Tracking
Theme – Newspaper
Just to be CLEAR, Once again. The errors have only come about since installing the TD mobile plugin and using the AMP integration. I have had a AMP plugin working fine before
@activeJR I also have the woocommerce plugin active, that script is loading for me as well. From what I can find the AMP plugin should remove it automatically and make the AMP page valid, seems it does not remove it. I will add this as well for investigation.
@Bintmusic That is also investigated.
Thank you for the feedback, I have reverted to the previous AMP method. Keep me informed when you have a fix as the TAGDiv looks cleaner
