#5789 - ProfilePage schema requires mainEntity property which is missing in Composr
-
By PDStig
- Added
- 1 view
| Identifier | #5789 |
|---|---|
| Issue type | Trivial issue (does not break functionality) |
| Title | ProfilePage schema requires mainEntity property which is missing in Composr |
| Status | Open |
| Tags |
Roadmap: v11 (custom) |
| Handling member | Deleted |
| Version | 10.0.48 beta |
| Addon | authors |
| Description | schema.org/ProfilePage requires a mainEntity, which is a Person or Organization. But this is missing in Composr.
ProfilePage is used in the Authors addon but might be used elsewhere. Search everywhere for its use and fix accordingly. We will need to add a new radio selection to choose between Person and Organization when adding or editing an author. We may need to fundamentally edit the authors addon / screen to include additional fields as defined by Person or Organization entities. As mainEntity is required, we must decide on the behavior of authors: a) Continue allowing the auto-creation of new authors when specifying one that does not exist; default to Person, and document this behavior. b) Forbid typing in an author that does not exist; it must be manually created by adding a new author so that we can explicitly define if it's a Person or Organization. |
| Steps to reproduce | |
| Additional information | See https://developers.google.com/search/docs/appearance/structured-data/profile-page#structured-data-type-definitions |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments