subOrganization

subOrganization · Optional

Appears in

• Organization

What is it?

subOrganization declares that another organization is a subsidiary, division, or child entity of the current organization. It is the inverse of parentOrganization. A parent company uses subOrganization to enumerate its owned entities, while each subsidiary uses parentOrganization to point back up.

The value is an Organization object. Multiple subsidiaries are expressed as an array. Each nested organization can carry its own name, url, sameAs, and other organization properties.

Why this matters for AEO

AI answer engines build corporate knowledge graphs from structured relationship data. When a user asks "What companies does Alphabet own?" or "Is YouTube a Google company?", AI systems look for structured ownership declarations. subOrganization provides a machine-readable list of an organization's owned entities that AI systems can use to answer these questions directly.

This field is particularly valuable for conglomerates, holding companies, and media groups where the parent brand name does not always appear on subsidiary sites. The structured declaration lets AI systems surface the relationship even when it is not prominent in the page copy.

What the specs say

Schema.org:subOrganization expects an Organization value. A relationship between two organizations where the first includes the second, e.g., as a subsidiary. See also: the more specific 'department' property. [Source: https://schema.org/subOrganization]

Google: Not mentioned as a specific rich result trigger in Google's structured data documentation for Organization. Contributes to knowledge graph entity resolution. [Source: https://developers.google.com/search/docs/appearance/structured-data/organization]

How to find your value

List all direct subsidiaries and wholly owned entities. For each subsidiary, provide at minimum a name and url. Adding sameAs with a Wikipedia or Wikidata identifier improves entity resolution.

Limit entries to direct subsidiaries. Listing all downstream companies through multiple layers of ownership creates unnecessarily complex structured data. The subsidiary's own page should declare its own children.

Format and code

Holding company with subsidiaries

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Alphabet Inc.",
  "url": "https://abc.xyz",
  "sameAs": "https://en.wikipedia.org/wiki/Alphabet_Inc.",
  "subOrganization": [
    {
      "@type": "Organization",
      "name": "Google LLC",
      "url": "https://www.google.com",
      "sameAs": "https://en.wikipedia.org/wiki/Google"
    },
    {
      "@type": "Organization",
      "name": "DeepMind",
      "url": "https://deepmind.google",
      "sameAs": "https://en.wikipedia.org/wiki/Google_DeepMind"
    },
    {
      "@type": "Organization",
      "name": "Waymo",
      "url": "https://waymo.com",
      "sameAs": "https://en.wikipedia.org/wiki/Waymo"
    }
  ]
}

Media group with brands

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "News Corp",
  "url": "https://newscorp.com",
  "subOrganization": [
    {
      "@type": "Organization",
      "name": "The Wall Street Journal",
      "url": "https://www.wsj.com"
    },
    {
      "@type": "Organization",
      "name": "HarperCollins Publishers",
      "url": "https://www.harpercollins.com"
    }
  ]
}

Webflow implementation

Static pages

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

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Parent Company",
  "url": "https://parentcompany.com",
  "subOrganization": [
    {
      "@type": "Organization",
      "name": "Subsidiary Name",
      "url": "https://subsidiary.com"
    }
  ]
}
</script>

CMS template pages

For parent organizations with many subsidiaries stored in a Webflow CMS collection, reference each subsidiary's name and URL fields in a code embed on the parent page template.

In Schema HQ

The organization schema editor supports subOrganization entries. Add each subsidiary through the editor and Schema HQ generates the correct nested array structure.

Real examples

Meta Platforms:

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

Related fields

• parentOrganization
• department
• member
• owns

FAQ

What is the difference between subOrganization and department?

subOrganization is for legally distinct child organizations, subsidiaries, or companies under common ownership. department is for internal subdivisions of the same legal entity. A wholly owned company is a subOrganization. A business unit within a single company is a department.

Should I also declare parentOrganization on the subsidiary's page?

Yes. The two fields are inverses. The parent uses subOrganization on its page; the subsidiary uses parentOrganization on its page. Both declarations together create a bidirectional relationship in the structured data graph.

How deep should the subOrganization chain go?

Limit to direct subsidiaries only. Each organization in the hierarchy should declare its own direct children. Multi-level nesting in a single JSON-LD block is valid but makes the document harder to maintain and update.