“mainEntity” missing on FAQ page

Hi @coachview

We are sorry to hear that you’re having trouble. We looked at the relevant page and see a missing field in the Yoast SEO generated schema markup and as such, it’s throwing the error. To investigate the issue further, we’d like you to please perform a conflict check first to make sure that there’s nothing else is interfering with Yoast SEO. This will help us narrow down the exact cause and determine what the next steps are while saving you time.

The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

As we can imagine that you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process:?How to check for plugin conflicts.

Thanks for the reply. I’ve diabled all possible plugins in staging, without succes. I can’t disable all plugins and switch theme, because de Question/ Awnser block is part of my main theme (Salient)

Hi,

We can see this is a page: https://www.coachview.net/ondersteuning/veelgestelde-vragen/. Pages do not get a MainEntityofPage schema.

So marking it as a FAQPage and then Google tossing out those errors is expected behavior (as pages lack that schema type to begin with).

The way to resolve it is to use the Yoast FAQBlock. This guide explains more: https://yoast.com/how-to-build-an-faq-page/.

We understand that may not be possible because you are using an FAQ block from the theme.

In this case the workaround would be to force Yoast to output the mainEntityofPage. You would need to use our guide here: https://developer.yoast.com/features/schema/api/#add-or-remove-graph-pieces to develop on the Yoast plugin to output it.

Unfortunately, there’s a difference between the support we can offer and the level of programming needed to change (core) features of our plugin. Since we don’t want to take the risk that we break your website by suggesting incorrect or incomplete code, we cannot advise you on how to make such changes. And even though we cannot be of any assistance, you’re completely free to change anything in the plugin to better suit your needs.

We highly recommend checking out?our list of Yoast Partners here https://yoast.com/yoast-partners/ in case you are in need of development.

We will also keep this issue open for 1 week in case someone from the community can help. Perhaps a developer watching these forums can assist further. After which, we will close in order to keep the overview.

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

I am having the same issue on my FAQ page. I created the page with elementor pro and did not used the Yoast SEO content block. Is that the reason why I get the error in google search console?

• This reply was modified 4 years, 3 months ago by christianbrucki.

I am having the same issue starting on 3/8 I created the FAQ page with Yoast FAQ Block.

You made a change to the plugin 15.9.1
Release Date: March 4th, 2021
Removes mainEntityOfPage from our FAQ Schema block output and moves it to mainEntity on the WebPage output, fixing a Google parse issue with those FAQ blocks.

Now Search Console flags this as an error.

Please provide a fix for your fix. Thanks.