Your structured data declares your parent company or subsidiaries with verifiable links
Can AI systems trace your corporate hierarchy to disambiguate brand-versus-parent confusion?
What this signal tests
We check whether your Organization JSON-LD declares its place in a corporate hierarchy. If you are a subsidiary, your homepage should include a parentOrganization with the parent's name, URL, and ideally a sameAs link to the parent's Wikidata entry. If you are a parent with subsidiaries, the reverse: a subOrganization array pointing to each subsidiary.
Why it matters for your visibility in AI
Corporate hierarchies confuse AI systems. Is Instagram a separate company or part of Meta? Is DeepMind owned by Google or Alphabet? Without explicit parent or subsidiary linkage in your structured data, AI assistants must guess from page text, which is often outdated or wrong. A concrete consequence: a financial-news user asks Perplexity "what are Acme Corp's holdings in renewable energy?" If your subsidiary GreenAcme does not declare Acme as its parentOrganization, the assistant may miss the connection entirely and report that Acme has no renewable holdings. Worse, it may attribute GreenAcme's actions to a similarly-named unaffiliated company. Explicit parent or subOrganization linkage removes that ambiguity in a single field.
Pass criteria at a glance
| Criterion | Passes when |
|---|---|
| parentOrganization or subOrganization present and points to resolvable entity. |
How we test it
We parse the Organization JSON-LD on your homepage and look for either a parentOrganization or a subOrganization property. parentOrganization must be a single Organization object; subOrganization must be one or more. Each linked organization must have a name and at least a url or sameAs (ideally a Wikidata Q-number). We resolve the linked URL to confirm the entity exists. If neither property is present, or the link is broken, the signal fails.
Show technical detection method
Organization.parentOrganization is Organization object with name and url/sameAs; reverse on parent.
If your site fails: how to fix it
- Determine your position in the corporate hierarchy: are you the parent, a subsidiary, both, or neither (a standalone entity)?
- If you are a subsidiary, add a parentOrganization object to your Organization JSON-LD with the parent's name, url, and a sameAs URL to the parent's Wikidata Q-number.
- If you are a parent with subsidiaries, add a subOrganization array with one object per subsidiary, each containing name, url, and sameAs.
- Keep the hierarchy bidirectional where possible: the subsidiary's site should declare parentOrganization and the parent's site should declare subOrganization referring back.
- If your hierarchy changes (acquisition, spinoff), update both sides within a week; stale hierarchy data is a frequent source of AI factual errors.
- Validate with Schema.org Validator and confirm parent or subsidiary URLs resolve.
Quick facts
| Maturity | ESTABLISHED |
|---|---|
| Weight | medium |
| Category | Entity |
Primary sources
Related signals
Frequently asked questions
What if my company is a standalone with no parent and no subsidiaries?
Then this signal does not apply to you and you can ignore it; failing it without a hierarchy to declare is not a meaningful error. The signal mainly targets subsidiaries (most important) and holding companies with multiple brands.
Should the subsidiary link to the parent or the parent to the subsidiary?
Both are valuable, but the subsidiary linking up to the parent is the higher-leverage direction because it disambiguates the smaller brand against confusion with unrelated companies. Parents with many subsidiaries should still maintain a subOrganization list for completeness.
Do I need to expose every internal entity?
No, only entities that have a public-facing identity (separate website, separate brand, separate product line). Internal legal vehicles or holding shells with no consumer presence can be omitted.
What about partnerships or joint ventures?
Use the parentOrganization or subOrganization fields only for ownership relationships. For partnerships, use sponsor, funder, or affiliation properties on the relevant content type instead.
Run your own scan
Run a free scan and see how your site grades across all 155 AI-readiness signals.