Missing field “mainEntity” on Question Pages

Could you let us know if you have added a FAQ block to that page? Adding the FAQ block adds the required FAQPage schema data, so not having that FAQ block may cause an error in Google.

To resolve the issue, we recommend adding a Yoast FAQ block. If that’s not an option at the moment, another alternative is to select the default, WebPage.

My website is related to Q&A topics.

So I setup the schema options as like this:

Page type as: QA page
Article type: default for questions.

Here is the screenshot: https://ibb.co/HpHtkTq

If I miss anything, Please let us know.

@trainingsadda

Checking the provided screenshot, it looks like you’ve configured it to be a QAPage from the default setting of WebPage.

Our default logic comes with a lot of build-in validation and error handling. These checks make sure that we don’t output invalid structured data in edge cases, or when we encounter conflicting options. They also help us to integrate all of the different pieces of schema which a page outputs.

By overriding the defaults, you may alter your schema markup in ways that don’t make sense, or which are incomplete.

So in order to resolve this, you’ll either need to add the missing markup (while you can set it as a QAPage in the Yoast SEO schema tab settings, you’ll still need to add the remaining markup) by adding custom code by way of our Schema API – https://developer.yoast.com/features/schema/api/

Or you can decide to set it back to the default of WebPage in the schema tab settings and it shouldn’t show that particular error message anymore. (but this might mean that it won’t be eligible for a Q&A rich result anymore).

You can test it out afterward on Google’s Rich Results Tool.

You can learn more about it here – https://yoast.com/help/selecting-content-types-in-schema-settings/

We hope this will help!

Thanks for your valuable suggestions.

But is this affect my SEO results?

Which one do I need to implement?

Hi @trainingsadda

This shouldn’t affect your SEO results directly, but if the schema markup has missing or incorrect data, then that would affect its eligibility to output as a rich result in the search results.

In this case, you can either keep the setting at ‘QAPage’ and add the appropriate markup via the Schema API (which you’ll have to add the custom code) or you can set it back to ‘WebPage’ and the schema data wouldn’t result in any more errors (however, it won’t have a chance to output as a ‘question’ rich result).

You can learn more about how to implement schema with the Yoast SEO plugin here – https://yoast.com/help/implementing-schema-with-yoast-seo/

Hello,

This thread has been marked as resolved due to lack of activity by original poster.

If you are not the original poster but have a similar issue, please open a new request.