Tips – Page 2 – GenealogyAtHeart.com

Part 4: Helpful Hoosiers, Elusive Records, and One Good Clerk

This is a continuing series on my recent adventures to acquire documents for dual-citizenship. You can read earlier posts here – here – and here.

We were up bright and early on Wednesday, ready to track down a divorce record at the Porter County, Indiana courthouse before they even opened.

Here’s another tip for researchers working in Indiana: be prepared to feel like a threat. Most facilities are swarming with armed officers who clearly believe they’re guarding nuclear codes rather than 19th-century paperwork. And no, you can’t bring your cell phone in. Doesn’t matter if you need it to pay. Doesn’t matter if you’re old and holding a manila folder. It’s Wild West rules. Don’t bother asking for an exception. I warned you.

As expected, they couldn’t locate the record.

I thanked them for the stack they had mailed me two years ago, minus the final dissolution of marriage I actually needed certified. Last time, it took them three months to find anything, and they charged me $50.00, a dollar per page, even though they’d made five copies of the same ten pages. No, it wasn’t a juicy divorce. Just sloppy duplication.

This time, I showed them the exact document I needed. I was told I’d hear back once they found it.

Here we go again.

One Clerk, One Win

On to the Porter County Health Department, where I entered a bit too early for some folks’ comfort. While I stood silently at the counter, I overheard one clerk complaining about “letting people in before we open.” (Hi, yes. That would be me.)

Thankfully, another clerk came to the rescue. She was efficient, kind, and within five minutes, I had the certified record I needed.

I mentioned the nightmare from the day before in Gary, and she replied with a sigh: “I couldn’t even get my own birth certificate from them. I had to go through the state.”

So maybe I was lucky after all.

A Church with a Lock and a Secretary with a Key

We drove back to Lake County to revisit the church that had been closed the day before. Again, the door was locked and the secretary spoke to us through it. When I explained what I needed, she let us in and quickly found the baptism and marriage books.

She couldn’t locate the names but from across the desk, upside down, I spotted them and pointed them out. She allowed me to take a photo of the entries, but only after covering up the rest of the page. I didn’t bother mentioning that many dioceses have digitized records entirely, so full-page images are already online.

She couldn’t issue the certificates, though as there was no priest available, and wouldn’t be one “for a while.” The plan was to mail them when a priest showed up.

Which, given how things were going, might be never.

Cemetery Software and the Mystery of the Missing Priest

Next, we made a quick stop at the cemetery, where I hadn’t planned to clean any graves, but found myself wiping down markers anyway. I was there to get an updated cemetery record for the family plot. The version I had was from 2001, and a new family member had since been buried.

They had upgraded to new cemetery software. Unfortunately, no one knew how to print a basic update using it.

So one employee simply handwrote the new information and told me to submit it alongside the old printout. (Ah, technology!)

Déjà Vu with a Twist

While there, I got a call from Porter County. They told me to check my email to confirm they’d found the divorce record.

Cue near-heart attack.

I checked: no email. Nothing in spam. I called back, no voicemail. I called again. The clerk laughed and said, “Oh, I didn’t send it yet.”

I told her we were already on our way.

One Archivist’s Righteous Indignation

And then the Chicago Archdiocese archivist called.

She wanted me to know firmly that my grandparents had not married at St. Salomea’s and that she would not be refunding my money.

I hadn’t asked for a refund.

She was clearly annoyed that I had requested a church record despite already having a civil marriage certificate number. I explained that the county couldn’t find the record.

Her response? “They should find it.” Right – shoulda – woulda – coulda!

As if that’s something I can make happen.

She then turned her attention to the birth/baptism record copies I had submitted for reissuance. Because mine were in English and the parish books were in Latin, she couldn’t issue a new version.

I told her Latin was fine.

Next excuse: the form she uses doesn’t include the word “birth,” and my copy did. She couldn’t reissue it for that reason, either.

I simply said, “That’s okay. I’ll explain that policies have changed over time.”

She grumbled something about being unsure when she’d get around to it. I told her to mail it. We were already heading home.

Tally So Far?

Two days. Fourteen stops. Five records. Not great.

Part 3: The Gary Gauntlet and the Bureaucratic Brick Wall

Gary, Lake County, Indiana Index to Death Records, 1908-1920, Joseph Koss, digital database; Ancestry.com: accessed 30 July 2025, image 10 of 14.

This is a continuing series on my genealogical adventures in obtaining family records for a dual citizenship application. You can read my previous blogs here and here.

