Find a Grave Member for 12 Years

Today is my 12th anniversary of joining Find a Grave to add ancestor memorials, link ancestors to parents/siblings/children, post photos, post bite-sized bios, indicate which ancestors were veterans, offer suggested edits to improve memorials others have created, and use the site for cousin bait. All for free!

Above, my member profile page. Initially, I added a photo to personalize the page, then later added a "bio" listing the main ancestor branches I'm researching. Note that the profile offers the option of listing a "home page" - which, for me, is this genealogy blog. This makes it easy (and free) for cousins and surname researchers to contact me.

Another advantage of Find a Grave (owned by Ancestry) is that its memorials are included in search results on a number of major genealogy platforms, extending the reach of my ancestor memorial pages.

For convenience, I've created a number of virtual cemeteries in which I grouped listings of memorials for my paternal ancestors, my maternal ancestors, hubby's paternal ancestors, hubby's maternal ancestors, and related families. I can share the URL of these virtual cemeteries with relatives who are interested in knowing where family members were buried.

Over the years, several cousins and FAN club members (friends, associates, neighbors of my ancestors) have gotten in touch with me via Find a Grave's messaging feature. And I've connected with a couple of distant cousins because I discovered memorials they had made for our mutual ancestors and I sent them a message.

As I conduct research, I really appreciate when I find a memorial for one of my ancestors and see that someone has carefully photographed the grave, transcribed the info, and maybe even added a couple of extra pieces of info. I've also requested grave photos a few times, and had most of these requests fulfilled. I've thanked these volunteers privately, but this is my public thank-you to the many thousands of volunteers who add memorials and photos on Find a Grave.

Let me say that I entirely agree with the criticisms of Find a Grave for not preventing memorial pages from being created immediately after reports of peopling being killed in a terrible crime or disaster. There must be technical fixes to stop this, and by now, after years of criticism and outrage, it should be a top priority.

For myself, even after a dozen years, I continue to use Find a Grave every week, sometimes every day, to search for clues on memorial pages or add details to improve my ancestors' memorial pages for the sake of future generations.

Have You Checked for Fold3 Memorials?

In my presentations about Fold3, I demonstrate how to search the 39 million Memorial pages devoted to veterans and others, not just from the US but from other countries as well. (NOTE: Fold3 is owned by Ancestry, which also owns FindaGrave. It acquired the UK-based Forces War Records last year, merging it into Fold3.)

Some local and state libraries (and some FamilySearch libraries) offer free access to Fold3, which is also available with an all-access Ancestry subscription. Or you can start a free 7-day trial here. Sign in to begin your search.

Start from home page

To check for any ancestors who might be represented in the Memorials, start at the bottom of Fold3 home page, where you'll see a red banner to Search all Memorials. (Shown in image at top.)

On the search page that comes next, you can select a country or US state, a war, and filter by name of your ancestor. If you just want to get a sense of what a Memorial looks like, browse the full list and select one to view.

Lt. James Vernon Goss

I viewed the Memorial for US Army Air Corps Lt. James Vernon Goss, who died when his plane was hit by enemy fire during WWII. Here's what his Memorial looks like, including a photo of Lt. Goss in his uniform. Details of his service are in the timeline at left.

I labeled a source link at right, which takes you to the Find a Grave page of Lt. Goss. 

Also on the right is a section called "Partners" where a nonprofit is listed: Stories Behind the Stars, which encourages volunteers to research and write the stories of military men and women who died in the service of their country. I've bookmarked this site to explore later!

Getting in touch

The "owner" of Lt. Goss's Memorial, below the Partners heading, is a Fold3 member with the user name HideandSeek69. 

She added the photo and info on the page, and she is the only person authorized to add to the Memorial. 

Since her user name is blue, it's clickable. Go ahead and click!

Her member page shows all her contributions to Fold3. Over the years, she has written brief bios for dozens of service members and posted them on Fold3, with photos when available. 

Now notice the red "contact me" button that's located below the member's name and start date. This is how you can get in touch with a member if you recognize one of the service members and want to exchange info. 

Check for your ancestors

Follow this process to check Fold3 for any Memorials honoring your ancestors. Review the life events and photos posted, review any photos, and pay attention to the "owner" or authorized contributors so you can try to get in touch. 

A Fold3 Memorial page might serve as cousin bait, as well as a very good way to memorialize an ancestor fallen in the line of duty.

Go Ahead and Save My Stuff to Your Tree

Yes, I've spent 24 years researching ancestors on my family tree and my husband's family tree. Yes, I've spent thousands of dollars ordering vital records from both sides of the Atlantic. 

Yes, I want you to take anything and everything connected to my public family trees and add that stuff to your own tree if we have mutual ancestors. That's why I shared all those things publicly. 

Genealogical clues and cousin bait on my trees

These items are great genealogical clues, and they're also great cousin bait. So go ahead and save to your tree! 

