• Resolved wpvkp

    (@wpvkp)


    Man everything was working just fine but after the update my Google webmasters console is flooded with AMP errors.

    Error I am facing:

    Invalid CSS stylesheet:
    Line 160:10 s-serif; }
    Line 159:99 9ter_men;: 0; }
    Line 159:108 : 0; }

    AMP markup error:
    The mandatory tag ‘body’ is missing or incorrect.

    Website url: https://wpvkp.com
    AMP url: https://wpvkp.com/amp/

    Check yourself: https://search.google.com/test/amp

    Fix this problem man. Or it will be just so much difficult for me to individually remove amp pages from google.

    My theme: Genesis Framework. I know there is no error in my child theme, if there would be, then why I never received any errors/warning before.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Relax!
    Just grab a few of the pages that Google says have a problem and test them here:
    https://validator.ampproject.org/

    I just tested the URL you posted and it’s fine.

    Sometimes when Googly is crawling pages (especially amp ones) some kind of glitch occurs and it reports all sorts of errors that are false positives.

    If your pages are passing in the AMP Validator above then eventually Google will re-crawl and the errors will disappear.

    Indeed you have spurious and invalid css under this heading

    /* Style Modifer */

    For example where or how is this being defined with two semi-colons after those selectors :

    .amp-wp-tax-tag a, a, .amp-wp-author, .headerlogo a, [class*=icono-] { color: #26519e;; }
    .amp-wp-content blockquote{ border-color:#26519e;; }
    .nav_container, .comment-button-wrapper a { background:  #26519e;; }
    .nav_container a{ color:#fff }
    amp-user-notification { border-color:  #26519e;; }
    amp-user-notification button { background-color:  #26519e;; }

    There are several css selectors which appear to be wrong.

    • This reply was modified 7 years, 5 months ago by frenchomatic.
    Thread Starter wpvkp

    (@wpvkp)

    @lancecarr I think you are wrong here.

    Put this url over here and you will understand what I am saying.

    https://search.google.com/test/amp — visit here.

    https://wpvkp.com/amp/ — place this link over their.

    Thread Starter wpvkp

    (@wpvkp)

    But it’s fascinating that according to

    https://validator.ampproject.org/#url=https%3A%2F%2Fwpvkp.com%2Famp%2F

    there is no error on my site.

    Seems Google is messed up.

    Don’t know, but I need answer from this plugin’s author.

    Actually it is quite common which is why I have answered you here so you don’t go off trying to fix something that is not broken.

    The Google bot that crawls websites sometimes may hit a problem, it could be a server problem, a packet of info gets lost in transfer… it could be anything.

    The REAL test is whether the AMP page in question can pass the Validator test.

    If it does then the page is fully compliant per the requirements of the latest AMP project settings and it is Google’s problem, not yours.

    Thread Starter wpvkp

    (@wpvkp)

    @lancecarr — Thanks for the reply.

    But as far as I know AMP is a project maintained by Google right?

    So if their fancy AMP testing tool is showing error, doesn’t it means that there is some sort of problem with the code on my site.

    Main problem is that while I am surfing Google and if I find my site on search result pages it shows me this: Your page has AMP implementation errors.

    As for the data packet loss… that’s not something which is happening here. Because if that would be the case then why is google bots properly indexing my non amp pages without any error and showing problems in my amp.

    Well who knows!
    I just put that AMP url into both the AMP project validator AND the google one and both times got a pass!

    Thread Starter wpvkp

    (@wpvkp)

    Ok seems everything is working as of now.

    What I did.

    Cleared my CDN cache, Cleared cloudflare cache (I use page rules for full page cache), cleared nginx cache, cleared automize cache and done.

    Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    @wpvkp
    I guess I came here a bit late.

    I am glad to see that the issue has been fixed

    Thanks, @lancecarr for helping him troubleshoot.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Not a valid AMP page: CSS Errors’ is closed to new replies.