How accurate is FamilySearch? How to check an index against the original record

On this page
  1. What an index is, and what it is not
  2. A correction from the example
  3. Check a record step by step
  4. When records disagree
  5. How accurate are the big sites?
  6. What each record can and cannot prove
  7. What is still unknown
  8. When to ask for help
  9. Questions people ask
The short answer

How accurate is FamilySearch? Its record images are as accurate as the originals, its indexes are volunteers' readings that are mostly right, and its shared Family Tree is only as good as the sources attached to it. To check that a record belongs to your family, open the original image, read every column, and test it against two independent facts, such as the parents' names and the town.

Most family research now begins with an index: a line on a website that gives a name, a year, a place and a pointer to a record. Anyone who asks how accurate FamilySearch is, or Ancestry or MyHeritage, is usually asking about that line. Indexes make millions of pages of registers searchable, and most of their lines are right. The trouble is that a line in an index looks as certain as the record behind it, and the two are different things.

This guide explains how far to trust each part of the large sites, tells how the example on this site withdrew an identification once the original was read, and sets out the steps that keep a wrong ancestor out of a family tree.

Key points

  • An index is someone else's reading of a record, and it can misread a name or a date.
  • The record images on FamilySearch, Ancestry and MyHeritage are as reliable as the originals; the indexes and trees need checking.
  • Before a record goes into a tree, open the original and test it against the parents' names and a second record.
  • In the example, an index listed a birth for a Nuta Tarko, the original register read Nuta Marko, and the identification was withdrawn.
  • When records disagree, set them side by side and say which one you follow and why.

What an index is, and what it is not

An index is a list made from records, usually by volunteers or archive staff, so that the records can be searched. It copies a few facts from each entry: the name, the date, the place, sometimes the parents.

The record itself is the page the clerk wrote at the time, with every column he filled in, the margins, the signatures and the later notes. An index points to a record. Only the record says what was written.

How errors get into an index

Most index errors come from reading, and they are easy to make:

  • Old handwriting and faded ink, where a T reads as a P or an M.
  • Records in another language. From 1868 the registers of Russian Poland, the Jewish ones among them, were kept in Russian, so a name written in Cyrillic letters had to be read and spelled again in Latin ones.
  • The calendar. The Russian state used the old Julian calendar, twelve days behind ours in the 1800s and thirteen from 1900, so a register entry in Russian often carries two dates, and an index may give either.
  • Columns read in the wrong order, so a witness or a parent becomes the child.
  • Names that vary in Jewish records: a Hebrew name and a Yiddish or civil form for the same person, a patronymic in place of a surname, and children registered under their mother's surname when their parents had married only in a religious ceremony, which is common in the records of Galicia.

Online trees are copies of other people's conclusions

A family tree on a genealogy site shows what its owner decided, with or without a record behind it. When one tree is copied into another, the mistake is copied too, and a wrong date or parent can turn up in dozens of trees that all seem to agree.

Agreement between copies is not evidence. Look for the record each tree cites, and read that.

A correction from the example

In the research for the example on this site, the Tarko family history, an index of Polish Jewish records listed a birth in 1896 for a Nuta Tarko. It looked like a find. Natan Tarko, the father of the family in the book, went by Nuta in Poland, and by his own account he was born in 1895. The name was right and the year was one off, which is common in records of that time.

The original register told a different story. The entry read Nuta Marko. The index had read the M as a T, and Nuta Marko was another man. The identification was withdrawn, and the book does not use the entry. The same correction is the example for step five of How we work, reading and checking.

What the index said, and what the register said
SourceNameResult
Index of Polish Jewish recordsNuta Tarko, born 1896A possible match, one year from his own date
The original registerNuta MarkoAnother man; the identification was withdrawn

What the book now says about Natan's birth shows the method from the other side. In 1945 he gave his date as 3 March 1895 and his town as Przedbórz, with his parents' names, and his later papers repeat the date. The records of the Łódź ghetto give dates between 22 February and 29 March 1895, and his refugee forms of 1948 and his American papers give Łódź as his birthplace.

The Jewish registers of Przedbórz for 1895, kept in Russian and now online through the Polish State Archives, were read for the weeks after his date, and his birth is not among them, so it may have been registered late. The book follows his own date of 1945, because it is the earliest record and was given with his parents' names. It also says what is still to be read: the yearly indexes at the back of the Przedbórz registers.

How to check a record, step by step

