Schema markup examples by page type

How to combine multiple schema types on one page

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.example.com/#organization",
      "name": "Example Audio",
      "url": "https://www.example.com/",
      "logo": "https://www.example.com/logo.png"
    },
    {
      "@type": "WebPage",
      "@id": "https://www.example.com/headphones/#webpage",
      "url": "https://www.example.com/headphones/",
      "name": "Ultra Wireless Headphones",
      "mainEntity": { "@id": "https://www.example.com/headphones/#product" }
    },
    {
      "@type": "Product",
      "@id": "https://www.example.com/headphones/#product",
      "name": "Ultra Wireless Headphones",
      "image": "https://www.example.com/images/headphones.jpg",
      "brand": { "@id": "https://www.example.com/#organization" },
      "offers": {
        "@type": "Offer",
        "price": "199.00",
        "priceCurrency": "USD",
        "availability": "https://schema.org/InStock"
      }
    }
  ]
}

Rules that keep combined markup trustworthy

• Mark up only what a visitor can see on the page, with the same values.
• Describe each real thing once and reuse its @id instead of repeating it with slightly different details.
• Use the most specific type that is true (for example Dentist rather than LocalBusiness).
• Validate the finished page, not each block on its own.

What Google shows from these types

Only some types produce a Google search feature. Product, Event, JobPosting, LocalBusiness, Recipe, and others are listed in Google's Search Gallery. Others, such as WebPage, Service, or Place, have no rich result but still describe the page for search engines and AI assistants. Google has also retired some rich-result displays, such as FAQ results in May 2026. Those types are still valid schema.org markup, so stacks keep them. Each schema type page shows its current Google support status with a link to Google's documentation.