Correct usage of mainEntityOfPage in Article type #3274
-
I write a blog using Ghost CMS they automatically generate json-id. I also use a stats system that tries to use that json-id to show detailed stats on material. The problem is that one of them is not interpreting the schema.org specification correctly. Help me understand who is wrong. The analytics developers say that the mainEntityOfPage should contain a link to the article itself in @id. The Ghost CMS developers believe that @id in mainEntityOfPage should point to the root page of the blog, not to the current article. Would be grateful for help |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Following the description of the property at schema.org/mainEntityOfPage, the associated background documentation, and json-ld example, the Ghost CMS developers are not correct. The mainEntityOfPage property of an Article/BlogPosting should contain the url of the page (preferred page if it appears on more than one) it is displayed upon. Having said that, reading your description, I do not think that the analytics developers have it quite correct either. In the example you describe there are two things (entities) the Article/BlogPosting and the WebPage it is displayed upon. Ideally they should be described separately with the mainEntityOfPage property of the Article linking to the WebPage - see the examples for BlogPosting. For completeness, in addition to reviewing the use of mainEntityOfPage to link an Article to the WebPage it is displayed upon, use of its inverse mainEntity should be looked at. mainEntity is a property of a CreativeWork (usually WebPage) linking to the main Thing (entity) that page describes - see example. |
Beta Was this translation helpful? Give feedback.
Following the description of the property at schema.org/mainEntityOfPage, the associated background documentation, and json-ld example, the Ghost CMS developers are not correct.
The mainEntityOfPage property of an Article/BlogPosting should contain the url of the page (preferred page if it appears on more than one) it is displayed upon.
Having said that, reading your description, I do not think that the analytics developers have it quite correct either.
In the example you describe there are two things (entities) the Article/BlogPosting and the WebPage it is displayed upon. Ideally they should be described separately with the mainEntityOfPage property of the Article linking to the WebPage …