A careful researcher follows these steps for every person in a tree. They take longer than accepting an index line, and they are the only way to know.

  1. Find the original image behind the index entry, on the site that holds it or in the scans of the archive that keeps the register, or write to the archive.
  2. Read every column of the entry, including the margins and any notes added later, and transcribe it in full before deciding what it means.
  3. Match the parents' names. A child with the right name and the wrong parents is someone else.
  4. Match the place and the dates against a second record made at a different time, such as a marriage, a census page or a later document the person gave.
  5. Look for a third record made for a different purpose, so that the facts do not all rest on one informant.
  6. Write down what the record does not show: a missing mother's name, a date that does not fit, a town that is spelled two ways.
  7. Record where the original is kept, with the register, the year and the entry number, so that anyone can find it again.

Checklist

  • I have seen the original image, and read more than the index line.
  • The parents' names match what I already know.
  • The place and the date agree with a second record made at another time.
  • I searched every spelling of the name and the town.
  • I have noted what the record leaves out or gets wrong.
  • I have written down where the original is kept.

Tips for checking family tree information online

Open the source attached to each fact before accepting it, and treat a fact with no source as a question. Watch for a person whose dates or children seem to belong to two people of the same name, a common error in shared trees. Keep your own notes of what you checked and where, apart from any tree on a website.

The Genealogical Proof Standard

Professional genealogists in the United States work to a written standard, the Genealogical Proof Standard, set out by the Board for Certification of Genealogists in its book Genealogy Standards and explained at length in the work of Elizabeth Shown Mills, including Evidence Explained. It asks for five things before a conclusion counts as proved, and the steps above are the same standard in plain terms:

  • reasonably exhaustive research;
  • complete and accurate citations of the sources;
  • analysis and correlation of the evidence;
  • resolution of any evidence that conflicts;
  • a written conclusion that explains the reasoning.

When records disagree

Records often disagree, and a good family history says so instead of choosing quietly. In the example, the mother of the family, Laya, has five different birth dates across her papers. In 1945 she had given a younger age, as many young people did that year, and the younger age stayed on some of her papers.

One woman's five recorded birth dates, from the example
Date givenWhere it is recorded
20 July 1929Her British and American papers
20 July 1930A list of the children who reached England in 1945
1930Other lists of 1945
20 July 1928A tracing office's list
1924A registration in Łódź

The book sets the five dates side by side and tests each against the births of her sisters. Only 1928 fits between the sister born in July 1926 and the sister born in October 1929, so the book follows about 1928 and gives its reasons. It also names the records that would settle the question, the Piotrków birth registers of 1927 to 1929, which have not yet been read.

Five recorded birth dates for one woman, each with the record it comes from and whether it fits between her sisters' births. The table shows which year the book follows and why; it does not settle the day, which no record found so far gives. From the example, Book One, pages 126 and 127.

One man, five spellings

Names change from record to record, and each spelling has to be searched in turn. Natan Tarko appears under five forms in the records used for the example:

One man in five records
SpellingRecord
NatonAmerican census, 1950
NatanA ship's roll, 1949
MotaA committee's search card, 1945
NathanDeclaration of intention, 1950
Natan Neta, and NathanHis gravestone, 1982, in Hebrew and English

In Poland he was Nuta, the Yiddish form of his second name, Neta. Four of these records are shown as images on How we work.

How accurate are FamilySearch, Ancestry and MyHeritage?

The fair answer is that each site holds three kinds of material, and each kind deserves a different level of trust.

What the large genealogy sites hold, and how far to trust each part
MaterialWhat it isHow far to trust it
Record imagesPhotographs or scans of the original registers, censuses and listsAs far as the original itself: these are the records
IndexesNames, dates and places typed from the images by volunteers or staffMostly right, often wrong on names and dates in other languages; always open the image
Member trees and suggested matchesOther users' conclusions, and possible matches the site proposesA lead to follow, never a fact until a record confirms it

FamilySearch and its Family Tree

FamilySearch is free with an account, and many of its collections include the images. Some images can be seen only at a FamilySearch center or an affiliate library, or on a partner's subscription site, under limits usually set by the archive that owns the records. Its indexes were typed by volunteers.

Its Family Tree is one shared tree that any registered user can edit, with one profile meant for each person who has died, so each fact in it is only as good as the source attached to it.

Ancestry and MyHeritage

Ancestry and MyHeritage are subscription sites with large collections of images and indexes. Their record images deserve the same trust as any copy of an original, and their member trees and suggested matches the same caution as any tree.

Find a Grave

Find a Grave is a collection of memorials created by volunteers. A photograph of the stone is good evidence of what is carved on it. The typed dates and the linked relatives are someone's reading, and can be wrong.

DNA estimates answer a different question

Many people who ask how accurate Ancestry is mean its DNA ethnicity estimate, an estimate of where a person's ancestors may have lived, drawn from comparison with other people's samples. It says nothing about which record belongs to which ancestor. A DNA test for Jewish ancestry can point to living cousins, whose papers may lead back to records.

