Family Tree Mistakes: The Errors Hiding in Almost Every Tree

If your tree has been growing for a while, it almost certainly contains family tree mistakes. Not because you were careless — because genealogy software makes it easy to add a person in two clicks, and because online trees copy each other. One wrong date entered years ago can quietly distort everything built on top of it. The good news: the most common errors fall into a few recognizable classes, and every one of them can be checked.

Impossible dates

The simplest family tree mistakes are arithmetic. A man who dies in 1880 and marries in 1885. A mother who was eight years old when her daughter was born. A child born twelve years after his father's death. These slip in when a date is typed wrong, when a birth year is estimated and later treated as exact, or when two different people's dates end up on one profile. A systematic check reads every date in the tree and flags the ones that cannot all be true at once. It is the fastest win in any error check, because the math never gets tired.

Two people merged into one

Same name, same county, roughly the same age — sooner or later, two different men get merged into a single profile. The result is a person who seems to be in two places in the same census year, whose children are born in two different states in the same twelvemonth, and whose "wife" changes names without any marriage or death in between. Untangling a merge means going back to the records and asking, for each fact, which of the two people it actually belongs to. Until that is done, every generation above the merge is suspect, because you may be climbing the wrong man's line.

Copying other trees without records

Most online trees grow by accepting hints and copying other members' work. Sometimes that work is excellent. Sometimes one person's guess — a parent attached because the name "looked right" — gets copied into fifty trees, and after enough copying it starts to look like established fact. It isn't. A fact is only as good as the record behind it. In our reports we label every finding Verified, Supported, Inference, or Conflict, so you can see at a glance what is proven by a record and what is still a working theory. When you check your own tree, ask of every key fact: what record says this? If the only source is another tree, treat it as a lead, not a conclusion.

Places that are wrong — or didn't exist yet

Place errors are quieter than date errors. A town entered in the wrong state. A county name used for a year before that county was created — which means the record you want is filed under the parent county instead. A birthplace copied from a modern map when the family actually lived in a district that later became a different county entirely. These mistakes send you searching the wrong courthouse, the wrong archive, and the wrong census district, and they can make a perfectly findable ancestor look like a dead end.

Children attached to the wrong spouse

When an ancestor married more than once, genealogy software — and researchers — often attach all the children to the first spouse. The fix is a timeline: line up the marriages, the spouses' death dates, and each child's birth, and see which mother was actually alive and married to the father at the time. Getting this wrong doesn't just mislabel one person; it sends you up an entirely wrong maternal line.

How to check your family tree for errors

You can do this yourself, person by person: run the date math, demand a record for every parent–child link, check each place against the year it was recorded, and rebuild the timeline for anyone with two marriages. It is slow work — and it is exactly the work our Family Tree Error Check was built to do. The check scans the whole tree for every class of error above and reports what it finds, each finding labeled by how solid the evidence behind it is.

Get your tree checked

Start free. Create a free account, upload your GEDCOM file, and you'll instantly see your tree's problem counts — how many impossible dates, possible duplicates, missing details, and unsourced people are in it.

Want the full picture? The Family Tree Error Check (from $25) goes through your tree person by person and returns a written report with every finding labeled Verified, Supported, Inference, or Conflict, plus a downloadable GEDCOM file of your tree. Returning customers get 20% off every order after their first.

See the Family Tree Error Check

Order by card at tree-detective.com or by email to admin@tree-detective.com.