As shown above, 20 members of Ancestry have saved the unique handwritten version of family history jotted down by my husband's grandfather, Brice Larimer McClure (1878-1970). These people were his relatives, and his notes have been fantastic clues for further investigation. Some of the members who saved this to their family tree have been in touch with me to exchange additional information, including a few who are DNA matches with my husband. 

Cousin bait, not just genealogical clues. 

LOCKSS vs "my tree"

I share widely because of LOCKSS: lots of copies keep stuff safe for today and tomorrow. 

I recognize that some people are unhappy when their trees are copied and their materials used without attribution. They've done a lot of work and they would at least like to be recognized for that work when someone else copies from a public tree. Although I certainly understand and respect this perspective, it's not my approach.

When I started on my genealogy journey in 1998, many people kindly shared info with me. They gave me a head-start. Now I'm paying it forward and looking ahead with LOCKSS. 

If I don't want something copied (such as personal photos), I don't post that stuff these days. On the family photos I do post online, I've been adding the name of the person, dates if known, and then "Courtesy ___ Family" to clarify the source (as on this photo of my great uncle, which I posted on WikiTree).

The more people who have ancestor names and supporting materials on their trees, the less likely these ancestors will be forgotten in the decades to come. I want my research to be available long after the distant day when I join my ancestors, not just in the hands of my family but more widely. 

This is why I post trees on multiple sites (WikiTree, Ancestry, MyHeritage, and so on) and add to the FamilySearch tree. I also have heirs on both sides of the tree who will become custodians of my genealogy collection in the future.

What will happen to your family history? Are you taking steps now to keep your genealogy, stories, and materials safe in the years to come?

-

For ideas on how to plan ahead, please see my popular book, Planning a Future for Your Family's Past, available from AmericanAncestors.org and from Amazon US/Canada/UK/Europe. If you're on Kindle Unltd, you can read the ebook for free!

Great Cousin Bait: Ancestor Landing Pages

It's been nine years since I first created ancestor landing pages along the top of my genealogy blog, an idea I got from Caroline M. Pointer. 

I use these landing pages to summarize what I've learned about each ancestor or ancestral family, including images plus links to specific blog posts I've written about that ancestor or family. As I discover more details and write new posts, I add the links to the corresponding ancestor landing pages.

Just as important, ancestor landing pages are incredible cousin bait! When relatives search online for one of their ancestors, they often see my ancestor landing pages in their search results. With a click, they land on the landing page, read about the ancestor(s), and can connect with me via my blog's "contact me" widget. 

Thanks to landing pages, I've heard from dozens of farflung cousins who have landed on my landing pages. What a joy to get acquainted or reacquanted and exchange stories and photos!

By far the most popular ancestor landing page is the one devoted to my husband's McClure ancestors from Donegal. Even when most readers don't turn out to be related to this branch of the McClure family tree, they can get fresh ideas for researching their McClure ancestors by checking the resource links on this landing page or getting in touch with me.

Other genealogy bloggers have created different formats for their ancestor landing pages. For instance, Randy Seaver calls his "Randy's Genealogy," with links to his family trees plus more. Gail Dever calls hers "My Ancestors' Stories," linking to stories she has written about particular ancestors. Sandra Sue Pittman McPeak labels each landing page by surname. 

Different formats, same goal: to tell the ancestors' stories AND to serve as cousin bait!

"Landed" is the week 7 genealogy prompt in Amy Johnson Crow's 2022 edition of #52 Ancestors.

Two More Reasons to Create Virtual Cemeteries on FindaGrave

So far, I've created five virtual cemeteries on the free, worldwide, Ancestry-owned website FindaGrave.com. 

See my detailed post here about how and why to create a virtual cemetery on FindaGrave.

I've named each virtual cemetery and for some, I've added a brief description ("Descendants of Solomon Elias Burk and..."). Others will get a description very soon.

Names and descriptions help relatives and researchers who want to browse these memorials.

Now I want to point out two more reasons--two very good reasons!--for creating a virtual cemetery on FindaGrave.

Reason 1: Quickly go to a memorial 

Often, I access an ancestor's FindaGrave by clicking a link on my Ancestry family tree. 

If I'm not working on my Ancestry tree at the moment, I just go to my listing of virtual cemeteries on FindaGrave and locate a particular memorial that way. Fast and easy! 

I'm accessing many more of my memorials these days as I compose and post brief, bite-sized bios on FindaGrave and other websites. How easy it is to simply click on my virtual cemetery, see a memorial, and note which still need bite-sized bios.

Reason 2: Return to a memorial to see what's new

Just today I returned to a memorial I haven't accessed in months...and discovered that someone left a flower two weeks ago! In fact, looking at linked memorials, I saw this person left a flower on more than one of my ancestor's pages. Cousin bait?!

