Draw the real paths to the same page
Record the page identity and each claimed parent. Verify that the hub exists, is published and provides the context its label promises. An arbitrary topic word is not automatically a useful parent page.
A fictional training library places a course under project management and leadership courses. Both may be legitimate. A third path through a removed campaign is a remaining fault rather than a valuable new alternative.
Decide how alternatives are selected
Define a fixed visible main path or explicit alternatives. A solution depending on a visitor's arrival route must also work on direct entry and within the caching model. One visit's context must not become another person's misleading trail.
Google documents support for multiple BreadcrumbList paths, but that does not justify invented hierarchies. Ground every described path in actual navigation. The page's canonical identity is a separate question from several categories leading to it.
Compare after category and language changes
Change the parent in a safe environment and read the delivered page. Check visible labels, links, order and relevant markup. An updated CMS field does not prove that a built template consumed the new relationship.
Test the decision across affected languages. An equivalent category may be absent or organized differently. Do not invent a parent simply to make every language have the same number of levels.
| Case | Risk | Expected check |
|---|---|---|
| Two real categories | Arbitrary undocumented selection | Documented main path or justified alternatives |
| Removed parent | Trail leads to wrong content | Current relation and real destination |
| CMS-only change | Stale built navigation | Delivered page follows the new decision |
| Direct visit | Missing history dependency | Useful path without a preceding click |
| Missing local equivalent | Wrong language or invented hub | Explicit local handling |
Keep a relationship test for template changes
Record page, intended parents, name source and why the paths are legitimate. Test direct loading, ordinary navigation, mobile and keyboard. Repeat when a parent moves, is translated or unpublished.
Classify failures as wrong relationship, stale delivered version or presentation fault. Calling everything a schema error can hide the underlying content decision. Passing demonstrates your sample and does not guarantee how search results appear.