Viewing 13 replies - 1 through 13 (of 13 total)
  • I’m getting this error too. What happened? I haven’t touched my FAQ page for months.

    Thread Starter sagarchaudhuri

    (@sagarchaudhuri)

    Same here. I am getting this error in all my post pages!

    +1 Same error for pages with Yoast FAQ Schema block.

    Same issue here..

    Plugin Support devnihil

    (@devnihil)

    Thank you for bringing this issue to our attention!We apologize?for the trouble you are currently experiencing with our plugin. Luckily, a so-called “bug report” (a description of the issue, so we can fix it) is filed already.

    What’s next? Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority level. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate of when they’ll start working on your report. If you have any further information that may affect the prioritization or help our development team solve this bug, please feel invited to reply to this forum topic.

    Thread Starter sagarchaudhuri

    (@sagarchaudhuri)

    Appreciate the quick response. However, it seems that several other users have been impacted as well (I have already seen their tickets). Though I am not sure, but it might start impacting our searching rankings and hence our businesses as well till the bug gets fixed. Thanks for your understanding.

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    We understand your concern, @sagarchaudhuri. We can confirm that it won’t affect anything negatively to the search engine’s ranking.

    That said, our development teams are already working on this and we’re expecting a patch release very soon. Once the next release is available, please update the plugin to the latest version and that shall fix the issue for everyone.

    Thanks for your continued patience!

    Thread Starter sagarchaudhuri

    (@sagarchaudhuri)

    In all likelihood, this bug was introduced in the last update of the plugin. Since the Google bot doesn’t crawl all pages everyday, the issue surfaced with a lag. So rolling back the last update might be a quick fix. Please consider. Thanks.

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    We have already released Yoast SEO v15.9.1. We recommend you please update the plugin to the latest version to have the relevant fix in place.

    I have updated the Yoast plugin on our website and the problem still exists in Google Search Console. I also turned off our Cloudflare cache just in case that was an issue. Still same problem. This is for our FAQ page.

    Thread Starter sagarchaudhuri

    (@sagarchaudhuri)

    Same here. I continue to get the same error even after updating to 15.9.1

    Please check https://www.hifives.in/key-trends-in-hr-for-2021-and-beyond/

    on Google Rich Results Test

    Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    @sagarchaudhuri We have tested the relevant URL on our end by using the Google Structured Data Testing Tool and we’re no longer seeing an error at all. In this case, can you please confirm where exactly you’re seeing the missing field mainEntity error still on your end?

    We look forward to hearing from you.

    Plugin Support devnihil

    (@devnihil)

    We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Missing field “mainEntity” Error in Google Search Console’ is closed to new replies.