Referenced AMP url is not an AMP.

  • Resolved nicoleao

    (@nicoleao)


    4 years, 2 months ago

    Hello,

    according to the Google Search Console I have this problem: Referenced AMP url is not an AMP. And they offer these examples:

    https://www.renmamaren.com/kerstmuziek-waarop-je-kunt-hardlopen-7-kerst-songs/amp/

    The people of the Yoast plugin told me this:

    We’ve looked at the example URLs and we found that something is redirecting these pages to the non-AMP version and the URL includes “?noamp=available”.

    After deactivating the Yoast plugin the problem is still there. So they adviced me to contact AMP support.

    Changing my theme didn’t help.
    Deactivating all my plugins resulted in a 404 error so that didn’t help either.

    I’ve used the AMP validator and did get a lot of errors I don’t understand:

    The mandatory attribute ‘?’ is missing in tag ‘html’.
    line 3, column 0

    Custom JavaScript is not allowed.
    line 51, column 2

    Custom JavaScript is not allowed.
    line 55, column 88

    The mandatory attribute ‘amp-custom’ is missing in tag ‘style amp-custom’.
    line 58, column 2

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-includes/css/dist/block-library/style.min.css?ver=5.5.1’.
    line 72, column 1

    The mandatory attribute ‘amp-custom’ is missing in tag ‘style amp-custom’.
    line 73, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-content/plugins/linkpizza-manager/public/css/pzz-public.css?ver=5.5.1’.
    line 76, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-includes/css/dashicons.min.css?ver=5.5.1’.
    line 77, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-content/themes/tweakme2/assets/css/bootstrap.min.css?ver=3.0’.
    line 79, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://use.fontawesome.com/releases/v5.5.0/css/all.css?ver=5.5.0’.
    line 80, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-content/themes/tweakme2/style.css?ver=2.2.2’.
    line 81, column 0

    The mandatory attribute ‘amp-custom’ is missing in tag ‘style amp-custom’.
    line 82, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-content/uploads/tweakme2/custom-css.css?ver=1599470218’.
    line 85, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-content/plugins/simple-social-icons/css/style.css?ver=3.0.2’.
    line 86, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-content/plugins/jetpack/_inc/social-logos/social-logos.min.css?ver=8.9’.
    line 87, column 0

    The attribute ‘href’ in tag ‘link rel=stylesheet for fonts’ is set to the invalid value ‘https://www.renmamaren.com/wp-content/plugins/jetpack/css/jetpack.css?ver=8.9’.
    line 88, column 0

    Custom JavaScript is not allowed.
    line 89, column 0

    Custom JavaScript is not allowed.
    line 89, column 125

    Custom JavaScript is not allowed.
    line 90, column 0

    Custom JavaScript is not allowed.
    line 95, column 0

    Custom JavaScript is not allowed.
    line 96, column 0

    Custom JavaScript is not allowed.
    line 101, column 0

    Custom JavaScript is not allowed.
    line 102, column 0

    Custom JavaScript is not allowed.
    line 107, column 0

    Custom JavaScript is not allowed.
    line 108, column 0

    Custom JavaScript is not allowed.
    line 109, column 0

    Custom JavaScript is not allowed.
    line 110, column 0

    Custom JavaScript is not allowed.
    line 115, column 0

    Custom JavaScript is not allowed.
    line 123, column 8

    Custom JavaScript is not allowed.
    line 131, column 8

    Custom JavaScript is not allowed.
    line 165, column 9

    Custom JavaScript is not allowed.
    line 174, column 0

    Custom JavaScript is not allowed.
    line 177, column 0

    Custom JavaScript is not allowed.
    line 178, column 0

    The mandatory attribute ‘amp-custom’ is missing in tag ‘style amp-custom’.
    line 185, column 3

    Custom JavaScript is not allowed.
    line 191, column 3

    Custom JavaScript is not allowed.
    line 196, column 112

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 211, column 45

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 256, column 9

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 260, column 3

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 262, column 3

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 264, column 3

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 266, column 3

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 268, column 3

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 270, column 3

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 272, column 3

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 274, column 3

    The mandatory attribute ‘action’ is missing in tag ‘form’.
    line 285, column 6

    The mandatory attribute ‘target’ is missing in tag ‘form’.
    line 285, column 6

    The tag ‘form’ requires including the ‘amp-form’ extension JavaScript.
    line 285, column 6

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 286, column 4

    Custom JavaScript is not allowed.
    line 288, column 5

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 314, column 257

    The mandatory attribute ‘target’ is missing in tag ‘form’.
    line 315, column 2

    The tag ‘form’ requires including the ‘amp-form’ extension JavaScript.
    line 315, column 2

    The attribute ‘action’ may not appear in tag ‘form’.
    line 322, column 12

    The tag ‘form’ requires including the ‘amp-form’ extension JavaScript.
    line 322, column 12

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 348, column 165

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 351, column 252

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 374, column 328

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 417, column 8

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 425, column 8

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 433, column 8

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 441, column 8

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 449, column 8

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 456, column 350

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 457, column 97

    The mandatory attribute ‘action-xhr’ is missing in tag ‘form’.
    line 478, column 1

    The tag ‘form’ requires including the ‘amp-form’ extension JavaScript.
    line 478, column 1

    Custom JavaScript is not allowed.
    line 489, column 0

    Custom JavaScript is not allowed.
    line 494, column 0

    The parent tag of tag ‘noscript enclosure for boilerplate’ is ‘a’, but it can only be ‘head’.
    line 499, column 183

    Custom JavaScript is not allowed.
    line 521, column 0

    The parent tag of tag ‘style amp-custom’ is ‘body’, but it can only be ‘head’.
    line 524, column 2161

    Custom JavaScript is not allowed.
    line 525, column 1

    The attribute ‘action’ may not appear in tag ‘form’.
    line 529, column 2

    The tag ‘form’ requires including the ‘amp-form’ extension JavaScript.
    line 529, column 2

    The tag ‘img’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-img’?
    line 542, column 3

    Custom JavaScript is not allowed.
    line 556, column 2

    Custom JavaScript is not allowed.
    line 557, column 0

    Custom JavaScript is not allowed.
    line 558, column 0

    Custom JavaScript is not allowed.
    line 559, column 0

    Custom JavaScript is not allowed.
    line 560, column 0

    Custom JavaScript is not allowed.
    line 561, column 0

    Custom JavaScript is not allowed.
    line 562, column 0

    Custom JavaScript is not allowed.
    line 563, column 0

    Custom JavaScript is not allowed.
    line 564, column 0

    Custom JavaScript is not allowed.
    line 565, column 0

    Custom JavaScript is not allowed.
    line 566, column 0

    Custom JavaScript is not allowed.
    line 571, column 0

    Custom JavaScript is not allowed.
    line 572, column 0

    Custom JavaScript is not allowed.
    line 601, column 0

    The tag ‘iframe’ may only appear as a descendant of tag ‘noscript’. Did you mean ‘amp-iframe’?
    line 605, column 289

    Custom JavaScript is not allowed.
    line 616, column 2

    Custom JavaScript is not allowed.
    line 700, column 2

    Custom JavaScript is not allowed.
    line 701, column 0

    The mandatory tag ‘head > style[amp-boilerplate]’ is missing or incorrect.
    line 713, column 0

    The mandatory tag ‘noscript > style[amp-boilerplate]’ is missing or incorrect.
    line 713, column 0

    The mandatory tag ‘amphtml engine v0.js script’ is missing or incorrect.
    line 713, column 0

    Could you please help? How do I fix this?

    • This topic was modified 4 years, 2 months ago by nicoleao.
    • This topic was modified 4 years, 2 months ago by nicoleao.
    • This topic was modified 4 years, 2 months ago by nicoleao.

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