What each record can and cannot prove

Common records, what they usually prove, and where they go wrong
RecordWhat it usually provesCommon errors
Civil or religious birth registerThe child's name, the date, the parents, often the father's trade and the witnessesLate registration, Julian and Gregorian dates, the mother's surname used for the child, a misread surname
Census pageWho lived together on one day, with their ages and how each was related to the head of the houseAges rounded or guessed, names spelled by the enumerator, one informant for the whole house, children left out
Passenger listThe voyage, the age and often the last residence and a relative left behindNames copied by clerks, and towns spelled by ear
Naturalization fileArrival, birthplace, often the exact town, a signature and sometimes a photographThe birthplace given as the nearest city, the birth date changed over the years
GravestoneThe Hebrew name, the father's name, the date of death and often the communityDates carved years later, the age on the stone taken from family memory
Index entryThat a record exists, and where to lookMisread names, dates and columns
Online treeWhat someone else concludedCopied mistakes, and people merged with others of the same name
Printed genealogyA compiler's research, sometimes careful and sometimes notFamily legend printed as fact, no sources given

A gravestone photographed with its Hebrew read and translated is shown on Inside a book. A published family history of another branch is a printed genealogy, and needs the same checks.

What is still unknown

A family history that has been checked against the originals ends up with open questions, and it should say what they are. The example closes with a section that sets out each question, what is known, and which record in which archive might answer it, so a reader can see which conclusions are firm.

"What we still don't know": each open question with what is known and the records that might answer it. From the example, Book One, pages 220 and 221.

When to ask for help

Some of these records can be searched from home. Others are held by archives that answer only written requests, in Polish, German, Russian or Yiddish, and some files have never been indexed at all, so checking them can take months of letters and fees. Doing the research yourself or commissioning it sets out how families decide.

A Zichronos commission includes that work and its archive, copy and translation fees, and ends in a finished book. Every identification in the book is tested against the original record, and the book says which record settles it and what is still unknown. How the example was researched follows the method from the first papers to the printed book. The examples page shows what a finished book holds, what a family history book costs compares the options, and How we work sets out the eight steps. For letters in Yiddish or Hebrew, see how to get old letters read and translated, and for more on the records themselves, finding family records.

Sources: FamilySearch's help article on image restrictions; the Board for Certification of Genealogists, Genealogy Standards; Elizabeth Shown Mills, Evidence Explained; JRI-Poland and the Polish State Archives' Szukaj w Archiwach on the registers of Russian Poland; Find a Grave; the example's notes. Checked October 2026.

Questions people ask

How accurate is FamilySearch?

FamilySearch's record images are copies of the original registers and are as accurate as the originals. Its indexes are typed by volunteers and are mostly right, with more errors in names and dates from other languages. Its Family Tree is one shared tree that anyone can edit, so trust a fact there only when a record is attached and you have read it.

Is Ancestry accurate?

Ancestry's record images are reliable copies of the originals, and its indexes are mostly accurate but can misread names and dates. Its member trees and suggested matches are other people's conclusions and need checking. Its DNA ethnicity estimate is a separate product and says nothing about which record belongs to your family.

Is the FamilySearch Family Tree accurate?

It varies person by person. The tree is a single shared tree that any registered user can change, so one person's careful work and another's guess can sit side by side. Open the sources attached to each fact, and change nothing in your own research until you have read the record.

How accurate is MyHeritage?

Like the other large sites, MyHeritage holds record images, indexes and member trees. The images are as good as the originals, the indexes are mostly right, and the trees and suggested matches are leads only. Check each match against the original record before accepting it.

Is Find a Grave accurate?

A photograph of a gravestone on Find a Grave is good evidence of what the stone says. The typed dates, transcriptions and family links are added by volunteers and can be wrong. Read the stone in the photograph yourself, and check the dates against a death record.

Is an index entry enough to prove an ancestor?

No. An index entry proves only that a record exists and suggests where to find it. Open the original, read every column, and check the parents' names and the dates against at least one other record. In the example, an index entry that looked right turned out to name another family.

How do I get the original record behind an index entry?

On FamilySearch and the subscription sites, open the entry and look for the image; some can be viewed only at a FamilySearch center or affiliate library. When an index gives only a register and an entry number, as many indexes of Polish records do, find the register in the archive's online scans or write to the archive that holds it.

How do I verify the accuracy of my family tree information?

Treat each fact as a claim that needs a record. Find the original behind it and check it against a second record made at another time, then note what is still unknown. Facts copied from other trees count only when you have read the record they cite.