Accelerated Mobile Pages Errors on Google Webmasters

  • anish008

    (@anish008)


    9 years ago

    These are the AMP Errors that have come up in google webmaster after I installed & activated the AMP Plugin version 0.3.1 on my wordpress site.

    1. Invalid attribute value (http-equiv=refresh)
    2. Prohibited attribute (style, pagespeed_no_defer)
    3. Stylesheet CDATA attribute missing or invalid (boilerplate (noscript) – old variant)
    4. Unknown syntax error ()

    Can anybody tell me whether it is the incompatibility of the AMP Plugin 0.3.1 with WordPress Version 4.2.2 that is causing these issues or is it something else?

    https://www.ads-software.com/plugins/amp/

Viewing 8 replies - 1 through 8 (of 8 total)
  • neotrope

    (@neotrope)

    Likely good to update to the newest version of the plugin as first step.

    You should not have a refresh tag in a normal HTML/php page, or you’d need to find way to strip that out for AMP.

    The noscript code you have in your text might be outdated; updating it to modern format advisable.

    The plugin works perfectly fine with WordPress 4.2.x (WP and the AMP plugin are both made by the same company – Automattic — by the way).

    Having the same http-equiv=refresh issues on my articles too.

    Some link: https://www.isaumya.com/the-untold-truth-about-unlimited-hosting/amp/

    Tip – remove the http-equiv=refresh from your pages, not a good thing to have in a normal webpage. Or, you will need to create a filter to remove whatever is adding that to your posts, from your AMP template.

    There is normally no good reason to refresh a post page on a news site, which is main initial purpose of AMP.

    So, refreshing an ad unit perhaps? But kind of bad for a visitor while reading to suddenly have the page refresh. You might consder removing the refresh if you don’t “really” need it. Just a thought ??

    AMP doesn’t support it, is bottom line.

    Yah I got it it is getting added by nginx_pagespeed. I’ve already pused this to the Google team and they are working on it.

    Thanks for the reply.

    That’s super weird as not seeing that with the Apache mod_pagespeed … but you likely note if looking at the beta builds for MPS that they are really finally working to shore up NGINX support .. the number of fixes in the beta’s is pretty awesome for you GINXers ??

    Well I haven’t tested with apace or mod_pagespeed, but it is definately a thing for nginx_pagespeed. I’m on their latest stable build not beta.

    Besides if you visit CENTMIN MOD website https://centminmod.com/ and visit their source code, you will find the same HTTP-EQUIV="refresh" thing in every page of the site.

    They are also using nginx + nginx_pagespeeed.

    Ah, so that’s unique to that other code — not related to Google’s mod_pagespeed tech. Gotcha.

    Yeah, they are injecting javascript code into body and AMP explicitly doesn’t use java, so anything “injected” will cause error, which is this stuff

    so, presumably you’d need to add some filter to disable that for the AMP version

    <body><noscript><meta HTTP-EQUIV="refresh" content="0;url='https://site.ooo/?PageSpeed=noscript'" /><style><!--table,div,span,font,p{display:none} --></style><div style="display:block">Please click <a href="https://site.ooo/?PageSpeed=noscript">here</a> if you are not redirected within a few seconds.</div></noscript>

    I had the same problem with pagespeed for apache and I found this on pagespeed faq: https://modpagespeed.com/doc/faq#noscript-redirect

    This setup worked just fine. ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Accelerated Mobile Pages Errors on Google Webmasters’ is closed to new replies.