MyHeritage Smart Matches: Are They Worth It?

What a Smart Match Is

A Smart Match is MyHeritage telling you that someone in your family tree also appears in another member's tree. Nothing more: it is a pointer to another researcher's work, not a historical record. MyHeritage's sister feature, Record Matches, points at actual documents (censuses, parish registers, newspapers); Smart Matches point only at trees.

For family historians this matters because other people's trees are the fastest way to grow a tree, and also the fastest way to fill it with other people's mistakes. Used well, a Smart Match leads you to a cousin who has already found the baptism you have been chasing for years. Used badly, it lets you import a stranger's guesswork in one click and present it as your ancestry.

This article explains how the feature works, how Ancestry, FamilySearch, Findmypast and others do the same job, where the real risks lie, and a practical method for using Smart Matches without wrecking your tree.

How Smart Matches Work

Every time you add or edit a person, MyHeritage compares that profile against every other tree on its platform, plus the Geni World Family Tree and (under licence) the FamilySearch tree. The comparison is "fuzzy": it weighs names, dates, places and, crucially, the surrounding family, so that a Jon Smith in your tree can match a John Smyth in someone else's if the parents and siblings line up. Both tree owners are notified when a match is found (MyHeritage Help Center).

The technology is older than MyHeritage's version of it. It began as SmartMatching on the GenCircles website, built by Pearl Street Software, which MyHeritage bought in 2006 (Data Mining DNA).

Where you see them. A green icon on a person's card in your tree, email alerts, and the Discoveries menu, which lists matches either by people (one ancestor, all their matches) or by source (one other tree, all the people you share). Record Matches, which point at documents, use a brown icon and sit alongside them in the same lists.

What happens when you click Confirm. Confirming only records that you agree the two profiles are the same person. Nothing is copied into your tree until you also click Save to tree, where you can tick individual facts or use Extract all info. By default a save adds a citation to the other tree as a source, even if you take no facts from it (Data Mining DNA). You can also Reject a match (meaning "not the same person") or Ignore this tree to silence a poor-quality source entirely.

Sorting is by value, not confidence. The default order puts first the matches that would add the most new information to your tree, not the ones the algorithm is surest about. MyHeritage publishes no per-match confidence score, so a match at the top of the list is not necessarily a more reliable one (Data Mining DNA).

Three features sit on top of Smart Matches:

Feature	What it does	Risk level
Record Matches	Matches your people to historical records, not trees. Brown icon.	Low: you can read the record yourself
Instant Discoveries	Bundles a Smart Match into a one-click import of up to 50 people at once; the first is free, the rest need a PremiumPlus or Complete plan (MyHeritage Knowledge Base)	High: whole branches arrive unverified
Theory of Family Relativity	Chains pending and confirmed Smart Matches and Record Matches to explain how a DNA match is related to you; requires a site subscription or a one-off DNA unlock fee (MyHeritage Blog)	Medium: a wrong Smart Match produces a wrong theory

Subscription. Seeing that matches exist is free, but reviewing and confirming them in full needs a paid plan (Premium or above), and free trees are capped at 250 people. Matches also arrive faster for subscribers. Smart Matching can be switched off per tree, and matching to Geni is a separate toggle (Data Mining DNA).

Do Other Sites Do the Same Thing?

Yes. Every major platform now compares your tree against its own records and, on most of them, against other members' trees. MyHeritage's distinctive choices are to keep tree hints and record hints visibly separate, to reach across platforms (Geni, FamilySearch), and to match names across 42 languages and alphabets (Data Mining DNA).

The important split is between the separate-trees model (MyHeritage, Ancestry, Findmypast) and the one-tree model (FamilySearch, Geni, WikiTree). On a separate-trees site a hint invites you to copy from a stranger; on a one-tree site it invites you to merge with them, which is a stronger commitment and tends to come with more community scrutiny (Amy Johnson Crow).

The table also shows why it pays to cross-check hints across sites rather than live on one. The record collections differ: if a line runs through Scottish or Irish parish registers, Findmypast's record hints will often surface an entry that MyHeritage's collections never show you, because the two sites licence different registers. A tree hint on one site is a reason to go looking for the record on another.

On accuracy, MyHeritage itself says its matches are correct in the high ninety-percent range, a figure based on how often users accept them (as reported by Family Tree Magazine). Treat that figure carefully: acceptance measures whether users agreed two profiles were the same person, not whether the facts in the other tree were right. Independent reviewers rate MyHeritage's hinting as probably the most accurate of the big sites, while still advising that every hint be checked against records (Genealogy Explained).

Are They a Good Thing?

Yes, as a finding aid. No, as a source. Kept in that role, Smart Matches earn their place for five reasons:

1. They find cousins who are researching the same people. A match is a living person who cares about your ancestor, often with photos, letters or oral history that never reach a record office. You can message them or ask to join their family site.
2. They point across language barriers. A great-grandfather recorded as Ivan in a Cyrillic tree in Minsk and John in yours can be matched, which no manual search would manage.
3. They raise questions you did not know to ask. A second marriage, an emigrant sibling or an unexpected birthplace in another tree is a lead worth testing even if the other tree is poorly sourced.
4. They sometimes carry sources. A well-kept tree will have Record Matches attached to each fact. Following a Smart Match to a tree that cites the baptism register saves you the search.
5. They feed DNA analysis. Confirmed matches are one input to Theory of Family Relativity, so a carefully confirmed tree makes your DNA results more useful (MyHeritage Blog). Our January article on adding DNA matches to your tree will pick this up.

MyHeritage itself gives the same advice: it recommends reviewing each fact rather than clicking Extract all info, warns that a match may be wrong through coincidence or someone else's typing error, and says that accepting matches indiscriminately introduces errors and inconsistencies (MyHeritage Knowledge Base, 8 things to fix).

The Dangers

Errors spread faster than corrections. When one tree gets a parent wrong, and ten people accept the match, there are now eleven trees agreeing with each other. The next researcher sees eleven Smart Matches and takes the consensus as proof. Nothing in the system records who entered a fact first or whether anyone ever checked it (Lineages).

Same-name conflation. The algorithm is good at seeing that two profiles are the same person. It is less good at seeing that two profiles with the same name, the same decade and the same county are different people. Rural parishes full of cousins named John and Mary are exactly where this fails. Once two men are merged, their children, wives and parents follow.

Instant Discoveries. Up to 50 people can be added to your tree in one click, and once added, each new person generates their own Smart Matches, which generate more Discoveries. Experienced users describe the result as a "Frankenstein tree" stitched from unrelated branches. MyHeritage's own documentation concedes that the manual route "might ensure greater accuracy" (MyHeritage Knowledge Base, Data Mining DNA).

Boomerang matches. Your own research comes back to you from a tree that copied it, now looking like independent confirmation. You can spot these when your photos appear in the other tree. Keep a note of which trees copy from you.

Wrong matches poison DNA theories. Theory of Family Relativity builds on pending as well as confirmed Smart Matches. A wrong match you never got round to rejecting can produce a plausible but false explanation of a DNA cousin (Data Mining DNA).

No easy route to the evidence. From the match comparison page there is no one-click way to see what records, if any, back the fact being offered. Checking properly means opening the other tree, and if it is private, waiting for a membership request to be answered.

Value sorting hides risk. The matches offering the most new information float to the top. Those are also the matches where the other tree has gone furthest beyond what you can verify.

Fatigue. Unreviewed matches pile up into the thousands. Users respond either by bulk-accepting or by switching the feature off, and both throw away the feature's real value.

Re-uploads reset everything. Deleting your tree and re-uploading a GEDCOM wipes every match you ever confirmed, rejected or ignored, and the whole backlog comes back. If you keep your master tree in a desktop program, this one catches people again and again.

Spouses and in-laws. Matches on a 3rd cousin's wife are indistinguishable in the list from matches on your direct line, and there is no filter to exclude them.

The Best Approach

Treat a Smart Match as a tip from a stranger: worth hearing, never worth repeating until you have checked it. In practice that means the following.

Before You Start

1. Build a documented core first. Enter your family back to your grandparents or great-grandparents from records you hold or have found yourself. Matching works on context, so a well-sourced core produces better matches and gives you a yardstick to test them against.
2. Set your expectations about cost. You can see that matches exist for free, but reviewing them properly needs a paid plan, and the 250-person free tree limit arrives quickly. Decide whether the subscription is for records (the stronger case) or for trees before you pay.
3. Never use Instant Discoveries on a branch you cannot already verify. If you use them at all, restrict them to a tree whose owner you know and whose sourcing you have inspected. MyHeritage's own guidance says as much (MyHeritage Knowledge Base).

