When using the “ProfilePage”, we should also add what is the main entity of that profile page, for example the person described on the page.
After I select ProfilePage on Yoast page settings, I run the schema validator and see that Yoast doesn’t add any schema for describing a person (mainEntity). So, how can we “tell” search engines what is that profile page about without adding Person type schema as the main entity?
Thanks for reaching out about the ProfilePage schema type. Can you let me know what type of content you have marked as a Profile Page page type in the schema tab of the Yoast SEO meta box? Is it a page or an author custom post type?
I have the same error. I’ve created a page and set it as ProfilePage in the Yoast schema box, yet get the “mainentity” missing error in Google’s rich results test
Items with this issue are invalid. Invalid items are not eligible for Google Search’s rich results
Then it lists the URL of a page on my website that is identified by Yoast as having the “profile page” schema. It seems that the Yoast code is no longer current and needs an update to fix this.
Hi folks, we had the same trouble and were able to resolve it with a custom function. This function contains site-specific references, but can be adapted to work on your site.
/** * Update Yoast Profile Page schema markup to include mainEntity */
I too found the missing mainEntity in Google Search Console. It related to my “About Me” page, which I must have assumed at some point meant I should select Profile page in yoast schema.
I’ve now changed the page type back to default, but would like to know how we’re actually meant to deal with our “About” pages.
Adding additional code is probably a step too far for me.