FamilySearch is proud to have the world’s largest online family tree and thrilled to provide free family history experiences to millions. In order to give users the best experience possible, we are constantly working on updates and improvements to our online experience.
To keep you up to date on the latest FamilySearch experience changes, we will be listing them here chronologically. Check back often to see how your FamilySearch experience has improved!
Update: June, 24 2019—New Search Results Page
There’s a new look when you search for records on FamilySearch.org! On June 24, all FamilySearch users will see the system-wide update on the search results page. The update will help enhance the record search experience by making it faster and easier to view indexed records:
- When you select a row on the search results page, a box pops up to display the detailed record information. All the information is still there including who the source is attached to on Family tree, but now you can quickly move from record to record using the arrows on either side of the box.
- The “number of results to show” option on the search results page has increased from a maximum of 75 to 100. This also means that you can export up to 100 results at a time.
Update: May 30, 2019—Standardized Dates and Places
A system-wide update will standardize many dates and locations in the FamilySearch Family Tree. In the View Details section, these changes will appear with the contributor listed as “FamilySearch” and the date change starting on May 30, 2019. This will occur for vital and couple relationship conclusions only and will not trigger users’ Watch Ancestor notifications.
This update will help users by removing the data problem “Missing Standardized Date,” and “Missing Standardized Location”, saving the user time. It will also assist the site in providing more accurate record hints and creating more reliable data. Standardized dates will help you find ancestors more easily when you search the entire site.
This update will be applied to 15 percent of the dates and locations that are currently missing a standardized value. We will make the update only in cases where the standardized value very closely matches the value being replaced.