By early afternoon, I decided to head straight for Crown Point, the county seat of Lake County, Indiana. According to the website, the building that housed marriage and divorce records was located directly across the street from the one with birth and death records. Efficient, right? I actually thought to myself, “Wow, Lake County has it together!”

Think again, Lori.

Crown Point Confusion

Our GPS led us to… a juvenile detention facility. No address numbers anywhere. Hoping for better luck, we crossed the street to a large, official-looking government building and went inside.

That’s where I was able to obtain one record: a marriage certificate. After six hours of effort, that felt like winning the lottery. The staff promised to research the divorce record and contact me if, yes if, they found it.

Next stop: the County Health Department, which, according to an officer, was “the white building next to the juvenile facility.” Turns out the reason we hadn’t seen it was because it was set so far back off the road it might as well have been hiding.

My husband noted, “Hey, we got the first free parking space right in front of the door. That’s a good sign!”

Narrator: It was not a good sign.

Enter: The Wall of Gary

The moment we walked in, we were greeted by multiple signs declaring that the health department did not have records for Gary.

Wait, what? This is the Lake County Health Department, and they don’t have records from one of the cities in the county?

I double-checked the website later, no mention of this. I asked the clerk at the window where I could get Gary records. She looked at me like I had just uttered profanity in Latin. “At Gary’s Health Department,” she snapped.

“And where is that?” I asked.

Without a word, she pointed to a sign with an address on it, turned, and walked away.

Wow.

The Ethnic Club and the Mystery Man

My original plan had been to stop at two more locations that day, a local ethnic organization where my family had once been active, and the Diocese to pick up church records. But it was nearly closing time, and now I had three stops to make, clearly, that wasn’t happening.

We decided to do as much as we could, spend the night and continue the next day.

We started with the ethnic club, since it was close by. A car was parked out front, but the building doors were locked. I had tried to reach out to them previously with no success. No website. No returned Facebook messages. At this point, I figured I’d just mail them a query and hope for the best.

As we were pulling away, a man opened the front door. I jumped out. He wasn’t affiliated with the group but rented office space there. Still, he was helpful, gave me two phone numbers and admitted that the organization wasn’t exactly known for its communication skills. No kidding.

He also offered advice on dual citizenship. Turns out, he was trying to apply, too but his info was wrong. He’d tried to get his birth certificate through VitalChek. I’ve used them before. They happily took my money and never delivered a record. (Pro tip: if you use them, pay with a credit card that’ll support you when you dispute the charge.)

This man told me he had made 37 phone calls to try to track down his birth certificate because, brace yourself, Gary wouldn’t give it to him.

Why not?

“You’ll figure it out,” he said.

Oh boy. I could hardly wait.

A Warm Welcome in Gary

Next stop: the Diocese. They informed me the church records I needed had been transferred to another parish. I called. They had just closed, literally two minutes earlier.

So we decided to head straight to downtown Gary to try and retrieve the birth and death records I needed.

When we arrived, a shirtless man was being confronted by a police officer on the sidewalk. And in my head? Back Home Again in Indiana was playing. You can’t make this stuff up.

We parked quickly and headed inside the same building I had visited as a child to get my birth certificate before starting school. The elderly security guard greeted us warmly and directed us upstairs.

The First Hint of Hope

There were two employees at the counter, and one immediately asked what we needed. Miraculously, we received two birth certificates almost right away. After seven hours of driving, detours, and dead ends I finally had three documents in hand.

Then things went south. Fast.

The Death Certificate Debacle

I asked for three death certificates, dated 1919, 1966, and 1970. (See pic above) The woman behind the counter asked for the deceased individuals’ birth certificates.

I calmly explained: they were born in the 1800s, outside the U.S., and their countries didn’t issue birth certificates at that time.

Her response? “No birth certificate, no record.”

That is not Indiana law. That is a clerk making up her own rules and digging in.

I showed her original death records issued by that very office. She didn’t care. She asked for death certificates of their children which I provided. I also gave her birth and baptism records for one child.

Still no.

I tried to show her obituaries naming the parents and just for fun, me. Nope. She wasn’t having it.

Then she turned and walked away, loudly repeating, “Birth certificate, birth certificate, birth certificate” as if chanting it would magically make them appear.

We left empty-handed.

At this point, we checked into a hotel in nearby Porter County because I had one more shot at records the next day.

Spoiler: Things get weird. Again.

Dual Citizenship Part 2: Chicago Chaos

Cook County, Illinois Marriage Indexes, 1912-1942, Koss, Mary, digital image; Ancestry.com: accessed 30 July 2025, image 145 of 304.

