How to Find Your Ancestors When Your Tree Has the Wrong Person in It
*This post may have affiliate links, which means I may receive commissions if you choose to purchase through links I provide (at no extra cost to you). All opinions remain my own.
You found her. Your great-great-grandmother, sitting right there in someone else's public tree. The name matched. The birth year was close enough. So you clicked the little green leaf, added her, and moved on.
Then something stopped adding up. A birth date when her mother was 55 years old. A son born while she was living three states away. A marriage to a man who, by other records, was already married to someone else at the time.
If that sounds familiar, you're in very good company. Learning how to find your ancestors is only half the work. The other half is confirming that the people you found are actually yours.
Wrong ancestors are common, and they spread fast, because online trees copy each other. One mistake somebody made years ago can sit in a hundred trees today. The good news is that these errors leave fingerprints. Once you know what to look for, you can spot them, and you can fix them without losing the research you've already done.
Hi, I'm Jessica
I've been chasing my own family history for 20 years, and I've worked as a professional genealogist for the last 5. My specialties are Hawaii, New England, and Quebec and French-Canadian research.
I've untangled a lot of mixed-up trees, including my own. (My Samuel Jones brick wall is still standing, so I know the feeling.) I've also learned that most people don't need to start over. They just need a clear way to check what they've got.
If you'd rather hand the digging to someone else, I offer Done-For-You research packages, and you can always book a free 20-minute chat first to see if we're a good fit.
How to Find Your Ancestors and Know You Have the Right Person
Here's the short version, for anyone in a hurry:
Start with yourself and work backward one generation at a time. Never skip ahead to the famous name.
Find a record for every person and every event. A name in someone's tree isn't proof of anything.
Check that every date and place is possible for one human being.
Look for a record that states a relationship, like a parent, a spouse, or a child. Matching names alone won't do it.
Write down where you found it. Every time.
That last step is the one people skip, and it's the one that saves you later. When a conflict shows up in three years, your notes are what tell you which record to trust.
The rest of this post walks through what goes wrong and how to sort it out.
The Sneaky Ways Wrong Ancestors End Up in Your Tree
Nobody adds a wrong ancestor on purpose. They sneak in, usually in one of these ways.
You accepted a hint without opening the record. Ancestry's hints are suggestions, not conclusions. The system is matching patterns, and it doesn't know your family.
You copied another tree. If that tree has no sources attached, you didn't gain evidence. You gained someone else's guess.
You trusted a transcription. Indexes are typed up by volunteers (or machines) reading old handwriting. A census taker's loopy letters (bless him) can turn Daniel into David, or Neaves into Nearer.
You filled a gap because it felt right. This one's human. You want the line to keep going, so you take the closest match and keep moving.
You inherited the error. A family group sheet from 1978, a published county history, a cousin's binder. Older doesn't mean verified.
For a deeper look at keeping your sources straight from the start, see How to Organize Your Genealogy Files.
Red Flags That You've Copied Someone Else's Mistake
Scan your tree for these. Any one of them is worth a second look:
A person with no sources attached at all, or only "Ancestry Family Trees" as the source
A mother who was younger than 15 or older than 50 when a child was born
A gap of more than about four years between children in a family that otherwise had babies every two years
Children born in two distant places in the same year
A death date that comes before a listed marriage or birth of a child
A birthplace that doesn't match any record, only other trees
For men, two different occupations in the same time period
An ancestor who suddenly jumps countries with no immigration record behind it
Someone has a tree with my 4x great-grandfather, Samuel Jones, being in jail in England at the same time as he was living in Vermont and having kids. I’m very sure he never left the country, let alone got jailed in in the UK!
If you find one, don't delete anything yet. Flag it and keep reading.
Same Name, Different Person: Why This Trips Up So Many Trees
This is the single most common way a wrong ancestor gets in.
Families reused names on purpose. A son was named for his father or grandfather. Cousins were named for the same great-uncle. In a small town, you can easily have three men named John Bouchard born within five years of each other, all living within a few miles.
Now add a second problem. People stayed put. Brothers settled on neighboring farms. Their sons married local girls and stayed too. So you get a cluster of same-named men in the same county, in the same records, at the same time.
Sorting them out takes locality knowledge, meaning you learn the place, not just the person. What churches were there? Which county held the land records? Did the county lines move? Once you understand the records available in that spot, the men start to separate.
My Locality Research Navigator is a 20-page template built for exactly this, and it walks you through building that regional expertise step by step.
How to Re-Verify a Shaky Connection From Scratch
When you've flagged a person, treat them like a stranger. Set aside what the tree says and rebuild.
Start With the Record That Names the Relationship
You're not looking for a person with the right name. You're looking for a document that says this person is the child of that person. Strong options include:
Baptism and christening records, which usually name both parents
Death certificates, which often name parents and a birthplace
Marriage records, which sometimes name fathers or list consent from a parent
Probate and will records, which name heirs directly
Land deeds, especially ones dividing a parent's property among children
Then check the source itself. Was it written at the time of the event? Who gave the information? A death certificate is a great record for the death, and a shaky one for the birth date, because the person answering questions was grieving and guessing.
If you get stuck at this stage, my Brick Wall Breakthrough Blueprint is the workbook I built for this exact moment. It's my signature framework for working a roadblock instead of circling it.
Build a Timeline to Catch Impossible Dates and Places
This is the fastest error-finder I know, and it costs you nothing but an hour.
List every event you have for one person in date order. Birth, baptisms of children, census appearances, land purchases, moves, death. Put the place next to each one.
Then read down the column. You're looking for things a real person can't do:
Two events on or close to the same date in two different states
A child born after the father died (possible, but only for about nine months)
A land purchase after the supposed death date
Children born less than nine months apart
A signature on a document from someone who was illiterate
When a timeline breaks, you've almost always got two people wearing one name.
You can build this by hand in a notebook, and plenty of people do. If you'd rather start from something ready-made, my Ancestor Timeline template comes in a watercolor design and a minimalist black and white version (that one saves your printer ink), and both are editable, so you can type each event or write it in.
Want the longer walkthrough? I broke the whole process into steps in 7 Simple Steps to Create a Genealogy Timeline.
When DNA Confirms (or Contradicts) Your Paper Trail
DNA is useful here, but with limits worth knowing.
What it does well: If you and several documented descendants of the same couple all share DNA, that supports the connection.
What it can't do: DNA won't hand you a name. It shows you that two people are related and roughly how closely. You still need records to say how. That's why you still need the paper trail.
When it contradicts you: Sometimes the expected matches simply aren't there. That can mean a wrong ancestor several generations back, no other descendants have tested yet, or it can mean something closer to home, like an adoption or a misattributed parentage nobody discussed. Go gently with this. Real families are involved, and living people may not know.
If your DNA results and your tree disagree, resist the urge to rebuild everything overnight. Pick one generation, verify it with records, and continue your research from solid ground.
Not sure which DNA test to take, or whether to test at all? I compared the main options in Best DNA Tests for Ancestry.
How to Correct Your Tree Without Losing Your Research Trail
Please don't hit delete. That's how you end up redoing years of work.
Try this instead:
Detach, don't delete. In most software you can remove a relationship while keeping the person in your file. The research stays.
Add a note explaining why. Write the date and the reason. "Detached 08/2026. Timeline shows this John was in Rhode Island in 1854. Ours was in Maine."
Keep the disproven records. Keeping a record of why you ruled someone out stops you from redoing the same work later to retrace why you already eliminated them.
Move the person to a separate file or a "holding" group so you can find them later.
Fix the generation, then work downward and check anyone whose line ran through that person.
Update your public tree if you have one. You'll save some future researcher a real headache.
Correcting a tree isn't a failure, but the sign of a researcher who's paying attention.
What If the Records You Need Aren't Online?
Often, they're not. A large share of genealogy records have never been digitized, and they sit in county courthouses, church basements, town clerks' offices, and regional archives. That's especially true for the places I work in most: rural New England towns, Quebec parishes, and Kingdom-era to modern-day Hawaii.
That's usually the real reason a shaky connection stays shaky. The proof exists. It just isn't on a website.
You can write to an archive yourself, and plenty of people do. If you'd rather not, that outreach is a big part of what I do. Find out more here.
Not sure which you need? Book a free 20-minute consultation and we'll figure it out together. No pressure either way.
Frequently Asked Questions
What should I do when two records give different dates for the same person?
Weigh them by who gave the information and how soon after the event it was recorded. A baptism record created days after a birth beats a death certificate filled out 70 years later by a grieving relative. When two records are equally close, look for a third to break the tie. Record both dates with a note about which one you trust and why.
How many records do I need before a connection counts as proven?
There's no magic number. Professional genealogists work from the Genealogical Proof Standard, which asks for a thorough search, accurate citations, careful analysis, and a written explanation that resolves any conflicts. In practice that usually means several independent records that agree, plus a clear answer for the ones that don't.
Can I fix a mistake in someone else's online tree?
It depends on the site. On Ancestry you can't edit another person's tree, though you can message the owner and share what you found. On collaborative sites like FamilySearch, the tree is shared, so you can make the correction yourself. If you do, attach your source and explain your reasoning so the next researcher understands the change. But also, be prepared that someone else may come along and undo your corrections anyway.
What if my family's story doesn't match the records?
That happens more often than you'd expect. Family stories usually hold a grain of truth wrapped in a few generations of retelling, so treat the story as a clue instead of a fact. Write down what the records actually show, keep the story in your notes, and see which pieces the documents eventually support.
Do I need to verify every person in my tree?
Not all at once. Start with your direct line, meaning your parents, grandparents, and back from there, because an error there affects everyone below it. Collateral relatives (aunts, uncles, cousins) can wait until you need them to solve a problem.
Where to Go From Here
Finding a wrong ancestor in your tree feels awful for about a day. Then it gets interesting, because the moment you pull that person out, the records start making sense again.
Pick one shaky connection this week. Just one. Build a timeline for that person, then go looking for a record that names the relationship, directly or indirectly. You'll either confirm what you had or find the crack, and both outcomes move you forward.
If you'd like help, the Brick Wall Breakthrough Blueprint will walk you through my full process, and you can browse the shop for the worksheets that fit where you're stuck. And if you'd rather have me do the digging, especially the archive work that never shows up in a search box, my Done-For-You research packages are open, and the free 20-minute consultation is always there first.