Searching with Wildcards in FamilySearch

Updates_FamilySearch

The Search features in FamilySearch.org are very powerful. One that is especially powerful is the ability to use Search with a character known as a wildcard.

 

 

 

 

Wildcards enable you to replace characters using wildcard characters. The wildcard characters are an asterisk (*) for multiple characters or a question mark (?) for a single character. Wildcards are useful when you can spell a surname or given name in multiple ways, for example, Thurgood or Thoroughgood. You can use up to four asterisks at a time for any surname or given name. You may also use multiple single character wildcards in a given name or surname. Note: To use a wildcard symbol in your search, in most cases, you must use at least 3 letters of the surname or given name. Here are some examples of how you can use wildcard characters:

Examples of using the single character wildcard question mark (?):

To see variations of Smith, replace Smith with Sm?th. FamilySearch will return Smeth, Smith, or even Smythe.

To see variations of Hansen, replace Hansen with Hans?n to get Hansen or Hanson. You can even try H?ns?n to get Hanson or Hansen, Hinsen or Hinson, Henson or Hensen.

Examples of using the multiple character wildcard asterisk (*):

To see variations of Tillitson, replace Tillitson with T*l*ts* to get Tillotson or Tilotson.

To see variations of Thibou, replace Thibou with Th*b* or T*b*u*. This way you can locate as many spelling variations as possible.

For unusually difficult surnames, wildcards are important when you are unsure of the spelling of the prefix of the name. You can put a wildcard (*) at the beginning of the name.  For example, for the surname Thibou, type *bou.   If you are unsure of the ending of a name, use the wildcard (*) at end such as Thib*. Then to narrow the search, enter a locality or date range. Wildcards are especially useful for European, Slavic, Native American, southern U.S., and other surnames.   Example:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 This article was written and submitted by Phil Dunn and Susan Burleson.
About the Author