• Resolved awill guru

    (@awillanurag)


    Hello Support Team,

    In Checklist–>Priority Section, I am getting this issue:

    “Make this Web Story easier to discover.

    Compatibility

    Your story contains errors that can affect eligibility to appear on Google.”

    I have disabled all the plugins except “Web Stories“, but this has not fixed the issue. See video(https://youtu.be/zJG9AKx4Auk)

    Note: Same issue I am getting on one of my different sites hosted on the same server. But this issue is not on the third site which is also hosted on the same server.

    NOW coming to next Issue:

    The second issue is that within 3-5 days I get a 404 error on each of my web stories links on all of my three sites, when I Deactivate the Web Stories Plugin and Activate it again the issue gets resolved. But I get the issue back after a few days (usually within 3-5 days). This has been happening for the last 2-3 months.

    Plz help me to fix the issues!

    Thanks

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

Viewing 12 replies - 1 through 12 (of 12 total)
  • Hello @awillanurag , thank you for posting your topic. Your story passed the AMP validation test and Rich Results test so there doesn’t seem to be any compatibility issue currently.

    Do you see this issue if you republish your story and clear any cache?

    If you could provide what information you can from your Site Health info privately through this form that would be great.

    Thread Starter awill guru

    (@awillanurag)

    I have submitted the form

    Plz see the next big Issue:

    The second issue is that within 3-5 days I get a 404 error on each of my web stories links on all of my three sites, when I Deactivate the Web Stories Plugin and Activate it again the issue gets resolved. But I get the issue back after a few days (usually within 3-5 days). This has been happening for the last 2-3 months.

    Plz help me to fix the issues!

    Thanks

    1. Your story at?https://basicknowledgehub.com/web-stories/a-new-anti-tracker-feature-has-arrived-for-apples/ fails because of Ezoic plugin and/or service. You can confirm this by removing that plugin and its service then see if the compatibility warning subsides.
    2. Regarding the 404 error, could you try to reset the permalink structure by going your WP?Settings > Permalinks?> then clicking save without changing anything?

    Next, set the Web Stories to Public and update the post once more.

    Thread Starter awill guru

    (@awillanurag)

    Plz confirm one thing:

    When I design the story there is no compatibility warning in the checklist, but when I publish the story I see the error.

    I had asked the ezoic team to bypass there service for story and I added some exclusion rules. It was working perfectly and I getting traffic form story. But, Nowadays there is no traffic and I came to know about this error. So I thought to inform concern team.

    Do this(compatibility) issue affecting the stories in search appearance? Because I can not disable the Ezoic services, I already told you that I disabled the ezoic plugin but the issue remains as it is.

    Plz suggest a way to fix, if it is affecting the traffic.

    Note: For 404 error, I will try your suggestions Once I get 404 error back.

    Thanks

    Plugin Author Pascal Birchler

    (@swissspidy)

    Do this(compatibility) issue affecting the stories in search appearance?

    Yes. As per the Google Search Central documentation, Web Stories should have no validation issues in order for them to be eligible for certain appearances on Google surfaces.

    Thread Starter awill guru

    (@awillanurag)

    I have tried a lot, contacted Ezoic team too, they are also not able to fix it. I have seen the debug section: https://ibb.co/g6R1M0L

    TAG_NOT_ALLOWED_TO_HAVE_SIBLINGS at 5:5740
    Tag 'amp-story' is not allowed to have any sibling tags ('body' should only have 1 child).
    4|
    5|/*# sourceURL=amp-custom.css */</style><link rel="alternate" type="application/rss+xml" title="Basicknowledgehub ? Feed" href="https://
    Plugin Author Pascal Birchler

    (@swissspidy)

    Do you perhaps have some caching plugin or something that might cause stale results?

    I still see a lots of code like <div class="ezmob-footer ezoic-floating-bottom ezo_ad"> and <!-- ezoic_pub_ad_placeholder-100-bottom_floating-728x90-100-nonexxxnonexxxxxxezmaxscaleval100 --> in your story, which is causing these errors. This must be coming from somewhere and I’d assume Ezoic are the ones who should be able to help you track this down and remove it from stories.

    Thread Starter awill guru

    (@awillanurag)

    I am continuously in touch with the ezoic team, I just forwarded this chat link to see the issue

    Thread Starter awill guru

    (@awillanurag)

    Sir, will you plz provide me the exact way to check the code in web stories?

    Plugin Author Pascal Birchler

    (@swissspidy)

    You can test your story by pasting your URL either at validator.amp.dev or in the AMP Test Tool, they’re almost the same. You can also open your story in the browser and use the “View Source” function in the browser to view the web page’s source code.

    Thread Starter awill guru

    (@awillanurag)

    Hi,

    finally the issue of compatibility is fixed!

    Plz check once by your side and close this converstation

    Thanks a lot

    This topic will be marked as resolved since your story passed the AMP validation test: https://search.google.com/test/amp/result?id=BINxju3pWRyjriMxcIGXNQ

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Compatibility and 404 Error’ is closed to new replies.