After all the issues I’d already encountered (you can read about here), I foolishly believed things could only get better. So off to Chicago I went.

Stop 1: Cook County Clerk’s Office

I started at the County Clerk’s office, bracing myself, several colleagues had warned me about unhelpful staff. To my surprise, the clerk I got was wonderfully professional. One small mercy. Unfortunately, I didn’t walk away with any of the three records I was hoping for.

I had a certificate number for my grandparents’ marriage record, but it wasn’t in the system. You can see it exists from the picture above. I was also looking for a birth certificate that was possibly never filed; after all, I had a church-issued “Birth and Baptism” certificate. Back then, churches often issued those in lieu of civil records, and that document had even been used by a family member to enroll in Social Security. Still, no luck.

I was also searching for a death certificate I’d requested by mail on 31 March, four months prior to my visit, with no response. After about an hour of searching, the clerk informed me that a specialist would need to take over the research and contact me once they found something.

Correction: if they find something.

Stop 2: The Elusive Archives

Tip for Cook County researchers:

Ask security where to scan your parking garage ticket to get a discount.
When you first arrive, skip the main office, go down the first hallway with a large sign and a barcode. Scan it to get an electronic number. My wait? Only 25 minutes.

While I waited for a maybe, I moved on to Plan B: the Archdiocese of Chicago.

From there, I drove several blocks to the address listed on the Archdiocese’s website. Found a garage, $27 for 15 minutes (ouch), and entered the building.

Inside, I was informed (drumroll…) the archives are no longer located there. They knew the website was wrong. No apology, no signage, no indication they planned to correct it. Clearly, they don’t want people to use the archives.

The receptionist suggested I call the real archives before heading over I suppose they don’t like visitors. I did and was told to mail my request instead of dropping it off. I explained I was already in town for one day and just wanted to drop off the application to ensure my information was correct.

Back to the car. $27 parking bill for 15 minutes. No discount from the diocese, either. So much for grace.

Stop 3: A Parking Lot Blessing?

I spotted another lot across from what I hoped was the correct archives this time only $11 for 15 minutes. Progress! As I crossed the street, I realized the building was none other than Old St. Pat’s, where my husband’s great-great-grandmother, Mary “Molly” O’Brien Cook, had secretly brought her sons to be baptized. (Read my blog about dear Molly)

That felt like a good sign. (Also made for a great photo op.)

Inside, however, I was told the archivist wasn’t available, was going on a two-week vacation, and I shouldn’t check back until late August. The secretary reviewed my paperwork, made a few copies, took my check, and that was that.

The wrinkle? I wasn’t 100% sure which church my grandparents had married in, either St. Salomea, which is now closed, or St. Benedict’s, the family’s parish at the time of my great grandparents’ last child’s birth. Here’s a fun fact: if you don’t know the exact church, the Archdiocese will not help you. No guessing allowed.

I gambled on St. Salomea and asked how to access St. Benedict’s records. “They’re still open,” the secretary told me, handing me their address. I asked if she’d mind calling ahead to make sure someone would be there. She wouldn’t. Just handed me the address and not even a good-bye. Wouldn’t give me the phone number, either.

So, onward to Blue Island.

Stop 4: St. Benedict’s—Sort Of

About 30 minutes later, I arrived to find the church closed and the office now located somewhere else entirely. Apparently, the Archdiocese archives hadn’t gotten the memo.

My GPS couldn’t find the new location, so we tried another app and eventually found the building, locked. After ringing the bell twice, a woman finally came to the door. Without opening it, she told us everyone was in a meeting and to come back later.

I explained that I’d been sent by the Archdiocese and simply wanted to leave a message. After a pause, she let us in and asked for the couple’s names and marriage date. I handed her a copy of the Cook County index listing with the certificate number.

She disappeared into a back room, reemerged a few minutes later, and informed me: “No one by that name was married on that date.”

Sigh. The saga continues next week…

When AI Lost the Plot

How a quiet English lineage turned into a political scandal and what it taught me about truth, technology, and trust.

I use AI almost daily and have written and presented on it for nearly two years. But a recent experience left me completely baffled and more than a little uneasy.

I’ve been working on my final family genealogy book, this one tracing our Great Britain ancestry. My previous four books came together easily earlier this year because my notes were meticulous, my colleagues had verified my findings, and I’d been blogging about those ancestors for ten years.

Our British roots, though, are a different beast. Between my husband’s lines and mine, there are only five but they reach deep into medieval soil. Scholars can’t always agree on the pedigrees, and the repeated use of the same names has led to confusion and overlap. Sorting it all out requires patience, precision, and a love of historical detective work.

