XooCode(){

OwnershipInfo

OwnershipInfo is a time-scoped ownership record: who owned what, when, and from whom they acquired it. It attaches to a Person's or Organization's owns property to publish provenance — especially useful for art, collectibles, vehicles, trademarks, and any IP where chain-of-custody matters.

Full example of schema.org/OwnershipInfo json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional
schema.org/OwnershipInfo
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Adelaide Voss",
  "owns": {
    "@type": "OwnershipInfo",
    "ownedFrom": "2019-05-14",
    "typeOfGood": {
      "@type": "Car",
      "name": "1967 Volvo 122S Amazon",
      "vehicleIdentificationNumber": "122-67-0001"
    },
    "acquiredFrom": {
      "@type": "Person",
      "name": "Roman Halliwell"
    }
  }
}
</script>

Direct properties (4)

  • typeOfGood: the Product or Service the record describes.
  • acquiredFrom: the Person or Organization that transferred ownership.
  • ownedFrom: DateTime when the owner acquired the good.
  • ownedThrough: DateTime when ownership ended (omit for current ownership).

Used most often by galleries, auction houses, car-history sites (CarFax-style provenance), and trademark registries that publish ownership chains as structured data.

Minimal valid version

The smallest markup that still produces a valid OwnershipInfo entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/OwnershipInfo (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "OwnershipInfo",
  "ownedFrom": "2019-05-14",
  "typeOfGood": { "@type": "Car", "name": "1967 Volvo 122S Amazon" }
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

  • No dedicated rich result (feeds provenance / knowledge-panel data)
    Google docs

Common OwnershipInfo mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Current ownership with ownedThrough in the past

    Wrong
    ownedThrough set to the current date every day
    Right
    Omit ownedThrough while ownership is current

    Consumers treat past ownedThrough as sale history; your current-owner node is read as a former-owner record.

  2. 02

    acquiredFrom as free text

    Wrong
    "acquiredFrom": "an estate sale"
    Right
    Person or Organization node (Estate of X is a valid Organization)

    Structured acquiredFrom lets provenance consumers chain records; free text breaks the chain.

  3. 03

    typeOfGood as the wrong entity

    Wrong
    typeOfGood: a Vehicle schema with no VIN
    Right
    Specific Product / Vehicle with identifier (VIN / ISBN / GTIN)

    Without an identifier, two chain-of-custody records for the same good can't be merged.

Schema properties in this example

OwnershipInfoStructuredValuePersonCarownsownedFromownedThroughtypeOfGoodProductServicevehicleIdentificationNumberacquiredFromOrganization

About the example data

Provenance of Adelaide Voss's 1967 Volvo 122S — acquired in 2019 from Roman Halliwell, previously owned 2005–2019.

Comments

Loading comments...

Leave a comment