-
Notifications
You must be signed in to change notification settings - Fork 882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing field 'mainEntity' error when the Page type is selected as 'Profile Page' #20935
Comments
Please inform the customer of conversation # 1085224 when this conversation has been closed. |
Please inform the customer of conversation # 1084718 when this conversation has been closed. |
Please inform the customer of conversation # 1085028 when this conversation has been closed. |
Please inform the customer of conversation # 1085834 when this conversation has been closed. |
Please inform the customer of conversation # 1088580 when this conversation has been closed. |
Please inform the customer of conversation # 1086874 when this conversation has been closed. |
Please inform the customer of conversation # 1091622 when this conversation has been closed. |
Please inform the customer of conversation # 1096076 when this conversation has been closed. |
Please inform the customer of conversation # 1097895 when this conversation has been closed. |
This bug is fixed with this issue https://github.com/Yoast/plugins-automated-testing/issues/1362 and PR and this one.(#21127) The update is scheduled for 22.1 as of now. |
Is your feature request related to a problem? Please describe.
Missing field 'mainEntity' error appears on Google Rich Results testing tool and GSC when page type is selected as the 'Profile Page'
Describe the solution you'd like
It would be great to see Yoast SEO support the "ProfilePage" schema so the error gets resolved.
Why do you think this feature is something we should consider for the Yoast SEO plugins?
Google's new support for discussion forum and profile page schema markup
Additional context
The text was updated successfully, but these errors were encountered: