• Resolved juditho

    (@juditho)


    I am currently having AMP Disallowed attribute on my website https://myjesusandi.com I have checked on search console the error i saw is this <meta name=”twitter:label1″ value=”Written by”> can you tell me how to fix it?
    the amp errors are 4 they are as follows:
    1 <meta name=”twitter:label1″ value=”Written by”>
    2 <meta name=”twitter:data1″ value=”Judith”>
    3 <meta name=”twitter:label2″ value=”Est. reading time”>
    4 <meta name=”twitter:data2″ value=”2 minutes”>

    can you help me interpret and fix this AMP errors?

    The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thanks for getting in touch. From inspecting your site it looks like your using an alternate AMP plugin. If you reach out on the respective plugins support forum they should be able to assist.

    Thread Starter juditho

    (@juditho)

    Dear James, if I disable that AMP plugin will this error be fixed?

    The error is an AMP validation error. If you disable the AMP for WP plugin and don’t install any other AMP plugins you won’t have any AMP validation errors, you won’t however have any AMP content. You need to install an AMP plugin to benefit from AMP, and should you encounter any validation errors you can reach out to the developer of that plugin.

    If you happen to test out this AMP plugin you can follow the on boarding wizard, or checkout the website FAQs section to understand how the plugin works. Likewise if you reactivate your existing AMP plugin the developers should be able to help out.

    Thread Starter juditho

    (@juditho)

    Dear James, Thanks. two more questions.

    I have a Jetpack plugin, do I still need to install an AMP plugin?

    Secondly, If I install a different plugin from the one I had previously, will this error still be there? Please respond to enable me decide if I should go back to the previous plugin or install another AMP plugin.

    Regards.

    If you want to enabled AMP on your site you will need to use an AMP plugin. Most aspects of JetPack are AMP compatible.

    Secondly, If I install a different plugin from the one I had previously, will this error still be there? Please respond to enable me decide if I should go back to the previous plugin or install another AMP plugin.

    The errors you reported seem to be coming from another plugin, and they relate to code inserts that are not AMP compatible. I’m unsure how other AMP plugins work but with this plugin it highlights any validation errors and allows users to choose a course of action, it can remove such code or features from running on the AMP version of your site if you wish.

    The website documentation how more information on how validation works.

    Thread Starter juditho

    (@juditho)

    I have installed the Plugin. Can you confirm if I installed the right one?

    If yes, please assist me fix this.

    Regards.

    Yes, you’ve installed this AMP plugin, which we provide support for. I don’t see any validation errors when checking. Feel free to try out the different reader mode themes for a different appearance of your AMP URLs. Refer to the website for more information.

    Thread Starter juditho

    (@juditho)

    Dear Janes

    Thanks. Previously, I noticed my ads don’t display on the AMP version. Is there any reason why this is so?
    If yes, can do anything to change it?

    If you’re using AMP you’ll need to ensure you have AMP HTML ads on your AMP URLs. I can’t be sure of your previous setup although you can use the Site Kit plugin if using AdSense. Site Kit can ensure Auto ads work on your AMP and non AMP URLs alike.

    Alternatively you can use this Guide to implement ads on AMP URLs.

    Thread Starter juditho

    (@juditho)

    Thanks for the update. I am not using Adsense. I’ll prefer auto ads that way it works on both AMP and none AMP URL.

    Will site kit work for media.net ads?

    Thanks once again.

    Yes, it looks like media.net support AMP ads.

    Click here for a full list of vendors.

    Thread Starter juditho

    (@juditho)

    Thanks, this is officially closed. Case resolved.

    No problem, happy to help.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Disallowed attribute or attribute value present in HTML tag’ is closed to new replies.