I immediately checked that person's FindaGrave profile page, found no listing of surnames, and sent a polite message (saying thank you for leaving a flower, and please let me know whether you're related to my ancestor). Fingers crossed that perhaps this is a distant cousin or someone in the FAN Club (friends, associates, neighbors).

Note I don't manage every one of my ancestor memorials (nor all of my hubby's ancestor memorials). As long as they're in good hands, I'm usually content to simply submit edits, including bite-sized bios. Other people also submit edits to these memorials on occasion (Census data, maiden names, etc). 

That's why it's always worthwhile checking back to see what's new. With my virtual cemeteries, I'm only a click away from any ancestor memorial.

Anatomy of a Bite-Sized Ancestor Bio

For the past year, I've been writing bite-sized biographies of ancestors to share publicly on My Heritage, WikiTree, Find a Grave, Family Search, and other genealogy sites. Apart from listing basic facts (birth, marriage, death), I also like to provide context and family connections, making each ancestor three-dimensional. 

Above is an excerpt of a bite-sized bio I wrote for my paternal grandmother, Henrietta Mahler Burk (1881-1954), and posted on her Find a Grave memorial page. Previously, I had posted a photo of her gravestone, as well as a photo showing her in 1937 (not visible in this excerpt). Also, I linked Henrietta to her parents and siblings, her husband, and one of her children on Find a Grave.*

Headline summarizes the story

My preference is to add a headline summarizing the highlights of each bio. In the case of my paternal grandmother, the headline shows she was an immigrant ancestor, mother of four, grandmother of five. 

The bio mentions her work as a stenographer before her marriage, but I didn't list a career in the headline because she didn't hold that occupation for very long. If Henrietta had been known for a particular skill or talent (needlework, music, rocket science, etc.) I would have noted it in the story and the headline. 

Cradle to grave

My bite-sized bio includes the ancestor's birth date, place, and parents, plus siblings where it's natural to weave in that info. Exact dates are shown for key facts (BMD for instance).

Sometimes there are special circumstances to note. I can't prove Henrietta was born in Riga, even though her husband's naturalization petition lists that as her birth place. Knowing that many immigrants in my family took the easy way out when asked about home town and named a nearby city instead of the tiny town where they were actually born, I used the wording "in or near." 

Next, my bio follows the major moves in Henrietta's life--literally a number of moves between her birth place, her residences, and then back and forth to Canada with her husband and children. Covering the key instances in her husband's life that affected her life creates a bit of overlap between the two ancestor bios, but that's OK. 

Sources noted (briefly)

To avoid interrupting the narrative flow of the bio, I note sources briefly in brackets. This signals to readers that the bio is based on solid sources beyond "family lore." Now or in the future, people can retrace my research with the aid of these brief sources. 

I also posted a version of this bio on WikiTree, Family Search, and My Heritage. This keeps Henrietta "alive" in multiple places online, and it also serves as cousin bait! 

--

* Ancestry recently changed its terms of use (August, 2021). The changes mean that when we upload a photo or other content, we are giving Ancestry "a perpetual, sublicensable, worldwide, non-revocable, royalty-free license to host, store, copy, publish, distribute, provide access to, create derivative works of, and otherwise use such User Provided Content..." 

This applies across Ancestry-owned platforms, such as Find a Grave. Read more about the changes at Judy Russell's blog post here. I don't agree with what Ancestry is doing, and am currently deleting many (but not all) family photos from my public trees. Please consider carefully before posting to these sites.

There's more about bite-sized bios and other fun projects in my popular webinar or live presentation, "Bring Family History Alive in Bite-Sized Projects."

DNA + Trees = Powerful Cousin Bait

Name your family tree so DNA matches can get a glimpse of names and places

 

Fishing in many ponds, my DNA results are on Ancestry, MyHeritage, FamilyTree DNA, GedMatch, and 23 and Me. My husband's DNA results are on Ancestry, MyHeritage, FamilyTree DNA, GedMatch, and LivingDNA.

To add to the power of DNA matching, I've uploaded at least a basic family tree where trees are allowed. This enhances DNA as cousin bait, allowing matches to investigate our possible connections. 

Also, as shown above, I include surnames in the name of the tree, along with specific surnames and locations in the tree description. I want to encourage DNA matches (and researchers) to explore further and envision possible connections in different branches. 

In my view, a name like "Frank's Tree" or "Family History" doesn't convey anything about the tree or the ancestors. 

Why not take the opportunity to boost the combined power of DNA and trees by providing an informative tree name where you have that opportunity? The tree name is another genealogical clue!

--

"DNA" is the #52Ancestors prompt for this week, and the theme of this month's Genealogy Blog Party.

Sifting Through Hints for Cousin Bait

Use surname filtering to focus on cousin bait

If you're looking for cousin bait, you have to focus your attention on the most productive possibilities when sifting through family-tree hints on Ancestry.