Viewing 15 replies - 1 through 15 (of 29 total)

  • Thanks for reaching out. I don’t encounter any redirection on your site at present, on either AMP or non AMP.

    I did notice that both your canonical (non AMP) and your AMP URLs display internal links without the full URL:

    <link rel="amphtml" href="/kerstmuziek-waarop-je-kunt-hardlopen-7-kerst-songs/amp/">

    as opposed to

    <link rel="amphtml" href="https://www.renmamaren.com/kerstmuziek-waarop-je-kunt-hardlopen-7-kerst-songs/amp/">

    If you’d like to share your Site Health information here, or share privately we can try and determine the cause, possible a caching or optimization plugin.

    Thread Starter nicoleao

    (@nicoleao)

    Hi James,

    thank you very much for your response. I’ve used the link to share my information. I hope I did it correctly.

    Your help is most welcome.

    kind regards,
    Nicole

    Unfortunately we’ll need your full Site Health Information as per this screenshot (Tools > Site Health > info > Copy site info to clipboard).

    We can then determine the plugins you have active.

    Thread Starter nicoleao

    (@nicoleao)

    My apologies. I’ve tried again. I think this time I did it correctly.

    Thanks for sharing. It looks like you have a number of plugins active which may have features to shorten URLs. I’ve tested the Minify HTML plugin and I was able to reproduce the same issue with the following configuration:

    Can you try and toggle that setting if applied and check for the same issue, or let me know when you’ve make the switch and I’ll check? Note you have some additional plugin which may have similar features, including the below:

    • WP-Cache cache
    • WP-Optimize
    • Speed Booster Pack
    Thread Starter nicoleao

    (@nicoleao)

    I deactivated the Minify HTML plugin to get rid of the problem the easy way. Will that be enough?

    I’ve just checked your site and yes, that seems to have fixed it. You can perform another check on any URLs within Search Console.

    Let us know if you have any other queries. And be sure to share your plugin feedback, we’d love to hear your thoughts on the latest version.

    Thread Starter nicoleao

    (@nicoleao)

    Thank you very much for checking! I really appreciate the help.

    Thread Starter nicoleao

    (@nicoleao)

    Hi, unfortunately today I got the message the problem still persists.

    Here’s an example of an url with the problem:

    https://www.renmamaren.com/brittany-runs-a-marathon/amp/

    becomes

    https://www.renmamaren.com/brittany-runs-a-marathon/?noamp=available

    What should I do to fix this?

    • This reply was modified 4 years, 2 months ago by nicoleao.

    That seems like a separate issue, with the URLs which have an AMP version available displaying the correct AMP link.

    For the URL you referenced you can check that you have AMP enabled via the toggle when editing that specific post? You’ll see the setting below:

    Plugin Author Weston Ruter

    (@westonruter)

    When accessing an AMP URL results in redirecting to ?noamp=available, the cause is usually that there are validation errors for that AMP page which have been marked as having the invalid markup “kept”. When invalid markup is kept, the user is redirected to the non-AMP version because otherwise crawlers would report AMP validation errors, for example in Google Search Console.

    This redirection shouldn’t happen when you are logged-in.

    To diagnose what is going on, make sure that you have AMP Developer Tools enabled in your user profile settings. Then when viewing the AMP page, you should see the AMP menu item indicate the validation status. Click “Validate URL” from there and you can get the details.

    Thread Starter nicoleao

    (@nicoleao)

    Hi,

    I checked and Enable Amp was on. It was.
    I then enabled AMP Developer Tools and clicked on the AMP menu which was red with a little cross. Now it’s yellow with an exclamation point

    I went to the post and changed kept to removed and now that url seems to work.

    There are 296 pages with this error. Is there a way to fix the error without having to go through each and every post?

    And what can I do to prevent this kind of error? I never clicked ‘kept’ in the first place. How did this happen?

    Plugin Author Weston Ruter

    (@westonruter)

    There are 296 pages with this error. Is there a way to fix the error without having to go through each and every post?

    If the validation error is shared across all those URLs, if you mark it as Removed once, then it will be done for all other instances.

    Otherwise, something else you can do is reset your AMP validation state. If you have access to WP-CLI, you can run this command: wp amp validation reset --yes.

    Or else, what you can do is select all Validated URLs, then select the Forget bulk action, and then go to the Error Index and click the “Clear Empty” button.

    And what can I do to prevent this kind of error? I never clicked ‘kept’ in the first place. How did this happen?

    That’s a great question. I’m aware of this happening one other time, but we didn’t get down to to the cause. The default status for invalid markup should be removed and not kept. Since you have provided us with your Site Health info, we’ll try to see if we can reproduce the issue.

    Otherwise, we’d also want to know if after you reset the validation state if the new validation errors which are reported for invalid markup end up getting created in the “kept” state as opposed to “removed”.

    Plugin Author Weston Ruter

    (@westonruter)

    One more question: when you saw the validation errors being marked as “kept”, were they also shown as “unreviewed”? In other words, did they have the orange border on the left or not?

    Plugin Author Weston Ruter

    (@westonruter)

    Oh, and what were the validation errors specifically that were getting initially marked as kept? Were they for invalid scripts or something else?

Viewing 15 replies - 1 through 15 (of 29 total)
  • The topic ‘Referenced AMP url is not an AMP.’ is closed to new replies.