• Resolved nicoleao

    (@nicoleao)


    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, 6 months ago by nicoleao.
    • This topic was modified 4 years, 6 months ago by nicoleao.
    • This topic was modified 4 years, 6 months ago by nicoleao.

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

Viewing 14 replies - 16 through 29 (of 29 total)
  • Thread Starter nicoleao

    (@nicoleao)

    Unfortunately I don’t know what WP CLI is, so I don’t think I have access to it.
    I clicked on Validated urls on my dashboard. There were 6. I did the bulk ‘Forget thing’.

    I think the status was ‘reviewed’ but I’m not a 100% shure.

    I also clicked on the error index button and got this:

    Invalid script: partnerProductlink.js

    Details | Delete
    Removed
    JS 49 mins ago 0
    Invalid inline script

    Details | Delete
    Removed
    JS 49 mins ago 0
    Invalid script: partnerProductlink.js

    Details | Delete
    Removed
    JS 49 mins ago 0
    Invalid inline script

    Details | Delete
    Removed
    JS 49 mins ago 0
    Invalid script: partnerProductlink.js

    Details | Delete
    Removed
    JS 49 mins ago 0
    Invalid inline script

    Details | Delete
    Removed
    JS 49 mins ago 0
    Invalid attribute: border

    Details | Delete
    Removed
    HTML attribute 2 weeks ago 0
    Invalid inline script

    Details | Delete
    Kept
    <head> JS 2 weeks ago

    Does that mean anything?

    Plugin Author Weston Ruter

    (@westonruter)

    So you have no Validated URLs left now, correct?

    You can now click the “Clear Empty” button to remove all those errors from the Error Index.

    Then I’m wanting to know if they show up again, and if they show up as “Kept” instead of “Removed”.

    Thread Starter nicoleao

    (@nicoleao)

    You are right, there were no validated urls left. I clicked on Clear Empty and got this:

    Cleared 8 validation errors for invalid markup that no longer occur on the site.

    Dismiss this notice.
    With the new version of Speed Booster Pack, your settings are migrated to the plugin’s new options framework. Click here to review Speed Booster Pack’s options.

    Dismiss this notice.
    Yoast SEO Premium detected that you deleted a term (/amp_validation_error/443307e38cde04b09f480507a27388e1/). You can either:

    Redirect it to another URL
    Make it serve a 410 Content Deleted header
    Don’t know what to do? Read this post .

    Yoast SEO Premium detected that you deleted a term (/amp_validation_error/b2fbe0885fb66db6dd26b4ce078d8010/). You can either:

    Redirect it to another URL
    Make it serve a 410 Content Deleted header
    Don’t know what to do? Read this post .

    Yoast SEO Premium detected that you deleted a term (/amp_validation_error/fd6761f29bb0cf0d27dc3fe5145ac26e/). You can either:

    Redirect it to another URL
    Make it serve a 410 Content Deleted header
    Don’t know what to do? Read this post .

    Yoast SEO Premium detected that you deleted a term (/amp_validation_error/f5fb9489baac1663e808a13aa38b77f0/). You can either:

    Redirect it to another URL
    Make it serve a 410 Content Deleted header
    Don’t know what to do? Read this post .

    Yoast SEO Premium detected that you deleted a term (/amp_validation_error/53e2c1263d3904b94bcd830181d71bdb/). You can either:

    Redirect it to another URL
    Make it serve a 410 Content Deleted header
    Don’t know what to do? Read this post .

    Yoast SEO Premium detected that you deleted a term (/amp_validation_error/fc18ca33991b1f9924037d35239d280c/). You can either:

    Redirect it to another URL
    Make it serve a 410 Content Deleted header
    Don’t know what to do? Read this post .

    Yoast SEO Premium detected that you deleted a term (/amp_validation_error/0447935fef964eeb2cdbf7a5fbfd85ad/). You can either:

    Redirect it to another URL
    Make it serve a 410 Content Deleted header
    Don’t know what to do? Read this post .

    Yoast SEO Premium detected that you deleted a term (/amp_validation_error/4b6b12534ce8ba37ae7d8fbaa50ee885/). You can either:

    Redirect it to another URL
    Make it serve a 410 Content Deleted header
    Don’t know what to do? Read this post .

    Plugin Author Weston Ruter

    (@westonruter)

    Those Yoast notices are irrelevant. Yoast shouldn’t be issuing them for non-public taxonomies like this.

    So now, visit an AMP page and in the admin bar under the AMP menu item, tap “Validate URL”.

    When you do this, you should see a list of validation errors. Are they initially removed or kept? Are the checkboxes checked in the reviewed column or not?

    • This reply was modified 4 years, 5 months ago by Weston Ruter.
    Thread Starter nicoleao

    (@nicoleao)

    Okay, there are 5 validation errors. I followed the steps and the checkboxes are not checked and they are ‘removed’.

    Should I do something?

    Plugin Author Weston Ruter

    (@westonruter)

    Ok, if the AMP page works fine, you can mark those validation errors as reviewed by checking the checkboxes and hitting Update.

    I want to find out if they every change to being marked as Kept unexpectedly.

    Thread Starter nicoleao

    (@nicoleao)

    I checked the boxes and clicked on update, but then they appeared again unchecked. So I did it again, and then updated, and again they’re back.

    Is that supposed to happen?

    Plugin Author Weston Ruter

    (@westonruter)

    Sorry for the delay. Can you please share a screenshot of the validation errors that appeared again unchecked? If you can expand the validation errors to show the details as well as “Text” and “Source Stack” information that will be very helpful. For example:

    Thread Starter nicoleao

    (@nicoleao)

    Hi Weston,

    I got a bad cold and corona test, which was negatieve but I haven’t been able to answer and now I can’t remember how the validation errors were marked : (

    When I look at the Amp validation error index I see this:

    Error
    Markup Status Context
    Type
    Last Seen
    URLs
    Invalid attribute: border

    Details
    Removed
    HTML attribute 6 days ago 1
    Invalid attribute: border

    Details
    Removed
    HTML attribute 6 days ago 1
    Invalid attribute: border

    Details
    Removed
    HTML attribute 6 days ago 1
    Malformed URL https://www.runningskirts.com target= for attribute href

    Details
    Removed
    HTML attribute 6 days ago 1
    Invalid attribute: border

    Details
    Removed
    HTML attribute 6 days ago 1

    Plugin Author Weston Ruter

    (@westonruter)

    Glad you don’t have the virus. Hope you feel better soon.

    Instead of the validation error index, go to one of the validated URLs. When you click the Recheck button do new errors appear? Of you mark them as reviewed and then click Update, do new validation errors appear?

    Share screenshots as I did above. You can provide links to the images uploaded elsewhere.

    Thread Starter nicoleao

    (@nicoleao)

    I clicked the recheck button and there don’t appear any new errors.

    Here’s an url to a screenshot I took:

    https://1.bp.blogspot.com/-vpTuVeTVCNg/X2MNfeDW1cI/AAAAAAAAuGU/xzfhIYe-fqwxseTNoo66MswEqFgE0aIrQCLcBGAsYHQ/s1048/Screen%2BShot%2B2020-09-17%2Bat%2B09.16.17.png

    Plugin Author Weston Ruter

    (@westonruter)

    Ok, so what is the problem again?

    Thread Starter nicoleao

    (@nicoleao)

    Referenced AMP URL is not an AMP
    First detected: 8/31/20
    Status: Error
    112 affected pages
    Example: https://www.renmamaren.com/hardloper-esmar-van-langen-van-girls-run-the-world/amp/

    But I’ve started validation again, and right now it is saying ‘looking good’ so I’m hoping the problem has been solved after all.

    Plugin Author Weston Ruter

    (@westonruter)

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