Findagrave Is A Messy Database But It Works If You Know How To Use It
Most people treat Findagrave like a search engine and get frustrated. It is not a search engine. It is a community-maintained database of cemetery photos and transcriptions that is wildly incomplete in some areas and over-documented in others. Michigan is one of those states where the coverage is uneven. Detroit and the Upper Peninsula have solid records from dedicated contributors. Rural towns in the mitten? You will find empty pages where graves should be. I have spent years pulling records for clients and family trees. The trick is understanding what the site can and cannot do before you waste three hours going in circles. Here is how I approach it.
Uncovering The Hidden Gems Of Michigans Past A Deep Dive Into Findagravecom
The real value of Findagrave is not in the basic search box. Everyone uses that and finds the same headstones. The hidden value is in the filters, the memorial links, and the contributor maps. Start by searching for a surname, then immediately narrow by county. Michigan has 83 counties. Searching statewide returns thousands of irrelevant results. Filtering to Ingham or Kent or Mackinac cuts the noise significantly. After you run a filtered search, look at the map view. Findagrave plots memorials geographically. You can spot clusters of related families by how the pins group together. This is how I found my first connection between two branches of a family I was researching in Manistee County. The surnames were different but the cemetery plots were adjacent. That meant marriage ties I did not know existed. Another feature most people ignore is the volunteer profile page. Some contributors specialize entirely in Michigan records. A few have been photographing cemeteries in Northern Michigan for over fifteen years. Their profiles list which counties they cover. I once used a contributor named "Great Lakes Volunteer" to locate a transcribed record for a pioneer family in Alger County that appeared nowhere else. That person had photographed stones that no other source had digitized.
How To Actually Search Without Losing Your Mind
The search function has a boolean-style filter system buried under the basic search. Click the advanced options and use the date range fields. Most amateur researchers skip this entirely. They type a name and guess. That approach works for recent deaths but fails quickly when you are looking for someone who died in 1842. Enter the death year range instead of guessing the exact date. The database matches broader ranges far better than free-text name searches. Also use the memorial number system. Every record on Findagrave has a unique ID. If you find a relevant burial, note the ID number and search by that ID later. It pulls up linked family members faster than any keyword search. I keep a spreadsheet of memorial IDs for every active case. It took me six months to build the habit but it saves me probably twenty minutes per search going forward. That adds up over a career. Photo requests are another underused tool. When a headstone is worn or illegible, you can submit a photo request through the memorial page. There is no guarantee anyone will fulfill it. But in Michigan, some of the older rural cemeteries have very few photographs. I have successfully gotten volunteers to visit and snap stones that had not been photographed in over a decade. The request queue itself does not show status unless the volunteer responds. I check back every few weeks rather than expecting a timely reply.
Get the Full Details
The Problems You Will Hit And How To Work Around Them
Findagrave does not own the data. Contributing users add and edit memorials at will. I encountered a specific issue last year where a researcher had created a memorial for a Revolutionary War soldier named Thomas Whitlock in Oakland County and listed his wife as someone whose maiden name I could not verify. The memorial had thousands of views. It looked authoritative because of the war service notation and the veteran flag icon. I pulled cemetery records and birth certificates from the county clerk before I realized the Findagrave entry was mostly fabricated. The headstone did not mention the wife at all. The memorial was wrong but it dominated the search results for that surname. The workaround is to never treat a Findagrave memorial as primary source material. Always cross-reference. Check the referenced cemetery location. Verify against county probate records if possible. The Michigan State Archives has digitized many probate files that predate Findagrave coverage. I use both together. Findagrave gives me the plot location and approximate dates. The archives give me documented proof. Another problem is duplicate memorials. The same person can appear three or four times under slightly different name spellings. I search for the person once, then do a second search with variations like "Wm" for William or "Jno" for John. Old inscriptions use those abbreviations constantly. Finding the duplicate lets you merge the information but you have to do it manually. There is no bulk merge feature.
What Findagrave Will Never Give You
The site has significant gaps. It does not have burial records for all cemeteries in Michigan. Many private family plots are excluded because no volunteer has photographed them. It does not track unmarked graves. It does not include cremations where the remains were scattered rather than interred. If your ancestor was cremated in 1978 and their ashes were given to a relative, Findagrave will almost certainly have no record. The site also lacks birth records. It only has death and burial data. For living information about someone who died, you need vital records from the Michigan Department of Health and Human Services or county probate courts. Findagrave will tell you when and where someone was buried. It will not tell you who their parents were unless a contributor added that relationship. Even then, the relationship data is user-entered and unverified. For comprehensive Michigan genealogy work, you need to combine Findagrave with the Michigan Genealogical Digital Library, county register of deeds records, and Ancestry.com or FamilySearch for census data. Findagrave fills gaps in burial information but it is not a standalone research tool. Treat it as one piece of a larger puzzle rather than the answer itself.
Practical Workflow That Actually Saves Time
Here is the process I use now that has cut my research time considerably. I start with a name and known death year. I search Findagrave with the county filter already applied. I note the memorial ID and any photo details. I then search Michigan state archives for probate or will records using the same name and date. I cross-reference the cemetery location from Findagrave with actual cemetery maps from the county treasurer's office. Some counties publish burial ground inventories online. I check those next. Only after all of that do I look at contributor notes on Findagrave for additional context. That order matters because each step validates the previous one before I move forward. The whole process for a single individual typically takes forty-five minutes to an hour when records exist. If the person moved between counties or changed names, it can take longer. I have had cases where the Findagrave record pointed me toward the correct cemetery but the actual grave site had been moved during a road expansion in the 1960s. The memorial still listed the original location. I had to verify with the county historical society whether the remains had been relocated. They had. The updated information was in a local newspaper archive, not on Findagrave. This is why starting with the physical cemetery record before trusting the online memorial prevents you from following dead ends. Findagrave is a starting point. It is not the destination.
When To Move Past Findagrave Entirely
If you are researching a family line that predates 1850 in Michigan, Findagrave coverage drops off sharply. The site was founded in 1995. Most early records come from later transcriptions rather than original photographs. Pre-1850 burials in Michigan were often in unmarked or forgotten plots. Headstones rotted away or were removed. Contributors could not photograph what no longer existed. In those cases, turn to the Michigan Pioneer and Historical Collections. Published between 1874 and 1927, these volumes contain transcriptions of early cemetery records that predate Findagrave by decades. I found more confirmed burial locations for my Upper Michigan research from the Pioneer and Historical Collections than from Findagrave combined. The collections are available through the Michigan Historical Center website and some university digital libraries. They are harder to navigate but far more reliable for antebellum records. For German and Finnish immigrant communities in Michigan, the church records held by the diocesan archives or Lutheran synod archives often contain baptismal and burial entries that Findagrave simply does not have. I once traced a Finnstad family in Oscoda County through Lutheran church registers that predated any Findagrave memorial by fifty years. The church had kept meticulous ledgers. Findagrave had nothing.
Bottom line: Findagrave is useful for what it covers. It covers a lot. It covers it imperfectly. Use it alongside official records and regional archives. Do not treat it as gospel. The data is volunteer-made and volunteer-maintained. It will have errors, omissions, and occasional outright fabrications. That does not make it worthless. It makes it one tool among several that you should learn to use critically.