Last spring, when winter refused to obey the calendar, I drafted the outline and introduction for my new book, Echoes of Britannia. Then the season’s speaking engagements and client projects took over, and I set the manuscript aside with plans to finish it this fall.

When I returned to it in September, progress came slowly. My writing rhythm faltered, and I found myself staring at the same sentence for far too long. Grammarly could fix the punctuation, but it couldn’t fix writer’s block. My AI research assistant, Geni, usually helps bridge the gaps between genealogical sketches but apparently, he was blocked too.

We were working on the Venables of Kinderton, a noble but quiet family from Cheshire. They lived out their days peacefully, kept out of court battles, and occasionally donated a stained-glass window to a nearby abbey. In other words, wholesome and uneventful.

Until AI got involved.

My writing style isn’t the typical “Josiah begot Daniel who begot Uriah who begot…” genealogy. My family would fall asleep halfway through the second begot. They don’t like numbering systems either, even though they’re math people, not history people. Me? I’d rather run laps in PE than solve for X.

That’s why AI has been such a useful partner. Geni understands that I’m a storyteller who insists on historical truth, even when it’s messy. I like to think I’ve created a new genre: bedtime family stories with pictures for visual learners.

But one day, Geni froze mid-thought. After several failed attempts, I switched to another AI tool, Claude. I don’t use it often, but it greeted me warmly by name, which felt encouraging. I gave it a straightforward task:

“From the provided information, maintain all footnotes while making the narrative more engaging. Keep the tone conversational for readers with limited historical background.”

What came back stunned me.

The Venables, my mild, landholding, church-donating family, had been transformed into a political thriller. Claude had rewritten the story to liken them to a well-known modern politician, naming names and all. Suddenly, the Venables were misogynistic felons clawing for power.

I was horrified. I hit “thumbs down” and deleted it instantly.

A week later, I still couldn’t shake it. How could a neutral story about medieval gentry morph into a contemporary political allegory? Who gave the machine permission to do that?

My only conclusion: some AIs are now reflecting the political biases of the data they’re trained on. If their training includes modern news, it stands to reason that bias slips in and it shows.

That realization made me pause. AI is supposed to help us see patterns, not project agendas. As genealogists, we work hard to separate fact from family legend. Shouldn’t we expect the same integrity from our digital tools?

I chose not to share the story on Facebook. The last thing our country needs is another spark thrown into the bonfire of division. But I also felt this moment needed to be shared, not as outrage, but as a reminder.

We live in an era where algorithms, headlines, and echo chambers can reshape our understanding of truth. It’s up to us, researchers, writers, and everyday citizens , to hold fast to kindness, empathy, respect, honesty, and responsibility. These aren’t partisan ideals; they’re the foundation of human decency.

And as for those Venables? I’ve decided to let them rest a while. I’ll return to them soon, with fresh eyes and a renewed respect for their quiet simplicity.

Because sometimes, living a peaceful life that harms no one isn’t boring at all, it’s the truest kind of legacy.

When the Cloud Collapsed, Genealogy Continues

Guess we now know which Genealogy software companies use Amazon! MyHeritage.com and Findmypast.com are up and running. (2 PM Eastern)

I hope this is a wake up call to all of you who haven’t SYNCHED or DOWNLOADED your trees elsewhere!

All of the software companies are working. I’m able to access all of my info because I’ve saved it other than Ancestry.com and FamilySearch.org.

When the cloud service is restored you may want to read my blog articles on how you can prepare for the next time. Here’s the how to for FREE – Legacy Family Tree does not synch but you can upload a downloaded .gedcom from Ancestry. This means you won’t have pictures of the census or any other media but you will have the information about your ancestors. This older blog article talks about a previous version of Family Tree Maker, I’ve updated to the latest and greatest which fixed the problem I encountered and provided the work around. I don’t use FTM’s vault, a cloud service, but you might want to consider it given what’s happened today with Ancestry. I no longer use RootsMagic since version 8 as later updates would not allow me to synch with Ancestry. They do have a free version for smaller trees you could download. I do appreciate that their tech folks recommended I try downloading my tree with the free version to see if the problem was corrected; it wasn’t but they are aware of it and working on it. Click here for the free version.

Your genealogy research does not have to stop when a part of the internet breaks. Go make a cup of tea, write up what you’ve been working on, and make a plan for the future so you don’t get caught without access to your information. Here’s links to an older blog about writing up your research using AI. If you aren’t comfortable with AI, here’s an alternative. Remember, once upon a time there was no “online” for us to use to help us with genealogy.