Working a Match

1. Work one branch at a time, not the whole list. The counter is not a to-do list; it refills as you edit. Pick the ancestor you are researching and open only their matches.
2. Sort by relation, not value. This pushes distant cousins' spouses to the bottom and your direct line to the top.
3. Read the other tree before you read the match. Open the source tree in a new tab. Does it cite records? Does it have obvious signs of bulk import: tens of thousands of people, duplicate children with the same birth date, a woman married at two? If so, Ignore this tree and move on.
4. Ask what the new fact rests on. For each piece of "new info", look for the record that supports it. If the other tree has none, search MyHeritage's records or FamilySearch for it yourself. Add the fact from the record, with the record as the source, and cite the tree only as the lead that pointed you there.
5. Confirm, then save selectively. Clicking Confirm commits you to nothing. Scroll the comparison and tick only the facts you have verified. Never click Extract all info.
6. Half-right match? Confirm and comment. If it is the right person with a wrong date, confirm the identity and leave a comment for the other owner explaining the discrepancy. Reject only when it is a different person, and say why in a comment.
7. Park what you cannot finish. Save a promising new person as an unattached "floater", research them later, and connect or delete them when you know.
8. Contact the owner. The person behind a good match is the real prize. Ask what they have that is not in the tree.

Housekeeping

• Re-review confirmed matches every few months; other trees change after you confirmed them (MyHeritage Knowledge Base).
• Keep a list of trees that copy from you, so boomerang matches do not read as confirmation.
• If you maintain your master tree elsewhere, sync rather than delete-and-reupload, or expect every reviewed match to come back.
• After any session that added people from matches, run MyHeritage's Consistency Checker, then export a GEDCOM and run it through the free GEDCOM Checker as well. It finds the duplicate people, impossible dates and loose ends that bulk imports leave behind, in your browser, without uploading anything.
• If a Theory of Family Relativity looks wrong, find and reject the Smart Match that feeds it.

A Simple Rule for Your Own Tree

Every fact in your tree should rest on at least one record, not on another tree. Smart Matches tell you where to look. Records tell you what is true. Keep the two jobs separate and the feature is one of the most useful things on the site; blur them and it is one of the most destructive.

The same rule decides what ends up on the wall. A printed family tree is only as good as the tree behind it: a chart drawn from a tree padded with unverified matches shows the wrong people in the wrong places, in good typography. Clean the tree first, then the chart is worth framing.

Conclusion

Smart Matches are the best tree-to-tree matching tool on any of the big genealogy sites, and the one most likely to wreck a tree in careless hands. The technology is sound; the weakness is that it presents other people's unverified work in the same confident interface as historical records. Use it to find cousins and leads, insist on a record for every fact, stay away from bulk imports, and you get the benefit without the damage.

Sources

• What is a MyHeritage Smart Match and how do I use Smart Matching?, MyHeritage Help Center
• What Smart Matches Are and How to Make the Most of Them, MyHeritage Knowledge Base
• Introduction to Instant Discoveries, MyHeritage Knowledge Base
• 8 Things That Could Be Harming the Quality of Your Family Tree, MyHeritage Knowledge Base
• Introducing the Theory of Family Relativity and 103 Million Theories Added, MyHeritage Blog
• MyHeritage Smart Matches: 24 Powerful Tips, Data Mining DNA
• Making the Most of Record Hints, Lineages
• Should You Take the Family Tree Hint?, Family Tree Magazine
• Family Tree Hints vs Record Hints, Family History Fanatics
• Ancestry vs FamilySearch vs MyHeritage vs Findmypast, Genealogy Explained
• Using hints and historical records, Findmypast
• Geni.com Tips for Beginners, Family Tree Magazine
• What's this Geneanet Ancestry Record Hint?, Genealogy Gems
• What Kind of Online Family Tree Is Right for You?, Amy Johnson Crow
• GEDCOMpare, WikiTree

Read next

How to Check a GEDCOM File for Errors The free in-browser checker that finds the duplicates, impossible dates and loose ends a tree view hides. How to Export Your Family Tree as a GEDCOM File Exact export steps for MyHeritage, Ancestry, Findmypast, FamilySearch, RootsMagic and Family Tree Maker.