The concept mapping guide explains how labels clarify what each connection means. For notes that extend across research sessions, see how to build a visual second brain.

A traditional family tree answers one question well: who descends from whom. But real family history is messier and richer than a tree of boxes. There are second marriages, informal adoptions, migrations, name changes, and the census record that almost confirms a link but not quite. Genealogy mapping gives all of that a place to live.

This post covers where a family tree runs out, and how to map ancestry as a network of people, places, records, and the relationships between them.

Where the Family Tree Runs Out

Tree-shaped genealogy software stores all of this. It files sources, places, and second marriages as fields attached to a person. What it does not do is show them as a network you can look at. That matters most when:

  • Blended and remarried families: step-parents, half-siblings, and multiple spouses sit on separate charts or in a dropdown.
  • Uncertain links: you suspect two people are the same person, but can't prove it yet.
  • The evidence itself: the census, the ship manifest, the parish record. A tree cites them under one person; it does not show which records tie which people together.
  • Places and migration: the town everyone left, the country they arrived in, the county lines that moved.
  • Non-blood relationships: godparents, witnesses, business partners, neighbors who keep appearing in the records. Tree programs file these as associations or notes, off the chart.

The breakthrough in a hard case often comes from a link between two records.

What Genealogy Mapping Looks Like

Instead of a tree, you build a network. Each person, place, and record is a card; each relationship is a labeled connection you can read:

  • People: ancestors, relatives, and the "same person?" duplicates you're still resolving.
  • Places: birthplaces, parishes, ports, and the towns a family moved through.
  • Records: census entries, certificates, wills, and photos, kept as artifacts you can point to.
  • Notes: the reasoning, like "matches the 1901 census, but the age is off by two years."

The strings between them carry the relationship: parent of, married, born in, witnessed, emigrated to, same person as, marked Uncertain.

How to Map Your Family History

Step 1: Start With a Brick Wall

Don't try to map your whole tree. Pick the ancestor you're stuck on, the brick wall, and put them in the center.

Step 2: Add Every Record as a Node

Give each document its own card: the 1880 census, the marriage certificate, the naturalization papers. Connect each record to the people it names. You can then see at a glance which claims rest on solid evidence and which rest on one shaky source.

Step 3: Label Your Confidence

Mark connections as Confirmed, Suspected, or Uncertain, and use a note to record why, with the kind of reasoning that would satisfy the Genealogical Proof Standard. When you come back in six months, the argument is still there.

Step 4: Map the Places

Add the towns and parishes as their own cards and connect people to them. Migration patterns become visible, like the whole family that left one county for one city, and those patterns point you toward the next record to look for.

Step 5: Follow the Cluster

"Cluster genealogy," researching the neighbors, witnesses, and associates around an ancestor, often gets past brick walls that direct-line research leaves standing. A network map is the natural home for it, because it shows who keeps appearing alongside whom.

Keeping It Private

Family history includes living people and sensitive stories: adoptions, second families, things a relative shared in confidence. Much genealogy software is cloud-first and social by default. For the working map where you reason through the evidence, a local file avoids cloud sync. Optional AI analysis sends the board to Google, so leave it off for private family information.

Genealogy Mapping in Redstrings

Redstrings works alongside your tree software. Keep the formal tree in your genealogy program. Use Redstrings for the research map.

  • Person, Place, and Artifact cards for relatives, towns, and every record.
  • Labeled strings like "married," "born in," and "same person as?" that read like sentences.
  • Notes and confidence to record your proof argument beside each link.
  • PNG export to share a clean map with family or attach to your research log.
  • Local storage: boards live on your machine by default. Optional AI analysis sends selected board content to Google with your own Gemini key, and you decide when to use it.

Download Redstrings free and start mapping the ancestor you're stuck on.