The Game of Thrones branch in this MVP
This page does not attempt to reproduce every Stark, Lannister, Baratheon, and Greyjoy line. Its Day-One purpose is the high-value Targaryen relationship cluster that explains Daenerys, Rhaegar, Viserys, Lyanna Stark, and Jon Snow. The branch begins with Aerys II and Rhaella, whose children in the current screen-canon dataset are Rhaegar, Viserys, and Daenerys. That shared parent pair lets the engine derive sibling relationships rather than storing them as duplicated facts.
Rhaegar and Lyanna lead to Jon Snow through a separate protected branch. With Spoiler Shield off, the tool shows the complete audited GOT path and warns that the full tree may contain spoilers. With the shield on below season seven, Jon remains available as a character but the protected House and parent relationships do not enter the active graph. This avoids the common privacy leak where a hidden fact is still exposed by search labels, filters, or relationship highlights.
How Daenerys and Jon are related
After the screen reveal is eligible, the relationship engine can travel from Daenerys to her brother Rhaegar and then to Jon. Because Daenerys and Rhaegar share two confirmed biological parents in this work context, they derive as siblings. A sibling of a person's parent is classified with the gender-neutral label 'aunt or uncle' because the frozen Character model does not store gender and the system does not guess it from a name.
That wording is intentionally mechanical inside the tool, while the surrounding page can explain the familiar interpretation in plain English: Daenerys is Jon's aunt in the Game of Thrones screen continuity represented here. The important point is that the answer is generated from visible, confirmed facts. If Spoiler Shield removes either of Jon's parent claims, the result becomes 'no confirmed spoiler-safe path' instead of revealing the answer through a supposedly protected comparison.
Why the GOT tree is intentionally focused
A complete Game of Thrones political genealogy would be a different product. The frozen MVP prioritizes the Targaryen lineage and only includes connected characters needed to answer its core family questions. That keeps the interactive canvas legible on a phone, keeps the index from filling with thin pages, and gives the evidence audit a clear boundary. Future Stark or Baratheon clusters should be added only when their relationships and page content can meet the same standard.
The focused scope also reduces search confusion. This URL targets the broad intent 'Game of Thrones family tree,' but its visible copy clearly states what is complete today and what is not. Visitors can still switch to House of the Dragon or A Knight of the Seven Kingdoms from the same tool because all views come from one canonical dataset. They are projections, not separate diagrams that can drift apart.
Searching and comparing GOT characters
This is a relationship-first guide, not a general plot encyclopedia. The interactive tree sits before the long explanation because most visitors arrive with a practical question: find a person, see the confirmed parents or children, and understand the path to somebody else. Select any node to keep exploring inside the same tree. The character panel separates parents, children, siblings, partners, and dragon bonds so the useful answer is not buried inside a biography.
Every confirmed line in the tree comes from the site's structured screen-canon dataset. Parent claims are stored once and other labels, including sibling, grandparent, aunt or uncle, cousin, ancestor, and descendant, are calculated from those claims. A marriage junction helps the diagram stay readable but does not replace the underlying parent evidence. When the supported screen material does not establish a link strongly enough, the site leaves it unconfirmed instead of completing the branch from book knowledge.
Spoiler Shield is optional and starts off. When it is enabled, progress is saved separately for Game of Thrones, House of the Dragon, and A Knight of the Seven Kingdoms. Protected identities, parentage, unions, and status details can disappear independently. If progress is unknown, the filter fails closed: it asks for progress rather than assuming every season has been watched. Shared URLs restore the selected character and useful filters while clean page URLs remain the canonical versions for search engines.