Poor support. Bugged schema feature.
-
Poor support. A bugged/defective schema feature has been on Yoast’s radar for over 5 months and they’ve done nothing. They even keep marking support posts about the bug as resolved despite it not being resolved.
The issue has been described by another user as:
“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?”
and
“In Google Search Console the error is:
Missing field ‘mainEntity’
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.”
- The topic ‘Poor support. Bugged schema feature.’ is closed to new replies.