: Can 'mainEntityOfPage' point to another page? I have two pages: page1.html: WEBPAGE->MainEntity->ARTICLE { inside ARTICLE I have PRODUCT with short description } page2.html: WEBPAGE->MainEntity->PRODUCT
I have two pages:
page1.html:
WEBPAGE->MainEntity->ARTICLE {
inside ARTICLE I have PRODUCT with short description
}
page2.html:
WEBPAGE->MainEntity->PRODUCT {
"Full description of PRODUCT"
}
Can I declare mainEntityOfPage on page1.html which points to page2.html?
For example:
<article itemprop="mainEntity" itemscope itemtype="http://schema.org/Article">
<meta itemprop="mainEntityOfPage" content="Article page" itemscope itemType="https://schema.org/WebPage" itemid="http://example.com/page1.html"/>
<div itemscope itemtype="http://schema.org/Product">
<h2 itemprop="name"><a href="http://example.com/page2.html" itemprop="mainEntityOfPage">Product name</a></h2>
<p itemprop="description">Product short description</p>
</div>
</article>
More posts by @BetL925
1 Comments
Sorted by latest first Latest Oldest Best
Yes, as its definition says "Indicates a page […]".
If it were intended only for the current page, there would have been no point in expecting a URL as value, as a Boolean value would have sufficed.
In your example, it’s probably not necessary to define mainEntity and mainEntityOfPage for the Article (assuming that the markup is on the page example.com/page1.html), because these properties are defined to be inverse anyway. But it doesn’t harm either (and it could even help in cases where a consumer only supports one of these, without caring about the fact that they are defined to be inverse).
If the Article is about the Product, you may want to use the about property. Currently these two items are not related to each other in any way.
And you might want to use the url property in addition to the mainEntityOfPage property for the Product (itemprop="mainEntityOfPage url").
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.