The Hidden Discoveries of Writing Your Research

As genealogists, we spend hours pulling records, analyzing handwriting, and piecing together family connections. Most of that work happens in the collecting stage, we hunt down wills, census pages, land deeds, and church registers. But it isn’t until we write that we begin to see what those records are really telling us.

Writing forces a shift in how our brains work. Collecting records is like gathering puzzle pieces. Writing is when you finally flip the pieces right-side up and begin to see the picture. Patterns emerge that you hadn’t noticed before. Gaps in the timeline become obvious. A stray witness on a deed suddenly matters because you’re weaving the story instead of cataloging the fragments.

I saw this firsthand with my ancestor Daniel Hollingshead. I had collected a mountain of records: tax documents from Cheshire, court cases, marriage records from Barbados, and family land deeds in New Jersey. It wasn’t until I began to write his story that the threads pulled tight. Suddenly, the narrative was clear:

A grandfather’s failure as a tax collector plunges the family into crisis.
An uncle flees to Barbados after funds are stolen.
A young Daniel joins the military, is posted to Barbados, and marries into sugar wealth.
He returns to New Jersey with enslaved people, rising socially but carrying moral shadows with him.

The facts were always there in the records. But the story, the irony, the Atlantic World connections, the moral reckoning , only emerged when I tried to explain it in writing.

That’s the hidden power of writing: it doesn’t just preserve what you’ve learned, it teaches you something new. Writing sharpens your research questions, reveals new avenues to explore, and brings ancestors to life in ways a database never can.

So the next time you feel stuck in the research grind, try writing a short biography or family sketch. Even a rough draft will show you what you’ve missed. You might be surprised at what discoveries are hiding , not in the archives, but in your own words.

Saving Google Photos

AI Graphic

Are you tired of Google telling you that you need to purchase more storage? Are they threatening to shut down your email? One way to lessen the storage is to remove your photos from Google Photos. You can do this in batches which makes the task quicker. Here’s a quick how to. The photos below were taken on Sunday, August 7, 2016. I want to save all of them so I click the checkbox next to the date. If you don’t want to save all, click the checkboxes next the pictures you want to save:

Click the 3 dots and select download

The download will pop up and click it.

Now, drop and drag to your Desktop. There you can rename – I add the date.

