Viewing 12 replies - 16 through 27 (of 27 total)
  • I can see the same issue on the URL you provided, accessing your canonical (non AMP) URL results in an AMP page.
    https://www.zotezo.com/in/top/best-mass-gainer-in-india/

    The same issue isn’t occurring on some URLs, see below:
    https://www.zotezo.com/in/medicines/eternex-m-500-tablet/

    You’ll need to troubleshooting with your caching/optimisation plugins and with your Cloudflare configurations. I’ve been unable to recreate this from my side.

    Thread Starter zo

    (@zotezo)

    Hi jamesosborne,

    From checking today they seem to be loading fine from my side now.

    From here https://support.google.com/webmasters/thread/78070549 I have received this response.
    https://www.zotezo.com/in/medicines/clomipure-100mg-capsule/?amp
    Check for the following errors in the source code of the first webpage:
    Error: Attribute amp not allowed on element html at this point.
    From line 1, column 16; to line 2, column 97
    TYPE html>?<html lang=”en-US” amp=”” i-amphtml-layout=”” i-amphtml-no-boilerplate=”” transformed=”self;v=1″>
    Compare this with info from amp documentation:
    This tells everyone that this is an AMP file. <html amp> works too.
    Error: CSS: Parse Error.
    At line 5, column 22856
    ee}}{color:#000}.menu-toggle,b

    Error: CSS: webkit-font-smoothing: Property webkit-font-smoothing doesn’t exist.
    From line 5, column 30332; to line 5, column 30342
    smoothing:antialiased;moz-o

    Error: CSS: moz-osx-font-smoothing: Property moz-osx-font-smoothing doesn’t exist.
    From line 5, column 30367; to line 5, column 30375
    smoothing:grayscale;paddi

    Error: CSS: speak: none is not a speak value.
    From line 5, column 34615; to line 5, column 34618
    –]{speak:none;font-

    Error: CSS: speak: none is not a speak value.
    From line 5, column 37719; to line 5, column 37722
    n-]{speak:none;font-
    Error: Element div is missing one or more of the following attributes: role.
    From line 64, column 4; to line 64, column 265
    </div>? <div class=”ast-main-header-bar-alignment” data-amp-bind-class=”( astraAmpMenuExpanded ? ‘ast-main-h…t’ )” aria-expanded=”false” data-amp-bind-aria-expanded=”(astraAmpMenuExpanded ? ‘true’ : ‘false’)”><div c
    Error: Element meta not allowed as child of element ul in this context. (Suppressing further errors from this subtree.)
    From line 172, column 196; to line 172, column 234
    rumbList”><meta content=”3″ name=”numberOfItems”><meta
    Contexts in which element meta may be used:If the charset attribute is present, or if the element’s http-equiv attribute is in the Encoding declaration state: in a head element.If the http-equiv attribute is present but not in the Encoding declaration state: in a head element.If the http-equiv attribute is present but not in the Encoding declaration state: in a noscript element that is a child of a head element.If the name attribute is present: where metadata content is expected.If the itemprop attribute is present: where metadata content is expected.If the itemprop attribute is present: where phrasing content is expected.Content model for element ul:Zero or more li and script-supporting elements.

    Error: Element meta not allowed as child of element ul in this context. (Suppressing further errors from this subtree.)
    From line 172, column 235; to line 172, column 281
    rOfItems”><meta name=”itemListOrder” content=”Ascending”><li it
    Contexts in which element meta may be used:If the charset attribute is present, or if the element’s http-equiv attribute is in the Encoding declaration state: in a head element.If the http-equiv attribute is present but not in the Encoding declaration state: in a head element.If the http-equiv attribute is present but not in the Encoding declaration state: in a noscript element that is a child of a head element.If the name attribute is present: where metadata content is expected.If the itemprop attribute is present: where metadata content is expected.If the itemprop attribute is present: where phrasing content is expected.Content model for element ul:Zero or more li and script-supporting elements.
    Error: Attribute submit-error not allowed on element div at this point.
    From line 454, column 3092; to line 454, column 3109
    </div> <div submit-error>
    Error: Duplicate ID text-area-author-id.
    From line 468, column 9; to line 468, column 65

    Error: Duplicate ID text-area-author-id.
    From line 479, column 9; to line 479, column 66

    Error: Duplicate ID text-area-author-id.
    From line 502, column 9; to line 502, column 65

    Error: Duplicate ID text-area-author-id.
    From line 511, column 9; to line 511, column 66
    What is the issue? How can i Fix?
    Please help.
    Thanks

    The URL you provided below is a fully valid AMP URL.
    https://www.zotezo.com/in/medicines/clomipure-100mg-capsule/?amp

    From my side the only issue I see if when I try and visit the canonical (non AMP) version:
    https://www.zotezo.com/in/medicines/clomipure-100mg-capsule

    It renders as an AMP URL. As mentioned above please try troubleshooting with your caching & optimisation plugins, along with purging your Cloudflare CDN and checking it’s configurations. There’s nothing we can apply from our side that will correct this.

    Thread Starter zo

    (@zotezo)

    Hi,
    We have already disabled WP-rocket. Purge cloudflare CDN cache already but today again showing error in some pages.
    Kindly provide me a solution.
    We are loosing our Rank conineously.
    Thanks

    Thread Starter zo

    (@zotezo)

    Hi,
    This is our cache rule setup in cloudflare.
    Can you please suggest what’s wrong with the setup?
    https://dev1.zotezo.com/1.png
    https://dev1.zotezo.com/2.png
    Please suggest whats wrong.
    Thanks

    Thread Starter zo

    (@zotezo)

    Hi @jamesosborne,

    From my side the only issue I see if when I try and visit the canonical (non AMP) version:
    https://www.zotezo.com/in/medicines/clomipure-100mg-capsule

    It renders as an AMP URL.

    what steps do you follow to visit the canonical version that renders them with an amp URL?
    Neither CF nor RC caches ?amp version. So I’m clueless until I see an example!!!
    Thanks

    I can’t be sure, again you’ll need to check your third party plugins and configurations.
    As you’ll see here your canonical URL passes AMP validation, it’s an AMP URL.

    If you’re unable to troubleshoot without caching/opsonization plugins and with your CDN temporarily deactivate there’s not much else I can add to this.

    Thread Starter zo

    (@zotezo)

    Hi,

    If you’re unable to troubleshoot without caching/opsonization plugins and with your CDN temporarily deactivate there’s not much else I can add to this.

    Wp-rocket told that-
    WP Rocket is compatible with AMP pages just optimizations won’t run on AMP pages, unfortunately. This is because AMP code can’t be manipulated to ensure the AMP checks go correctly, so is very unlikely this is related to WP Rocket.
    Autooptimize told-Autoptimize is not active on AMP pages, so it has no impact what-so-ever.
    Cloudflare running from long time from the begining of time but issue happens from last 3 days.
    Thanks

    Thread Starter zo

    (@zotezo)

    Hi @jamesosborne and @westonruter
    Please help me to solve my recent AMP issue that is arises in GSC report.
    I need your urgent help to fix the issue.
    My Valid AMP pages are gradually decreasing and we are loosing our rank.
    Thanks

    • This reply was modified 4 years, 1 month ago by zo.

    It looks like your canonical URLs are loading fine now, in particular the one you highlighted previously:
    https://www.zotezo.com/in/medicines/clomipure-100mg-capsule/

    I suspect it was some type of redirection you had applied on your CDN or hosting. Did you make any change?

    Thread Starter zo

    (@zotezo)

    Hi,
    Today showing new url which is showing error-
    https://www.zotezo.com/in/medicines/tenlicret-20mg-tablet/?amp
    https://www.zotezo.com/connect/best-yoga-mats/?amp

    All are AMP validated.
    All caching Plugins has been stopped.
    Still issue not yet fixed.
    After updating to latest version from 20th the issue started.
    Can you check with your development team?
    Thanks

    • This reply was modified 4 years, 1 month ago by zo.
    • This reply was modified 4 years, 1 month ago by zo. Reason: Modified
    James Osborne

    (@jamesosborne)

    Both those URLs you provided are fully valid AMP URLs. What are the errors reported for those URLs in Search Console?

Viewing 12 replies - 16 through 27 (of 27 total)
  • The topic ‘Sudden Issue Referenced AMP URL is not an AMP’ is closed to new replies.