0

I am in the process of learning schema markup, and one of the Blog Posts I reviewed as a reference has the isPartOf property under the mainEntityOfPage property. The main Schema Markup type in this case is Article.

Can you help me understand what was the reasoning behind this decision?

Here's the code:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Hello World",
  "name": "Hello World",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "id": "https://example.com/hello-world#webpage",
    "url": "https://example.com/hello-world",
    "isPartOf": {
      "@type": "WebSite",
      "id": "https://example.com/#website",
      "url": "https://example.com",
      "name": "Example Website",
      "publishingPrinciples": "https://example.com/publishing-principles"
    }
  }
}
New contributor
Leandro is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

1 Answer 1

0

The article (Article) on "Hello World" is what the page (WebPage) is about (mainEntityOfPage), which is part of (isPartOf) a website (WebSite) called "Example Website".

In your example, "id" should be "@id". And you should find that the WebSite @id is the same on every page. That way, machines can determine that multiple pages that contain articles are part of the same website.

1
  • Thanks for the tips Tony. I am still a bit confused about these concepts but I will try to keep digging.
    – Leandro
    May 18 at 0:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.