parentOrganization

parentOrganization · Optional

Appears in

• Organization

What is it?

parentOrganization identifies the larger organization that the current entity is a part of. It is the inverse of subOrganization. When you mark up a subsidiary, business unit, or regional division, parentOrganization tells structured data consumers which entity sits above it in the corporate hierarchy.

The value is an Organization object. At minimum, include name and url. Where applicable, adding sameAs pointing to a Wikidata or Wikipedia entry for the parent significantly improves entity resolution across knowledge graphs.

Why this matters for AEO

AI answer engines construct organizational hierarchies from structured data. When a user asks "Who owns Instagram?" or "Is DeepMind part of Google?", language models look for structured relationship data that connects entities. parentOrganization provides a direct machine-readable link from a subsidiary to its owner.

Without this field, AI systems must infer corporate relationships from text, which is error-prone and can become outdated. A structured parentOrganization declaration gives search engines and AI answer systems an authoritative, crawlable source for ownership and hierarchy information.

This field is particularly valuable during corporate acquisitions. The structured relationship updates cleanly, while unstructured copy across many pages takes time to propagate.

What the specs say

Schema.org:parentOrganization expects an Organization value. The larger organization that this organization is a subOrganization of, if any. [Source: https://schema.org/parentOrganization]

Google: Not mentioned in Google's structured data documentation for Organization as a specific rich result trigger. It contributes to Knowledge Panel entity resolution for corporate groups. [Source: https://developers.google.com/search/docs/appearance/structured-data/organization]

How to find your value

Identify the direct legal parent. If your organization is a wholly owned subsidiary, name that parent. If there are multiple layers (subsidiary of subsidiary), name the immediate parent, not the ultimate holding company, unless your implementation requires the full chain.

For the parent Organization object, provide:

• name: official legal name of the parent
• url: parent organization's canonical website
• sameAs: Wikipedia or Wikidata URL for entity disambiguation

Format and code

Subsidiary with parent

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Instagram",
  "url": "https://www.instagram.com",
  "parentOrganization": {
    "@type": "Organization",
    "name": "Meta Platforms",
    "url": "https://about.meta.com",
    "sameAs": "https://en.wikipedia.org/wiki/Meta_Platforms"
  }
}

Regional division with parent

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Google UK",
  "url": "https://www.google.co.uk",
  "parentOrganization": {
    "@type": "Organization",
    "name": "Google LLC",
    "url": "https://www.google.com",
    "sameAs": "https://en.wikipedia.org/wiki/Google"
  }
}

Multi-layer hierarchy

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "DeepMind",
  "url": "https://deepmind.google",
  "parentOrganization": {
    "@type": "Organization",
    "name": "Alphabet Inc.",
    "url": "https://abc.xyz",
    "sameAs": "https://en.wikipedia.org/wiki/Alphabet_Inc."
  }
}

Webflow implementation

Static pages

Add to Page Settings > Custom Code on the subsidiary's organization page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Organization",
  "url": "https://yoursite.com",
  "parentOrganization": {
    "@type": "Organization",
    "name": "Parent Company Name",
    "url": "https://parentcompany.com"
  }
}
</script>

CMS template pages

If subsidiary pages are managed through a Webflow CMS collection, store the parent organization name and URL as CMS fields and reference them in a custom code embed on the template.

In Schema HQ

The parentOrganization field is configured in Schema HQ's organization schema editor field. Provide the parent name and URL and Schema HQ generates the correct nested Organization object in the JSON-LD output.

Real examples

YouTube (owned by Google):

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "YouTube",
  "url": "https://www.youtube.com",
  "parentOrganization": {
    "@type": "Organization",
    "name": "Google LLC",
    "url": "https://www.google.com",
    "sameAs": "https://en.wikipedia.org/wiki/Google"
  }
}

LinkedIn (owned by Microsoft):

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinkedIn",
  "url": "https://www.linkedin.com",
  "parentOrganization": {
    "@type": "Organization",
    "name": "Microsoft",
    "url": "https://www.microsoft.com",
    "sameAs": "https://en.wikipedia.org/wiki/Microsoft"
  }
}

Related fields

• subOrganization
• department
• memberOf
• sameAs
• legalName

FAQ

What is the difference between parentOrganization and memberOf?

parentOrganization describes a corporate ownership or structural hierarchy. memberOf describes membership in an association, trade group, or professional body. A company can be a subOrganization of its holding company (parentOrganization) while also being a memberOf an industry trade association.

Should I declare parentOrganization on the parent's page or the subsidiary's page?

Declare it on the subsidiary's page. The subsidiary identifies its own parent. The parent organization uses subOrganization on its own page to enumerate its children. Both declarations together create a bidirectional machine-readable relationship.

Does Google use parentOrganization for Knowledge Panels?

Google does not explicitly document parentOrganization as a required or recommended field, but corporate ownership relationships do appear in Knowledge Panels. Providing this field in structured data gives Google a verified source for that relationship rather than inferring it from third-party sources.