• Resolved MC-land

    (@michaeliresource)


    Hi
    Ever since the update, search console have started picking up these errors and making the pages invalid for google search results.

    I cannot make any changes to this in the config, how can i fix this or will you address this issue in the next release?

    Thanks

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

Viewing 15 replies - 1 through 15 (of 29 total)
  • @michaeliresource If you are using a lazy loading widget or caching plugin can you temporarily deactivate and check to see if the problem exists? Along with the misplacement of some tags there are multiple css class references in your code, which is likely being inserted via another plugin.
    class="lazyload" class=""

    Thread Starter MC-land

    (@michaeliresource)

    Hi James,

    Thanks, I have followed your suggestion and ran another crawl, the same issue still persists.
    Can you take another look?

    Thanks

    @michaeliresource Looking at your site I don’t see any validation errors at present. Have you make any changes recently? If so it might take some time for the changes to reflect in search console. You can request a re-crawl here.

    Hello. I am getting the same errors from google. For all of my amp posts it is crawling.
    Talking about lazy loading for images and caching plugins, i am using those and we can’t deactivate those as they are highly important for our sites. Please tell how can we fix it or if it is some issue with amp plugin, kindly fix it as we need to resolve these errors asap. Thanks.

    @sandzee33987 If you open a new support ticket we can take a look, please share your site and details of the validation errors. Lazy loading is built into AMP, so the best option might be to disable those plugins on AMP endpoints, but provide the information in the support ticket.

    Hello,
    I was wondering if I could have some help too. I am getting these errors as well and now have almost 150 pages that do. What do I need to do to fix this?

    Thanks.
    Sarah

    @michaeliresource I am no longer seeing any validation errors on your AMP site. I will close this support ticket now.

    @runjumpscrap Please open a new ticket and provide additional information to allow us to troubleshoot (URL, Site Health info etc).

    Thread Starter MC-land

    (@michaeliresource)

    Thanks James, I noticed there has been a considerable drop in errors in my search console, theres still a few so will rerun the crawl to validate again.

    If still have errors, will just reopen this.

    Hello, as of about a week ago, I started getting the same error on vortexradar.com. I have lazy loading disabled on WP Fastest Cache and I don’t see any options to disable lazy loading in the AMP settings.

    Plugin Author Pascal Birchler

    (@swissspidy)

    @ariel-b Please open a separate ticket for your case and provide additional information to allow us to troubleshoot (specific URL with the problem, Site Health info etc). At first glance, I don’t see any invalid AMP pages on your website.

    ?????
    ??? ????? ??? ??? ???????
    Tag found outside the document head which is only allowed as a direct child of the document head.
    ??? amp
    ????? ??? ???????? ???? ????? ??? ?????
    ??? ??? ?? ???? ???????
    ???? ????????
    https://thaqefna.com

    @ramyabobali I don’t see any validation errors on the URL’s I checked. If you have any examples please open a separate support ticket, and share your Site Health Info from your WordPress dashboard.

    Since yesterday I also get the ‘Tag found outside the document head which is only allowed as a direct child of the document head’ warnings.
    My site health is fine.
    My blog is https://blog.computercreatief.nl.

    I think I solved it. It had something to do with settings in my optimizer plug-in from my hoster Siteground. I changed setting and now my amp-pages validate..

    • This reply was modified 5 years, 4 months ago by hafred.
    • This reply was modified 5 years, 4 months ago by hafred.

    @hafred Yes, sometimes caching/optimisation plugins can interfere. And nice work with your standard mode amp.

Viewing 15 replies - 1 through 15 (of 29 total)
  • The topic ‘Tag found outside the document head which is only allowed as a direct child of t’ is closed to new replies.