I create a folder by year (Right click your mouse, click “New” “Folder” and name the folder by year.
When done with saving the photos for that year, I drop the folder into Dropbox.
If you have a lot of pics, you can easily extract them at one time. Simply click the “Extract All” icon:

Make sure you have created a folder to place them in or they will be all over your desktop!

Just select the folder from Browse and click “Extract.”

Next you’ll want to delete the Google Photos you’ve saved.

Simply click the dates again and the checkmarks will return.
Click the 3 dots and select delete.
The deleted photos will remain for 60 days in Google Photos Trash; if you need to clear up space immediately, on the side bar, under Collections, scroll down (it’s hidden) to Trash:

4. Clicking on Trash will bring up all the photos you deleted. To lessen your storage numbers, click empty trash and they will all permanently disappear – make sure you are ready to get rid of them as you will not be able to retrieve them after emptying trash.

I’ll be honest, my storage numbers did not significantly drop after deleting large amounts of photos but they have stopped harassing me to buy more space! I also have a lot of emails saved which I plan to move out of Gmail. Will give you the process in an upcoming blog.

As an added safeguard, back up your Dropbox to a stand alone hard drive!

Fall Genealogy Tasks

The weather hasn’t yet cooled and I’m not complaining but it is officially fall.

Before I get back to writing my next and final (hooray!) family genealogy book on our Great British lines I decided I had to practice what I preach and take care of some pressing tech tasks that I have put off for way too long. The first was really bothering me as it was boring and there are so many more interesting things to do in genealogy then preserve photos.

Long ago, in 2002, a world that was radically different then today, my cell phone saved all of my photos to a desktop program called Picassa that Google later purchased. I used that product until 2018 when Google rolled it into Google Photos. That’s when my problems began.

When Picassa ceased to exist it lost some of my photos, years 2002, 2007, 2010, and 2019. I wasn’t worried about 2002 & 2007 as my kids were still in school and I was still scrapbooking so I have those photos. I digitized the scrapbooks so we were good. 2010 & 2019, not so much. Sure, other family members probably have some of the photos but I always was the main photographer so much of that is lost. I know, it could be a lot worse but still, not happy about it.

The next issue was with the rollover, some of my photos were doubled and even tripled. New photos were created from group shots – just the heads of whatever the tech decided to select. Then it began creating memory albums. Now that doesn’t sound bad but it became a problem because it used up space and Google, tying all their products together, kept reminding me I needed to purchase additional space from them or I could no longer have a functioning email.

Occassionally, I’d go into photos and delete some of the duplicates and albums but they just would pop back up. On my to-do list was to remove ALL of my Google photos, store them in Dropbox, and back them up to a standalone hard drive. BORING. but. necessary.

For Valentine’s Day, one of my kids gave me a picture frame where you can store and see changing photos. This gave me the impetus to get the photos out of Google. Next week I’ll print the detailed directions on how you can do that fairly quickly and easily, meaning not saving one photo at a time which I initially was doing.

I also realized that I needed to synch my Ancestry.com tree as it’s been awhile since I did that. I no longer use RootsMagic and since I last synched, I got a new desktop so I didn’t have Family Tree Maker downloaded to it. Now FTM has come out with their update (in May 2025 but it’s called 2024, go figure). I somehow missed the promotions but they have one remaining, half price for current license members so I took advantage of it ($40 instead of $80). I decided if I was going to save Dropbox to the stand alone drive I might was well include my Ancestry tree since I’ve just blogged about how I was working at updating it. Yes, it’s still a work in progress but I’d rather save what I have as I’ll never be done with it.

Next up was to delete everything on my stand alone drive as it was all old and not relevant so I turned it back to factory settings. Took hours!

Meanwhile, one of our adult kids had their credit card stolen and the thieves, being really stupid – (Jose Lopez – I am calling you stupid!) bought items in their own name and then had it sent to our kids’ address. (Now you see why I am calling Jose stupid – really, does he want to get caught? Don’t even need a forensic genealogist for that one.)

Jose or whoever was the original thief, was fairly smart at the beginning. Only purchased from stores the kid always uses so for the first two weeks the scam wasn’t noticed. Then, boldness hit and the thief began using it for large sums at stores never used by the kid. By the time it was noticed thousands of dollars of items had been purchased but thankfully, some get to be returned to the companies since they arrived at the kid’s house. (Jose, did you think you were then going to be a porch pirate, too?) Kid called the credit card company for a dispute and the police to file a report in case Jose was local and was going to be paying a home visit. Cop informed us that a local woman got taken for $499,000 the previous week because they also stole her social security number and took out loans. What a nightmare!

That made me realize it was time for me to update some of my own financial practices.

You may have some items on recurring charges. We’ve decided to use a separate card for those because it’s a major pain to have to contact those vendors to change an account if your card is shut down.
Since the card was stolen locally (we know this for reasons I’m not disclosing so the guilty can get their due, too bad, Jose, that bed you bought won’t get you a good night’s sleep in jail because it’s already been returned) we decided to use one card just for local purchases. It’s a card with a good reputation to notice fraud quickly so we won’t have to dispute lots of charges when (not if) it get’s compromised.
We’ll use another reputable card for online only purchases.

If you’re thinking, that’s a back up for a back up and yes it is, just like we do to save our genealogy data. This led me to realize it’s been awhile since I updated my passwords so I spent time doing that as well.

Last task I haven’t completed but is equally important, albeit BORING, is saving many of my emails. Lots of them contain genealogical info and I want to make sure the info is saved to the correct ancestor’s file in Dropbox. That’s my next project and by then, well, it’ll probably be time to redo the cycle.

With the colder weather u perhaps coming next week this is a gentle reminder, dear reader, to take a look at your items to do and start plugging away at them.

How to Clean Your Ancestry Tree Without Paying for Pro Tools Part 3

For the past two weeks I’ve been blogging about Ancestry.com’s Pro Tools. You can read about my experience here and here.

Today, I’m going to show you how to clean your Ancestry tree without paying for Pro Tools. It’s super easy and honestly, I wish I’d thought of this years ago.

Start by picking a free or low-cost software program. Family Tree Maker and RootsMagic both sync directly with Ancestry. RootsMagic Essentials is free, but large trees can slow it down (I blogged about that here). If you don’t need access to your photos or documents and just want to focus on fixing errors, you can also download your tree as a GEDCOM and import it into Legacy Family Tree, which is what I did.

I kept things simple. I didn’t need media files for the check up, I just wanted to identify structural problems in my tree.

Here’s how to do it:

On Ancestry, go to your tree.
Click Tree Settings under Trees > Create & Manage Trees.
Scroll down and select Export Tree.
Once complete, download the file to your computer (it usually lands in your Downloads folder or OneDrive).
Open your genealogy software and import the GEDCOM.
Run the problem checker.

If you run into trouble with the software, you can literally ask ChatGPT (aka Geni!) for help. That’s how I found this entire workaround.

Once your tree is loaded, use the software’s built-in tools to flag potential problems. In Legacy, I went to Tools > Potential Problems. I set criteria to mirror the kinds of problems flagged by Ancestry’s Pro Tools, things like parents being too young, children born after a parent’s death, and so on.

One downside: Legacy doesn’t flag individuals with no sources, which was one of the main issues Pro Tools surfaced. But what Legacy did reveal was surprising and far more accurate.

Here’s the report I got from Legacy (the error types flagged by Ancestry are in red):

Let that sink in: 940 total errors, almost all of which are legitimate and actionable. Of that, there was only 55 errors that Ancestry claimed was 301 and they didn’t identify these people! I plan on cleaning up all of the errors Legacy found as having two individuals over age 110 years is a problem Ancestry should have discovered. And the individuals with no sex given? That is a continual flaw in Ancestry’s system when you are adding new individuals.

Unlike Ancestry’s Tree Checker, which falsely flagged over 10,000+ records in my tree, Legacy gave me a clean, accurate list I could work with. I now have the names and the issues. I’m going through them one by one and making the corrections directly in my Ancestry tree, since that’s still my primary working tree. I’ll continue syncing it with Family Tree Maker.

And if I get another $7 Pro Tools offer in the future? Sure, I might try it again just to check whether they’ve cleaned up the bugs. But I’ll cancel it right after. Because let’s be honest:

If Ancestry really wants our trees to be accurate, they should provide these tools for free.

We are already paying for the data, the DNA, the platform and in many cases, contributing our own hard-earned research. Charging extra for a tree-checking feature (that doesn’t even work right) feels like asking users to fix the foundation of the house they already paid to build.

So, skip the upsell. Use free software. Clean your tree with confidence. And let’s keep our standards higher than their price tags.

When Ancestry.com’s Pro Tools Fail: A Professional Genealogist’s Experience with Ancestry’s Tree Checker Part 2

Last week, I shared my experience with most of Ancestry.com’s Pro Tools—an add-on offered for $10/month (I got in for $7 with a promotional email). You can read about those features here. Today, I’ll dive into the tool that motivated me to subscribe in the first place: Tree Checker.

If you’ve noticed the new Tree Checker score on your Ancestry tree, you might be curious. Mine showed a 9.1—“Excellent.” That aligns with my belief that my tree is about 90–95% accurate. But let’s be honest: no one has a 100% accurate tree. Without DNA confirmation for every line, there will always be an element of uncertainty. Still, I’m committed to removing the detritus that’s accumulated over years of brick wall chipping, FAN Club research, and lineage society applications.

Back in 1990, I started my tree with 50 people, using a TI-89 cartridge program. By 1995, I was entering data into FamilySearch’s .paf format. When Ancestry came along, I uploaded my work to what’s now the ubiquitous .gedcom. My skills, and my tree, have grown significantly since then. I’ve cleaned up my Swedish, Croatian, French, German, Swiss, and Dutch branches. What remains is my largest line: Great Britain. Before writing my next book, I knew it was time to clean that section.

I regularly back up my Ancestry tree to other programs (Family Tree Maker, Legacy, RootsMagic), all of which offer tree-checking tools. But because Ancestry is my primary research platform, I’ve been hesitant to clean externally and re-sync. So I was hopeful that Tree Checker would finally give me an effective cleanup solution within Ancestry.

Here’s what happened.

Tree Checker: Expectations vs. Reality

When I launched Tree Checker from the dashboard, I was greeted with a gut-punch: 14,000+ possible errors.

The majority were labeled “People with no sources.” I immediately knew what was going on. In Ancestry’s early days, there wasn’t a “web link” option. I got around that by uploading source PDFs to the Gallery or by placing citations in the timeline. Unfortunately, Tree Checker ignores those, unless it’s housed as an official Ancestry “source,” it’s invisible to the system.

But that still left other problem categories:

Possible Duplicates
People with Only Tree Sources
Other Possible Errors

I’ll add here that one of the most helpful “error types” isn’t even under Tree Checker, it’s found under Pro Filters > Family Lines > People Without Relationships. These are individuals floating without connections, often leftovers from attempts to delete a line. I had about 2,000 of these and quickly removed them.

People with Only Tree Sources was next. These were added from others’ trees, unsourced. That’s an easy fix, either delete them or attach a hint. Done.

Possible Duplicates looked daunting at nearly 2,000, but the number was misleading. Triplicates and higher were counted separately, and after filtering, I had fewer than 1,000 to review. Some were legitimate merges (e.g., marriage records auto-adding a new spouse). Others were not duplicates at all: families who reused names after a child died, or multiple “Johann” Harbaughs with different middle names. I worked through them in two days.

The Glitches Begin

After carefully resolving every duplicate, I noticed something troubling: they didn’t disappear from the error list. No matter what I tried, refreshing, logging out, rebooting, clearing cache, Tree Checker continued to show errors I had already corrected. I even tried deleting and re-adding a person. No dice.

Still hoping for results, I moved on to “Other Possible Errors” and found myself stunned.

Ancestry itself was causing many of the flagged issues. For instance, if a child was born in 1937 and enumerated in the 1940 census, Tree Checker would flag it as “Resident listed before birth date.” The kicker? That census record was automatically added by Ancestry in the timeline for 1935. To clear the error, I had to delete 1935’s entry FOR EVERY ONE born between 1936-1940.

Swedish church records were another problem. Ancestry indexes these by range (e.g., 1723–1728). If a child was born in 1724, Tree Checker flagged the 1723 record as occurring before birth. Completely illogical and a huge waste of my time to clean up!

Some new error flags also made no sense:

“Birth/Death dates span more than 10 years” with only one sourced date. What?
“Significant age difference between spouses” um, 2 years!
“Marriage occurred after spouse’s death” when no death date was even given. See the above screenshot proving the error was false.

And here’s the real kicker: even when I corrected the problems, they remained in the count. Over the next three days, my “error total” would inexplicably rise despite spending hours cleaning.

Note that it says there are 2 possible duplicates but none show.

People with only tree sources shows 1 but none are provided.

Under all possible errors the counter states 201 but there is only 1 error showing and it is not an error when you go to that page.

This reminded me of a long ago problem Ancestry had with what was called “Ghost Hints.” You can read my how-to-fix blog about it here. I tried that again but it appears that Ancestry has tightened up security and my fix it no longer worked.

As a genealogist, I dug into the data. I exported the report, analyzed the stats, and discovered something stunning:

75% of the Tree Checker results were false positives. That’s not a helpful tool -that’s noise! Seeing it graphically made me realize I had been sold a product that doesn’t work:

To top it off, this also distorts your overall Tree Checker “score.” I now wonder what my real rating would be if the tool actually worked. With the changes that took, my score reached a 9.4.

The Final Straw

I then turned to the “No Sources” filter and began manually fixing issues from A–Be, X, Y, and Z. That’s when I hit the wall. Even attaching suggested Ancestry hints they no longer removed individuals from the list. Not user error, this was a flat-out malfunction.

That’s when I noticed the word Beta scattered throughout Pro Tools. Beta testing, by definition, is the final phase before a product goes public. Users test real-world functionality and provide feedback. But here’s the problem:

Ancestry released an untested tool to the public and then charged for it.

If you charge admission before the dress rehearsal is done, that’s not Beta testing. That’s profiteering.

But that’s not all! Ancestry then sent me an email with their data about the changes I made to my tree:

What does 300% more duplicates found even mean?! We know I had no duplicates and most of those that they believed were duplicates were not. 84% fewer issues discovered? Does that mean my tree still has 16% undiscovered issues? If so, how would I ever find them when Pro Tools can’t identify them and the counter doesn’t work?

Where Do We Go From Here?

I’m not just disappointed, I’m concerned. It’s clear Ancestry recognizes the problem of flawed user trees. But their solution shouldn’t be charging extra for a broken product.

And now, they’ve rolled out something even more baffling, a $5,000/year “cohort club” promising professional coaching, a few DNA kits, and discounted branded merchandise. (Want a denim jacket? You can buy one at a discount.) Click the link as I’m not making this up. There VIP service, you get a working phone number if you have a problem. Pardon me, but I always thought that’s what a legitimate business offered TO ALL OF THEIR CUSTOMERS for free.

In a recent webinar, the presenter said she came up with the idea of genealogy coaching. That’s interesting, since I’ve offered coaching on my website for over a decade at a fraction of the price. I believe everyone should have access to their heritage, not just those who can afford a luxury tier. I was also appalled to hear that professional genealogists charge tens of thousands of dollars a year. No, just no!

I use Ancestry daily and plan to continue. But I’ve cancelled my Pro Tools subscription.

Next week, I’ll share how I cleaned up my tree without shelling out extra cash.