: Which entity to choose as "isPartOf" of WebSite according to Schema.org? If think logically - hierarchy the following: WebSite → WebPage → mainEntity → Article So, I must state WebPage as
If think logically - hierarchy the following:
WebSite → WebPage → mainEntity → Article
So, I must state WebPage as isPartOf WebSite.
From the other side I saw many times that for example only Article (mainEntity) section stated as isPartOf WebSite.
I understand that main idea of WebPage is mainEntity (header, footer, navigation are always the same on all WebPage-s), but anyway the question is:
Should I state WebPage as part of Website or only mainEntity of WebPage? The purpose - better SEO.
More posts by @Martha676
1 Comments
Sorted by latest first Latest Oldest Best
I think these structures make the most sense (from least detailed to most detailed, and most likely also from most popular to least popular):
Article
WebPage mainEntity Article
WebSite hasPart WebPage mainEntity Article
The hasPart/isPartOf properties are rather broadly defined (a work that is "in some sense" part of another work), so one could even argue to use it in addition to mainEntity (i.e., WebPage hasPart/mainEntity Article), but in my opinion that’s not a perfect match and probably not necessary.
Which to choose? This mostly depends on what data you want to provide. If you don’t have relevant data about your website, there is probably no point in providing a WebSite item. If you provide a WebSite item (e.g. for Google’s Sitelinks Searchbox), it might make sense to define this item only on the homepage. If you want to state that your WebPage items are part of this WebSite, you could reference its URI instead of providing a separate WebSite item on each of your pages, repeating the same information every time.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.