At left, the hint summary for my husband's family tree on Ancestry. There are 3,200 people on this tree, so it's not surprising that I have so many total hints.

Stories and photos are often very good cousin bait, especially if you filter the hints by surname as you focus on specific ancestral lines. Then you can look at the contributor's profile and tree (if public) to see how he or she fits into your family tree. (I'm not going to talk about DNA or ThruLines in this post--topics for another time!)

Stories as Cousin Bait

In this case, I looked at all 21 of the "stories" to see what they are, who posted them, and how many were personal vs. transcribed documents or records. Most could be seen without downloading any files (which I won't do unless I know the person, just in case).

Many of the stories were summaries of family histories with footnotes leading to county histories or other books. Two were transcriptions of will/probate materials for distant ancestors. All useful in my research, but not specifically cousin bait, although of course I checked to see how the contributors might fit into the family tree.

A good number of these 21 stories were transcriptions of oral history from someone who actually knew one of my husband's ancestors! Great cousin bait. I've now invited that contributor to see my public family tree, and he has invited me to see his public family tree. There is a distant cousin connection here, and the oral history posted as stories served as effective cousin bait to reel me in.

Photos as Cousin Bait

Ineffective as cousin bait

My favorite cousin bait (to leave as bait or to follow as bait) is a personal photo of an ancestor.

With 627 photo hints to sift through, I narrowed the focus by specifying a particular surname for searching photo hints.

Within the photo hints for McClure were dozens of flags, patriotic images, DNA symbols, and other non-personal images.

These are NOT effective cousin bait. Folks like to use such images to tag certain categories of ancestors, but they don't work well for cousin bait.

On the other hand, the photo shown below is top-notch cousin bait I discovered when searching photo hints for Larimer, another of my husband's ancestral surnames.

Effective cousin bait: A personal photo with a title

Not only is it a real photo, it has a title that indicates who and what the photo is about (I masked some info for privacy). I've confirmed that the person who posted the photo is actually a cousin. He has meticulously researched his branch of the tree and we are now guests on each other's family trees, sharing info about the Larimer line.

For all the other record hints, I will filter by surname and work down the list. I don't generally check family tree hints this way, by the way. Instead, I look at them when I'm researching a particular ancestor.

Have fun with #CousinBait! 

Curating Faces for the Family Tree

Yesterday's post was about how personalizing family trees with photos of ancestors can be wonderful cousin bait.

Putting faces on the family tree also preserves those images for future generations to see.

It's a process of curation...and it puts a face to the name.

Which photo to post?

My goal is to have at least one clear face for each ancestor in my husband's direct line and my direct line. If possible, I want that main photo to be of the ancestor as an adult.

Above are the photos I posted on MyHeritage of my father-in-law, Edgar James Wood (1903-1986), and mother-in-law, Marian Jane McClure Wood (1909-1983).

I chose good, clear photos of my in-laws in their mid-50s, recognizable to anyone who might have known them even in their later years.

Obviously there will be no photos when I get back beyond the mid-1800s, but occasionally I have something else suitable (such as the woodcut portrait of my husband's great-great-granddaddy Benjamin McClure from an 1880s newspaper).

I promise, no images of flags or ships or DNA! Update: Dara asked why no DNA image, since it's a quick way to see who's a match when we look at our own family trees. IMHO, a DNA image isn't good cousin bait and often there are too many DNA images that come up in "hints." I'm posting photos of deceased ancestors, using them specifically as cousin bait.

Captioning on the photo

I cropped each photo to focus on the face. Then I put a caption on the image. As shown above, the captions are:

Edgar James Wood, courtesy Wood family

Marian Jane McClure Wood, courtesy Wood family

No matter where these photos get copied, and no matter how many years have passed since being posted for the first time, the faces will always be identified (along with the source).

Once I have the photos cropped and captioned, I can upload to all of my trees (Ancestry, Family Search, MyHeritage, and Find My Past).

Thanks to the pandemic, I have the time to systematically climb each family tree, adding a photo to key ancestors on multiple genealogy websites.

Personalized Family Trees Are Great Cousin Bait

Family photos as cousin bait on FamilySearch.org

Ancestor photos are terrific cousin bait on family trees!

Recently, I contacted someone who had posted a photo of a descendant of my husband's great-great-granddaddy, Benjamin McClure. She immediately wrote back to confirm the relationship! We are excited about exchanging other photos and genealogical details. That's why I'm taking the time to personalize all my trees with photos on key ancestors. It's simple, it's easy, so I'm going for it.

Photos Catch the Eye

The handful of photos I've posted on my family trees on Family Search (above), Ancestry, and MyHeritage are designed to attract the eye of anyone researching these ancestors. Instead of a generic silhouette, these ancestors have a face!

I'm in the process of adding some photos to FindMyPast as well, since many of my husband's ancestors (Wood, McClure, Larimer, and more) were from England and Northern Ireland.

The faces personalize family trees and encourage cousins to get in touch. I'm including brief photo captions as well for a bit of added personalization. My photo caption for Marian Jane McClure simply provides her birth/death years and says she is the daughter of Brice Larimer McClure and Floyda Mabel Steiner McClure.

Of course, for privacy reasons, any photos and captions I post do not include faces or names of living people.
Watch Those Ancestors

Click the star to "watch" an ancestor on FamilySearch

On Family Search, I've clicked the star to "watch" key ancestors (see purple oval above). That means I'll get a message if and when anybody else makes any change to these ancestors. Usually I'm notified by email about a message.

But I can also log in and look for a dot above the "messages" link (see purple arrow). If a dot appears there, I'll know there's been a change to a "watched" ancestor OR a possible cousin is getting in touch!

Happy cousin hunting!

Thank You for Sharing

Handwritten note by Brice Larimer McClure, naming his ancestors

My husband's grandfather, Brice Larimer McClure (1878-1970), left several scraps of paper with notes about his family tree.

As shown above left, one of these scraps begins with the sentence: "I am Brice Larimer McClure, a son of . . . " He then proceeds to name his grandparents and great-grandparents and back as far as he knows.

Are the details all correct? Maybe yes, maybe no. This note was written from memory, I suspect, reflecting what Brice was told about his ancestors as he was growing up. Even if the names and dates aren't entirely accurate, they gave me good ideas for further research.

This first-person account of McClure and Larimer genealogy was so unique, I couldn't keep it to myself. I decided to share it on a public family tree on Ancestry back in 2011. As shown above right, I attached it to eight ancestors whose names appear on the note.

Since then, a total of 99 other Ancestry members have saved it to their family trees. This is far more people than have ever saved any other single photo or document from my public trees to their trees.

By sharing, I hope to give others clues for researching names, dates, and relationships in their trees, just as I've learned from clues in unique documents and photos shared by people who attached them to their public family trees.

Thank you, everyone, for sharing. Please go ahead and use any unique photos and documents you find on my public trees to jump-start your own research. And remember--unique items like this can be excellent cousin bait! 

Saturday Night Genealogy Fun: Surname Word-Cloud

Randy Seaver's challenge this week is to make a Surname Christmas Tree. A fun idea--one that I adapted for my own genealogical situation.

There are more than 80 surnames in my Jewish family tree. So I made a word-cloud in the shape of a heart rather than a tree.

Following Randy's how-to explanation, I first listed the names in a Word document and then sorted alphabetically, on the theory that a word-cloud generator would randomly assign names to different places in the shape.

Next, I selected one of the free word-cloud generation sites, chose the color theme, chose the shape (a heart, loosely interpreted as you can see), and set the gap between names at 2 spaces.

Then I uploaded my names, looked at the result, and played with a few of the settings (the font, for instance) until I liked the way the whole thing looked.

Finally, I downloaded the word-cloud as a .jpg and here it is!

Thanks, Randy, for this excellent holiday idea.

P.S.: I'm also listing all the surnames here as cousin bait:

ADELMAN

ASH

BARTH

BERGER

BERK

BERKMAN

BIRK

BLAUMAN

BLOCK

BOURSTEIN

BROWNSTEIN

BURK

BURKE

CAPLAN

CASSON

CHAZAN

DIAMOND

EMERMAN

ETSCHEL

EZRATI

FARBER

FARKAS

FESTINGER

GAFFIN

GARFIELD

GELBMAN

GENNIS

GOLDBERG

GOLDMAN

GOODFRIEND

GROSSMAN

GUTFRIED

HARRIS

HARTFIELD

HORWICH

JACOBS

KATZ

KLEIN

KOBLER

KRAUS

KUBA

KUNSTLER

LANG

LEBOWITZ

LETHERMAN

LEVINE

LEVY

LIPSON

LURIA

MAHLER

MANDEL

MANDEL

MARKELL

MARKS

MITAV

PITLER

POMPIONSKY

RETHY

RIGOROFSKY

ROSEN

ROTH

SALKOWITZ

SCHWARTZ

SEGAL

SHUHAM

SIMON

SIMONOWITZ

SMITH

SNYDERMAN

SOLOMON

STEINBERGER

STERN

VINOKUR

VOLK

WAJMAN

WALDMAN

WEIMAN

WEISS

WHITELAW

WIRTSCHAFTER

WOLF

ZUDECK 

-->

Steal My Family Photos--Please

Woodcut of hubby's ancestor, "stolen" by 13 other people for their family trees!

Dear cousins and possible cousins:

"Steal my family photos--please!"

And post them on your family trees so I can connect with you. Cousin bait!

Family photo of Tillie Rose Jacobs Mahler, "stolen" by others for their family trees!

If you save my publicly-posted family photos to your tree (whether it's hubby's 2d great-grandpa Benjamin McClure or my great-grandma Tillie Rose Jacobs Mahler), I can click on your profile photo, see whether we are a DNA match, look at your tree, and find out whether (and how) we're related.

Sure, some people who are not related have mistakenly claimed my photos of dead ancestors for their trees. Either I'll send a gentle private message questioning the connection or I'll post a politely-worded public comment on the photo on that tree.

You don't need my permission to "steal" a publicly-posted photo for your tree. And I don't expect you to ask permission.*

Please, just go ahead and steal my family photos . . . and lead me to our cousin connection!

This week's #52Ancestors prompt is "Thief."

*John Tew recently wrote that while he agrees with me, he also would like those who "borrow" his photos to give credit to his grandmother who so carefully and thoughtfully preserved these photos for future generations to enjoy. A lovely idea...and I do hope some of his distant relatives will do that. I'm just happy anyone saves any of my photos so I can follow the bread crumbs and find our cousin connection.

#CousinBait #Genealogy #FamilyHistory

McClure Cousin Bait on FamilySearch

Cousin Bait on Family Search 

I married my husband for his ancestors!

His many ancestors left photos, genealogical paperwork, diaries, newspaper clippings, and more. Lucky me!

Thanks to cousin L, the Wood family historian, we know a great deal about the Wood side of the family. My late father-in-law Edgar James Wood (1903-1986) had five Mayflower ancestors.

Cousin Bait on Family Search

So far, we don't have connections with too many McClure cousins--those related to ancestors of my late mother-in-law, Marian Jane McClure Wood (1909-1983).

Now I'm adding cousin bait to my husband's McClure ancestors on the Family Search family tree. See the screen shot above of some McClure ancestors and how I've begun personalizing their profiles on Family Search.

Personal Photos = Cousin Bait

Because Family Search has only one collaborative tree, any researcher who comes across these personal photos will see me as the source.

I'm easy to contact via Family Search (my email contact is up to date). And since Family Search is free, I know a lot of people use it for research and documenting family trees.

Sometime soon, I hope McClure cousins will get in touch after noticing the personal photos I posted on ancestor profiles.

Watchlist of Ancestors

Also, I'm "watching" other McClure and Larimer ancestors to see whether other researchers post any personal photos or other personalized details. Then I can check the source and contact those people, offering to share info.

Here's a watchlist of 7 people I'm watching so far on Family Search. I take a look every so often for any changes or photos posted to these ancestors, hoping that I'll connect with a few more McClure cousins.




--

Thanks to Amy Johnson Crow for this #52 Ancestors prompt of "cousins" for week 38.

Cousin Bait Leads to Discovery of Another Family History Book

My husband's Larimer family intermarried with members of the Work, Short, and McKibbin families in America.

One reason we know this is from the detailed Larimer family history book researched by John Clarence Work (1875-1962) and his father, Aaron Work (1837-1924). The book suggests that there were ties among the families back in the original home towns, before these ancestors crossed the Atlantic Ocean.

Believing that researching siblings, cousins, and in-laws can lead to more genealogical breakthroughs, I've been looking at the Work family connections with the Larimer family. And, of course, I've been blogging about the Work family.

My cousin bait blog posts have attracted a couple of inquiries--including one distant Work cousin who knew something I didn't about John Clarence Work.

Larimer Family History

A photocopy of the Larimer family history survived in my husband's family, along with my in-laws' hand-written corrections of spelling and dates for some of the people mentioned in the book. I've used the book and the corrections as a starting point for researching my husband's family, grateful for the clues and comments.

John Clarence Work and his father not only traced the Larimer family tree, they also compiled the names and brief bios of descendants of the original Larimer immigrant who left Northern Ireland about 1740 to make a new life in America. Happily for any Larimer descendant, the Larimer Family History is available for free, in its entirety, on FamilySearch (follow this direct link to the book).

As it happens, John Clarence Work was in touch with my late mother- and father-in-law during the 1950s, asking about their lives and the names/dates of their children (including my hubby). So I know how much effort they put into this family history. What I didn't know is that this was not the only family history done by John Clarence Work.

Work Family History

The Work cousin who contacted me via my blog said he was in touch with the Fairfield District Library in Lancaster, Ohio, near where the Work family once lived. The librarian kindly scanned and sent to him several pages from a book about Work family history, cowritten by John Clarence Work with his niece, Rhoda Fisher Work. That gave me an idea...

I searched the Family Search catalog for books by John Clarence Work. And I discovered that the Work Family History, like the Larimer Family History, is also available for free, in its entirety, on FamilySearch (follow this direct link to the book). What a treasure trove of genealogical clues!

One lesson learned from this experience is: If someone in the family wrote a family history, check to see whether that person wrote a second or third family history. Check the local library and historical/genealogical society in the area where these ancestors lived, and check Family Search as well.

Thank you to the Work cousin who contacted me and shared what he'd learned about the Work family history book!

New Clues in Genetic Genealogy Challenge

My maternal haplogroup is V7A

Genetic genealogy is by far my biggest challenge (challenge is this week's #52Ancestors prompt).

Despite 21 years of tracing the paper trail of family history, I haven't fully exploited the clues provided by DNA testing. But breakthroughs may be on the horizon.

Multiple DNA Tests and Sites

I am SO lucky. Having a twin sister really comes in handy!*

Between us, we've taken 4 different tests and uploaded results to the spectrum of popular genealogy DNA sites. (Neither she nor I use our full names on DNA test sites, for privacy reasons.)

Her results confirm that our maternal haplogroup is V7A and, as we already know from traditional genealogy evidence, our origins are Eastern European. Our ancestors came from Hungary (including parts that are currently in Ukraine), Lithuania, and Latvia.

More Cousins, More Colors

To make full use of DNA Painter and other tools, I need to be able to identify matches from specific parts of my family tree.

Recently I recognized names on Sis's list of close DNA matches that are not on any other site where our results are posted. These matches fill key gaps in my genetic genealogy knowledge. Now I can color-code more ancestors more accurately as I use DNA to determine who fits where in the family tree.

Just as important, Sis's matches are giving me an incredible opportunity to reach out personally to paternal 2d cousins I knew we had but wasn't able to locate using conventional means. They only tested on one site--a site Sis used, happily for us.

DNA is good cousin bait--and I'm taking their bait. Can't have too many cousins!

*Fish in Different DNA Ponds

You can always "fish for DNA matches in different ponds" if you wish (whether you have a twin or not). Take DNA tests from different sites and/or upload your results to multiple sites. So many excellent DNA guides are available that I won't even attempt to say more, since I'm far from an expert on genetic genealogy.

It's a good idea to list surnames and origins on each site (and/or upload at least a basic family tree) so potential matches can get a sense of where the match might be. To protect privacy, I don't ever show living people on my trees.

Remember that as of now, 23AndMe and Ancestry don't allow uploads from other testing sites. That's why Sis and I tested with multiple sites, to fish in as many ponds as possible even when uploads aren't an option.

Unique Ancestor Images on Public Trees Are Cousin Bait

83 people have saved Brice Larimer McClure's
note about his ancestry, which I originally posted.

Brice Larimer McClure (1878-1970), hubby's long-lived granddaddy, wrote a few notes about his ancestry on tiny slips of paper. Years ago, I scanned those notes and uploaded them to my public Ancestry tree, along with a full transcription. You can see the beginning of the transcription above ("I am Brice McClure a Son of Margaret Larimer McCure and Wm. McClure...").

Every year or so, I return to images I originally posted, and check to see who has saved each one. By now, more than 80 people have saved this unique, one-of-a-kind note, which I attached to 8 people in my husband's public family tree.

Clicking on the tree of each person who saved one of my unique images shows me where Brice or Brice's ancestors might fit into that tree.

It doesn't matter whether I believe the other person's tree to be accurate or not. My objective is to see who's on the tree and how these people might be related to my husband. Potential clues, in other words, to possible cousins.

Occasionally, I'm able to identify a solid cousin possibility. I double-check what's on the other person's tree and reexamine my tree's connection to that ancestor. Then I send a message about this possible cousin connection and offer to exchange additional genealogical info. And, thankfully, a few people have responded and continued to correspond about mutual research interests!

I know there are more cousins out there to be found via family trees and paper trails (DNA is not my primary focus at this point). If someone has saved a unique image or note that I originally uploaded, it's worth a few minutes of my time to check that person's tree.

Those unique images are cousin bait!

Ancestor Landing Pages: Summaries and Cousin Bait

As shown above, my genealogy blog includes tabs for a series of "landing pages," mostly devoted to summarizing what I know about key ancestors in my family tree and hubby's family tree.

I established the first of these ancestor landing pages more than 6 years ago, and expanded until now I have 14 such landing pages. Each tells the story, in brief, of an ancestral couple or family. When I blog about one of those ancestors or families, I update the landing page with a link to the newest post. This enables anyone who searches for that surname to see, at a glance, what I've learned about that family and what I'm still learning or wondering about.

In addition, I have a landing page devoted to hubby's Mayflower ancestors. The remaining 3 landing pages include links to free genealogy resources, sample templates for family history, and my genealogy presentations.

McClure, Larimer, and Schwartz

By page views, the three most popular ancestor landing pages are:

• Halbert McClure and family from Donegal. This is the Scots-Irish ancestor of my husband who had enough money to sail, with many members of his family, from the north of Ireland to Philadelphia. The family then walked to Virginia to buy farm land. 
• Robert & Mary Larimer. According to my husband's grandfather, family lore has it that Robert Larimer was sent from the North of Ireland to America to make his way in the world. Alas, he was shipwrecked en route and forced to work off the cost of his rescue. 
• Schwartz family from Ungvar. This is my maternal grandfather's family. Born and raised in what is now Uzhorod, Ukraine, Grandpa Teddy was the first in his family to leave for America. Soon he sent for an older brother and together, they saved their nickels and sent for a baby sister.

Cousin Bait

My landing pages are attracting thousands of views, so I know people are finding them via online search. Sometimes people even leave me a comment or write me c/o my blog to discuss possible family connections.

More than once, a cousin I didn't know I had (or couldn't find) has landed on my blog and gotten in touch with me. Genealogy blogs are excellent cousin bait, and ancestor landing pages increase the odds of being found via online searches.

DNA Plus Trees Equals Cousin Bait

MyHeritage profile is temporarily empty, soon to be filled!

This week's #52Ancestors prompt is DNA. For years, my main genealogy site has been Ancestry, in part because of the size of its DNA base and because my multiple, ever-growing family trees are all housed there. Thousands of ancestors, counting his and her trees, some with thousands of hints to be examined.

My DNA and hubby's DNA also appear on Gedmatch, because of the tools available for analysis and because we can fish for matches among all people using that site, regardless of where they originally tested.

I created a basic tree for him and for me on Gedmatch, and also listed major surnames so people browsing matches can quickly see how we might match, as cousin bait.

New Site for DNA Cousin Bait

Now I admit, I'm often frustrated by how many Ancestry DNA matches have no family tree, or only a few names, or a private tree only.

So now that I just subscribed to MyHeritage, to more intensively research my husband's British, Irish, and Scottish ancestry, I'm transferring my DNA and hubby's DNA there too.

With the new site, I need to complete my profile (sadly empty, as shown above) and plant my family trees as cousin bait. I began with a photo and basics...

More Hints Too

Since I sync my Ancestry trees with my RootsMagic 7 software, I will be able to upload an updated Gedcom tree for myself and my hubby onto MyHeritage with little effort. Thanks to the RootsMagic Users group on Facebook, I learned how to export a Gedcom with living people marked as private.

Now I can take advantage of both Ancestry and MyHeritage hints through RootsMagic, as shown here.

Make it easy for DNA matches to see the family tree(s), and we just might get better answers to our notes or possibly hear from matches who take the initiative to reach out to us! Cousin bait.

Genealogy Blog as Cousin Bait

Hubby's ancestor Benjamin McClure was a 19th-century civic leader in Wabash, Indiana

Last Sunday, I watched a very interesting live webinar by Tammy Hepps, "Technology for Cousin Bait That Works." Tammy's main point: Cousins and genealogy researchers can't find us if our content (written and/or illustration) doesn't appear in the first page or two of search results.

And lucky for me, Elizabeth O'Neal's Genealogy Blog Party this month is all about tuning up our blogs. She has links to lots of ways to test blogs, analyze search rankings, and improve the look and content of our blogs.

Here's what I did to I tune up my blog as cousin bait.

Search Like a Cousin

What, exactly, will attract a cousin? One 2d cousin found my blog because I had written about a synagogue where our ancestors were married. When she did an online search to learn more about that synagogue, my blog post ranked high in the results. She clicked to read more...and, happily for me and my family, she contacted me! One of my friends occasionally receives inquiries from people who find her blog because she posted about an orphanage where her ancestors were placed.

To search like a cousin, think like a cousin. Try searches using key words that might attract our cousins, including surnames and related key words. So far, I have been pleased with the results rankings.

Blogger already allows me to assign "labels" (key words) for each blog entry (such as a surname or a topic). I also list key words in my blog's description, and have changed these over time. Since I can't always predict what a cousin will look for, I go beyond surnames to include religious institutions, places, and so forth.

Surnames and Easy Contact

You can see the main surnames I'm researching along the right side of my blog.  Plus along the top of my blog, I have a series of "landing pages" for main surnames and the stories of those ancestors or families. I want these to be visible and I want cousins to know I welcome contact, as Tammy suggested.

In the past couple of years, I added a contact gadget just above the surname listing. Currently, I receive 1-2 inquiries every month. Not everyone who uses the contact gadget turns out to be a cousin, but I still appreciate that they make the effort to get in touch.

Blog Tune Up: Subheads and Captions

Yet another place to insert key words, Tammy noted, is in subheads of blog posts. Who knew? So now I'm tuning up my blog to add subheads, an easy tweak that might boost a post's rankings in search results when cousins go looking for their FAN club. Also, I'm going back to writing captions that include surnames and other key words, such as shown at top.

Finally, blog content must look good on mobile devices, an important criterion used by search engines. Mine looks fine on a small screen, according to the preview in my Blogger dashboard.

If you're reading this on your phone or pad, doesn't Benjamin McClure (1812-1896) look like a determined pioneer farmer and respectable civic leader?!