Ancestry is running its annual 4th of July Sale, offering 50% off 6-month or annual memberships through July 7, 2026. This limited-time discount applies to new and returning subscribers.

• U.S. Discovery: Access all U.S. family history records
• World Explorer: U.S. and international records
• All Access: U.S. records, global records, and access to Newspapers.com and Fold3

Important Details

• Deadline: The 50% promotional offer ends on July 7, 2026, at 10:00 AM ET
• Eligibility: This deal is valid only for new and returning subscribers (not applicable for renewals of current subscriptions)
• Auto-Renewal: Your subscription will automatically renew at the standard list price once the 6-month term is complete. If you don't want to renew, cancel at least two days before your renewal date

One of the most frustrating experiences in Appalachian genealogy is discovering that the records you need either don't exist, can't be found, or seem to have vanished entirely.

You know your ancestor lived in a particular place.

You know they owned land, paid taxes, got married, had children, and died there.

Yet somehow there are few—or no—records documenting those events.

What happened?

The feeling that your ancestors have "vanished" is a common rite of passage for researchers in this region. It isn't necessarily a failure of your research; it is a byproduct of the specific historical, geographical, and bureaucratic environment of the 18th and 19th-century frontier.

Understanding why these records are missing is the first step toward finding creative workarounds to break down those brick walls.

1. Many Records Were Never Created

One of the biggest misconceptions in genealogy is that every birth, marriage, and death was recorded.

In reality, many Appalachian communities had no requirement to record these events for much of their history.

Statewide birth and death registration often did not become mandatory until the late 1800s or early 1900s. Even then, compliance was inconsistent, especially in rural areas.

For many families, there simply was no official record created. When formal clerk records were nonexistent, much of family history lived in the family Bible. These books were passed down, lost in house fires, sold, or separated from the family line, taking generations of vital data with them.

2. Late Adoption of Vital Registration

Many states in the South and Appalachia did not mandate state-level birth and death registration until the early 20th century. Before that, recording such events was voluntary and often considered a personal or church matter rather than a legal requirement.

Read our in-depth guide to vital registration dates here: https://www.reddit.com/r/AppalachianGenealogy/comments/1ui7fip/genealogy_record_gaps_explained_a_guide_to_states/

3. County Boundaries Changed Constantly

Many Appalachian counties did not exist when our ancestors first arrived.

As populations grew, new counties were carved out of older ones. A family might live on the same farm for fifty years while technically residing in three or four different counties without ever moving.

Researchers often search the wrong county simply because they are unaware of historical boundary changes. When records seem to be missing, one of the first questions to ask is:

"Did this county even exist yet?" or "What was this area called before this time period?"

4. Geography Made Record-Keeping Difficult

The mountains that helped shape Appalachian culture also made administration more difficult.

Travel could be slow and dangerous. Many families lived far from county seats, churches, and government offices. Reporting births, deaths, and marriages was often inconvenient or simply not considered necessary.

As a result, record coverage can vary dramatically from one community to another.

5. Families Moved More Than We Think

Many Appalachian families followed migration routes through Virginia, Kentucky, Tennessee, North Carolina, West Virginia, Ohio, Indiana, Missouri, Arkansas, Texas, and beyond.

Researchers often assume an ancestor lived in one place their entire life when, in reality, they may have crossed multiple counties and states.

Sometimes the record isn't missing.

It's somewhere else.

In the early settlement days, people moved quickly to follow new land opportunities or shifting economic conditions.

They were often "squatters" on land they didn't officially own, meaning they never appear in deed books or property records. Even if they didn't own the land, they were often still taxed on their "movable property" (horses, cattle, slaves, or just a poll tax for being an adult male). This is why tax lists are frequently the only evidence that a family existed in a specific place during a specific decade. They show the person was there, but they don't link them to a permanent address.

6. Courthouse Fires and Record Loss

Throughout Appalachia, courthouse fires destroyed countless records.

Some losses were caused by accidents. Others occurred during wars, civil unrest, natural disasters, or poor storage conditions.

Entire collections of deeds, probate records, court records, marriage licenses, and tax books have been lost in some jurisdictions.

For certain counties, a courthouse fire can create a genealogical "black hole" spanning decades.

7. Names Were Flexible

Before widespread literacy and standardized spelling, names were often recorded phonetically.

The same individual might appear in records under several different spellings during their lifetime.

It was common for individuals to go by middle names or family nicknames that became their "official" identity in the community. Furthermore, the practice of naming children after older relatives—combined with the limited pool of names in many mountain communities—means you might be looking for "John Smith" when the record is actually filed under a nickname or an older kinsman with an identical name.

Researchers searching for only one spelling may overlook important clues or records hiding under another variation.

8. We Expect the Wrong Records

Many beginners search only for birth certificates, death certificates, and marriage licenses.

When those records do not exist, they assume the trail has ended.

In reality, Appalachian genealogists frequently rely on:

• Tax records
• Land grants and deeds
• Probate records
• Wills
• Court records
• Church records
• Military records
• Newspapers
• Cemetery records
• Family Bibles
• Oral history

Sometimes indirect evidence is the only evidence available.

How to Pivot Your Strategy

When the "official" records fail you, you have to reconstruct the paper trail using secondary and circumstantial evidence:

• Follow the Money (Tax Lists): Even when deeds don't exist, tax lists are often held in state archives and were generated annually. They are the best way to prove a person was in a specific county during the years between federal census records.
• Look to the Church: Many settlers were deeply religious. Even if the county didn't record a birth, the local church session minutes, baptismal records, or vestry books likely did.
• Use FAN Club Research: Research the Friends, Associates, and Neighbors. If your ancestor left no records, look at who they witnessed deeds for, who they served on juries with, and who married into their immediate circle. The record you need is often hidden in the files of a neighbor.
• State-Level Records: If the county records are gone, check the state land grants or legislative petitions. State capitals often kept copies of land surveys or records that survived the local disasters.
• Adopt Phonetic Searching: Stop searching for one specific spelling. Use wildcard searches (e.g., "Sm*th") and think about how a name sounds if spoken with a thick local accent. A clerk recording a name phonetically might write down something very different from how you see it on a modern document.
• Master Naming Patterns: Learn the traditional naming customs of the region. Often, children were named in a specific order (e.g., first son named after the paternal grandfather). If you find a mystery ancestor, look for neighbors with the same names; they are almost certainly extended family.

I know I am not the only one feeling the frustration of the "Appalachian fog." I’d love to hear how others have navigated these gaps. What is your "go-to" alternative source?

If you have been pulling your hair out trying to find a birth certificate or death record for an ancestor in the South or Appalachia around the turn of the century, there is a very good chance you are hunting for a document that literally never existed.

It is incredibly common to suspect something's going on when a family line goes dark, but the reality often comes down to state law: the records were never created in the first place.

Historically, states viewed births and deaths as private family or church matters, not government business. Centralized state registration didn't actually become the norm until the federal government pushed for national standardization in the early 1900s.

We've pulled together a timeline that outlines when mandatory statewide registration actually took effect across the regions, along with specific historical gaps that researchers should keep in mind.

State	Official Start Year	Historical Gaps
Alabama (AL)	1908	Earlier records exist only as fragmented county-level ledger books rather than centralized state files.
Georgia (GA)	1919	Mandatory tracking began in 1919, though general compliance wasn't achieved until the late 1920s.
Kentucky (KY)	1911	Enacted a law in 1852 but abandoned it during the Civil War. Continuous, mandatory tracking was not successfully established until January 1911.
Mississippi (MS)	1912	Centralized state records did not exist in any capacity before November 1912.
North Carolina (NC)	1913	Mandated in October 1913. A death in September 1913 will not have a state death certificate.
Ohio (OH)	1908	Centralized state records began in December 1908. While county probate courts recorded births/deaths from 1867–1908, compliance was highly inconsistent and un-indexed statewide.
Pennsylvania (PA)	1906	Centralized records began in January 1906. An 1852–1855 mandate failed and was repealed. Fragmented county records exist for 1893–1905, and major cities (like Philadelphia and Pittsburgh) kept earlier independent registries.
South Carolina (SC)	1915	The latest baseline start in the region. General compliance wasn't reached until several years after 1915.
Tennessee (TN)	1908 / 1914	The 1913 Void: Funding lapsed, meaning 1913 is completely blank statewide. Continuous tracking permanently resumed in 1914.
Texas (TX)	1903	Compliance was low for the first two decades, especially in rural areas and remote ranches.
Virginia (VA)	1912	The 1896–1912 Gap: VA tracked records from 1853–1896, but then repealed the law, creating a total black hole until 1912.
West Virginia (WV)	1917	No centralized state reporting for births and deaths existed prior to 1917.

How to Bypass the Gaps: 3 Substitute Records to Search Instead

When state vital records do not exist for a specific time period, alternative paperwork can help us build a circumstantial case.

1. Delayed Birth Certificate Collections

When Social Security was introduced in 1935, millions of people born in the late 1800s needed official proof of birth to secure their benefits. States met this demand by issuing "Delayed Birth Records" based on family Bible entries, school censuses, or old doctor affidavits.

These collections are searchable on Ancestry or FamilySearch and frequently document births stretching back into the 1870s.

2. County Equity & Probate Court Loose Papers

If an ancestor died without a will, or if a family disputed land boundaries, the local county court had to identify every single living heir to divide the estate or property proceeds. The "loose papers" of equity and probate courts often explicitly list all surviving children—including married daughters with their new surnames—proving relationships that regular vital records missed.

Some county collections are searchable on FamilySearch.

3. State Censuses

While the federal government took a census every decade ending in zero (1880, 1900), several states took their own completely separate State Censuses, usually on years ending in "5" (1885, 1895, 1905).

Both Ancestry and FamilySearch platforms have specific database subsets for state censuses.

• Alabama: Conducted several early censuses, including a post-Civil War count in 1866 (great for tracking families after the war) and a special census of Confederate veterans in 1907.
• Georgia: Ran state censuses in 1827, 1834, 1838, 1845, 1852, 1853, 1859, 1865, and 1879. Access varies by county, but they are incredibly helpful if your target county's records survived.
• Mississippi: Ran frequent state censuses throughout the 1800s, with later ones occurring in 1841, 1845, 1853, 1860, and 1866.
• North Carolina: Took a state census from 1784–1787, which helps replace the missing 1790 federal records for some counties, but did not conduct state censuses in the 1800s or 1900s.
• South Carolina: Conducted censuses in 1869 and 1875. The 1875 census is particularly useful because it hits right in the middle of the 1870–1880 federal gap.
• Tennessee: Only conducted one state-level census in 1891 (an enumeration of male voters), which can help bridge the 1890 federal census loss, though it only lists adult men.
• Texas: Only conducted state/territorial censuses between 1829–1836 while still under Mexican rule.
• Virginia: Only took state censuses right after the Revolutionary War (1782–1786) to help rebuild tax lists.

4. DNA Triangulation (Genetic Genealogy)

When the paper trail is limited, DNA can serve as a primary record. If you suspect an unrecorded child fits into a family line, look for distant cousin matches who descend from multiple different siblings of that target family. Matching descendants across separate branches triangulates the connection back to the parents, bridging the paperwork void.

5. Match Clustering

If you have a massive list of thousands of distant cousins and you aren't sure which ones belong to your unrecorded ancestor, you will need to group them. Historically, researchers used a manual spreadsheet system called The Leeds Method to do this.

If you use Ancestry, this is now built directly into the platform via Pro Tools as Matches by Cluster. It automatically runs the math, finds your matches between specific centimorgan (cM) ranges who also match each other, and drops them into clean, color-coded visual groups.

This instantly isolates your matches into distinct branches. Once they are grouped, you can ignore the rest of your match list and focus entirely on the tree patterns inside that cluster to find your missing ancestor.

6. Chromosome Mapping

This method involves mapping the actual physical segments of your DNA to those of your Matches using a tool called a chromosome browser, like DNA Painter.

When you look at your matches on a chromosome browser (like DNA Painter, GenomeLink, or GEDmatch), you can see the exact start and stop locations of the DNA segments you share.

By mapping these segments, you can visually phase your chromosomes to say, "I inherited this exact chunk of Chromosome 4 from my 4th great-grandmother." If five different descendants of that family all overlap with you on that exact same block of Chromosome 4, you have forensic, physical proof of a shared biological inheritance.

Which state has been the most troublesome for your family tree? I would love to know!

Mine goes all the way back to the very beginning of the colonial era in the late 1400s…one of my umpteenth great aunts was supposedly Pocahontas’ sisters.

It ends there but I’m assuming that’s because Natives didn’t keep a paper trail of documents pre-Columbus.

Hi Genealogists!

I recently built Whatiiif.com, a free, open source tool for sharing links to specific regions of digitized documents. It detects IIIF manifests and loads them into a viewer, then you highlight your desired region, and the website generates a permanent URL that loads as a comparison view with all of the context intact. The URLs are long because that's where all the data is stored, but that's what hyperlinks are for.

Just thought you guys could get some use out of this. Questions and feedback are welcome!

-Nate

We’ve all experienced the frustration: you find an indexed record that looks like the perfect breakthrough for your family tree, only to hit a wall that says “No Image Available.”

It’s incredibly tempting to stop there and assume it's a dead end—I’m guilty of doing that myself! But walking away means you are likely missing out on those critical un-indexed details that actually solve your research mysteries.

This can happen when Ancestry has permission to show the transcribed text but lacks the license to display the image, and it means that the actual document exists somewhere else.

An index entry on Ancestry is just a pointer; it is the starting point of the search, not the destination. So when you see "No Image Available," treat it as an invitation to go dig up the original source using these three methodologies.

1. Deconstruct the Source Citation

When Ancestry displays a "No Image Available" transcript, they are legally required to credit the archive or publication that owns the original document. Most researchers ignore this text at the bottom of the page, but it contains the exact coordinates of the physical or digital image.

Where to Find It

Scroll completely past the indexed names and dates to the bottom of the page. Look for fields labeled "Source Information," "Source," or "Source Citation" as pictured:

Source Information for a marriage record

Inside this text, you are looking for specific pieces of metadata:

• Repository: The name of the archive, historical society, or government agency that physically holds the record, such as “The National Archives at St. Louis” or “State Library of Pennsylvania”
• Publication Title: The title of the original book, ledger, or microfilm collection that this record appeared in (e.g., “North Carolina Christian Advocate” or “Confederate Pension Applications, 1911–1915”).
• Locators: Volume numbers, page numbers, certificate numbers, file codes, or box/roll numbers.
• Source URL: This is a web address pointing to an external database where Ancestry extracted the data. Try copy and pasting this URL into your browser to check and see if the image will load for you.

How to Execute the Search

Once you have copied this information, do not just throw the ancestor's name back into Google. You need to target the source directly using these methods:

• For Newspapers and Obituaries: If the citation lists a specific newspaper name, date, and page number, check free alternative repositories like my favorite, Chronicling America (Library of Congress) or state-specific digital newspaper projects run by university libraries. If the source citation includes an external link to a partner site (like Findmypast or Fold3), you often need to navigate directly to that specific platform to view the image.
• For Book and Ledger Citations: If the source data says something like "From the book: Wills and Administrations of Accomack County, Page 142," search the FamilySearch Digital Library, Google Books, or Internet Archive for that exact book title. Because these books are often out of copyright, they are frequently hosted for free on these digital libraries.
• For State Archive Citations: If the citation credits a state archives collection, go directly to that specific state’s official archives website. Locate their internal "Finding Aids" or digital collections catalog and use the box number, roll number, or folder code found in your Ancestry citation to pinpoint the exact digital folder or request a physical copy.

2. Decode the FamilySearch Film Number

One of the most valuable clues on an Ancestry index page is an entry labeled FHL Film Number, GS Film Number, or Film/Image Group Number.

Where to Find It

Look directly in the main body of the indexed transcript text. It is usually listed toward the bottom of the individual's indexed details, right before the formal source citation:

https://preview.redd.it/1esrt0xtgi9h1.png?width=654&format=png&auto=webp&s=ffa2b67840b1ec3513e6fa60b121e08207b6660c

How to Execute the Search

Many of Ancestry’s indexed collections were originally digitized from microfilms owned by FamilySearch. Ancestry has the right to host the searchable index, but the actual image files live over on FamilySearch for free.

1. Copy that specific film or image group number from Ancestry.
2. Head over to FamilySearch and open the Catalog search tool (Search > Catalog).
3. Select the option to search by Film/Image Group Number and paste the digits in.
4. On the Search Results page: Once you locate the correct microfilm roll, look at the status icons to the right of the film listing to identify your next steps.
   • Camera Icon: Best case scenario. The digital images are viewable online; click this button to browse the microfilm roll page-by-page to find your target volume and page number.
   • Camera Icon with Key Above It: Access is restricted due to licensing agreements.

3. Chase the Original Record Keeper

When there is no direct link, no film number, and no image on Ancestry, remember a fundamental rule: Ancestry is not the record keeper. It is an indexing and access platform. The physical records belong to a specific courthouse, state archive, or land office.

Where to Find It

Look closely at the index metadata for county names, volume numbers, book names, page numbers, or land certificate codes. This is common with early land patents, probate records, tax lists, and court minutes.

How to Execute the Search

Take those volume and page citations directly to the source. Search the state archive website, the Bureau of Land Management database, the county recorder’s office, or local historical repositories. You will frequently find that the original volumes have been digitized and hosted on a completely different local or state government portal.

----------------------------------------

Chasing down the original image takes a little extra effort, but it is exactly what helps us solve those mysterious brick walls and build bulletproof genealogical research. The next time Ancestry tells you an image isn't available, don't walk away—use these tools to trace it back to the source.

💬 What is the most surprising or critical piece of information you’ve ever found buried in an original document that was completely missing from the online index?

Hi there, I recently created r/AppalachianGenealogy as a space to research and discuss this niche genealogical topic.

I created the community because Appalachian Genealogy has very unique features that newcomers are often confused by.

I wanted a space where I could make longer form content to answer these questions, and where others who have expertise and experience can gather without distractions, gatekeeping.

One of my tactics to grow the community has been crossposting some of the applicable posts from the larger, "feeder" subs into mine. But after reading some posts on this sub, I started to wonder if those communities would be upset by my doing so.

I respect their sub and still participate with them, so I don't want to create any hard feelings. Vibe check me please 🙏🏼

Is this something to be concerned about?

I recently received my AncestryDNA results and found that my ancestry is primarily from England (61%), with significant Scottish/Northern Irish (20%), Welsh (12%), and smaller Irish (7%) roots.

My family has more recent roots in southern Mississippi (Jasper and Jones Counties), and I'm interested in learning more about both my ancestral origins in the British Isles and the migration of these groups into America.

I've come across the following books and am wondering if anyone here has read them and would recommend them:

• A History of Wales — John Davies
• The Reivers — Alistair Moffat
• The Scotch-Irish: A Social History — James G. Leyburn
• Born Fighting — James Webb
• Albion's Seed — David Hackett Fischer

For those familiar with British, Scotish, Welsh, Irish, or Southern U.S. history, are these good places to start?

Additionally, are there any other books you'd recommend?

Thanks!

Date Added: 6/22/2026

General collection information

This collection is an index of a family tree created by Ancestry’s professional genealogists from the book series Descendants of the Signers of the Declaration of Independence. Providing information from 1706 to 1900, Descendants of the Signers of the Declaration of Independence is one of the most complete genealogies of the signers and their descendants. The index doesn’t include images from the books.

This index provides the family history of the 56 signers of the Declaration of Independence, going forward up to five generations. The collection includes fourteen signers who left no direct descendants.

Using this collection

The index may include the following information:

• Names
• Birth dates
• Marriage dates
• Death dates
• Family relationships

If you believe you’re a descendant of one of the signers of the Declaration of Independence, this collection may be one of the best places to begin building out your tree or to fill in gaps in your tree. Alternatively, if you believe you are related to a specific Signer but don’t know how, you can use this collection to trace their lineage and find the connection to your tree.

This collection also contains index notes that may be able to provide you with more insight about your ancestor.

Source Information

Ancestry.com. U.S., Descendants of Signers of the Declaration of Independence, 1706-1900 [database on-line]. Lehi, UT, USA: Ancestry.com Operations, Inc., 2026.

Original data: Descendants of the Signers of the Declaration of Independence, seven volumes. Author Reverend Frederick Wallace Pyne, CGRS, 1997. The index for this collection was created by Ancestry ProGenealogists using Pyne’s book series.

Imagine logging into your DNA results for the very first time, eager to sort your matches into neat maternal and paternal columns, only to discover a massive group of people frustratingly labeled as "Both Sides."

Instead of neatly organizing your list into distinct paternal and maternal matches, algorithms often act like a binary switch—if they detect a tiny, distant fragment of overlapping genetic material from the opposite parent, they default to a "Both Sides" designation.

Understanding why this happens is essential for creating real, actionable tree connections.

Part I: Direct Family Tree Layouts

These are the reasons that make immediate sense, and you can solve them just by looking at a standard pedigree chart.

1. Cross-Branch Marriages

This occurs when distinct branches of your tree intertwine purely by marriage, without any biological endogamy or pedigree collapse.

• The Scenario: A cousin from your father’s side of the family marries a cousin from your mother’s side of the family, and they have a child.
• The DNA: That child (your match) genuinely shares biological DNA with both your mother and your father. The algorithm is technically correct here, even though your parents themselves share no common ancestors.

2. Parallel Ancestors (Identical Ancestors on Both Sides)

• The Scenario**:** An ancestral couple appears on both a maternal branch and a paternal branch further back in time.
• The DNA: Anyone descended from that specific couple will inherit DNA that could match either side of your family. Because the algorithm cannot differentiate which parent passed down which specific segment from that shared ancestral couple, it defaults to marking the match on "Both Sides."

Part II: Biological Factors

These scenarios occur when your long-term family history and regional biology alter the DNA itself over generations.

1. Pedigree Collapse

• The Scenario**:** Two lines of your family tree converge further back, meaning you have fewer unique ancestors than the standard mathematical progression because relatives married each other (such as second or third cousins).
• The DNA: While this frequently scrambles matches on a single parent's side, if pedigree collapse occurs on lines where your maternal and paternal trees eventually brush against each other, the algorithm cannot isolate a single ancestral source. It sees heavily concentrated, repeating segments of DNA and defaults to "Both Sides."

2. Endogamy

• The Scenario**:** Your maternal and paternal lines both trace back to the same highly isolated geographic region or distinct cultural group where people married within the same pool for hundreds of years.
• The DNA: Because the gene pool was closed, everyone in that population is distantly related to everyone else in multiple ways, leaving you with a dense baseline of shared genetic history from both parents. When Ancestry processes a match from that same community, the algorithm detects those identical-by-population segments on both your maternal and paternal strands, making a "Both Sides" label inevitable.

Part III: Technical & Algorithmic Limitations

These are the limitations within the platform's code and statistical processing that cause the system to miscalculate.

1. High-Weight vs. Low-Weight Pathways

• The Scenario**:** A match connects to you through a clear, high-centimorgan, definitive pathway on one parent's side. However, because your maternal and paternal lines lived in the same geographic areas for generations, you might also share a tiny, 7 cM segment from a completely different, ancient line on the opposite parent's side.
• The DNA: Instead of assigning proper weight to the obvious, close relationship, Ancestry treats any shared DNA on the opposite side as an equal trigger. It overrides your definitive tree pathway and forces the match into "Both Sides."

2. Random Chance vs. Real Inheritance (IBS vs. IBD)

• The Scenario**:** The algorithm spots a matching DNA segment on your maternal side and another on your paternal side.
• The DNA: Some small segments match purely by random chance or because they are incredibly common in a specific geographic population (Identical by State, or IBS). If the system catches a false, ancient "match" on your mother's side and a real, traceable one on your father's side (Identical by Descent, or IBD), it can't tell the difference and simply selects "Both Sides."

3. Phasing Errors

• The Scenario**:** The system runs its automated algorithms (like Timber) to filter and split your DNA results into parental sides when you don't have both parents tested. It relies on statistical data to "phase" your DNA—meaning it separates your maternal and paternal chromosome strands based on raw data.
• The DNA: The process isn't perfect. If the algorithm misreads a segment and accidentally assigns a paternal match's data to a maternal chromosome, it creates a technical conflict. Because the system's own data is contradicting itself, it defaults to "Both Sides."

Part IV: Key Takeaways for Research & Troubleshooting

How to Identify the Culprit - Spotting Tree Structure Factors:

When a match is flagged as "Both Sides" purely due to the structural layout of your family tree, you can easily identify the exact cause by looking for these specific clues:

• Identifying a Cross-Branch Marriage: Look at your Shared Matches list for the person in question. If you see two distinct, separate clusters of close cousins—one cluster exclusively from your father’s side and one cluster exclusively from your mother’s side—but those two cousin clusters share absolutely no DNA with each other, you are looking at a cross-branch marriage. The match is the child or descendant of those two separate lines crossing paths.
• Identifying Parallel Ancestors (Shared Ancestral Couples): Look at your own pedigree chart on both your maternal and paternal sides. Trace them back to see if the exact same surname and couple (e.g., John Smith and Mary Jones) occupy two different branches on your tree. If they do, any match who also descends from that specific couple will be flagged on "Both Sides," but their shared matches will only consist of other descendants of that specific couple, rather than your entire maternal or paternal family lines.

How to Identify the Culprit - Spotting Biological Factors:

• The "Shared Matches" Cross-Over: When you look at a match who is supposedly on "Both Sides," you will notice that their shared matches list includes prominent cousins from both your maternal and paternal lines.
• Surnames and Geography: You will see the same 3 to 5 distinct surnames repeating constantly across both your mother’s and father’s trees, typically concentrated in a single historic county, valley, or isolated community.
• Disproportionately High Centimorgans (cM): The total amount of DNA you share with a match will feel "too high" for how distant the paper trail says you are. Because you are inheriting multiple small segments from multiple shared lines, the algorithm stacks them together, inflating the relationship prediction.

How to Identify the Culprit - Spotting Technical Factors:

You can identify technical limitations through a simple process of elimination:

• The Single-Digit Segment Clue: Look at the detailed segment breakdown for the match (if the platform provides a chromosome browser or segment data). If you share a massive 150 cM block on your paternal side, but only a tiny, single 6 cM or 7 cM segment on the maternal side, it is highly likely a low-weight pathway or random chance (IBS). The algorithm is letting a tiny speck of background noise override a major relationship.
• The "Ghost Parent" Test: If you have one parent who has taken a DNA test, check if the match appears on that parent's list. If the match shares zero DNA with your tested mother, but the system is labeling them "Both Sides" on your profile, you are likely looking at a phasing error. The software simply misread which chromosome strand the DNA belonged to when processing your raw data.

How to Override and Update Labels on Ancestry:

If the automated parent assignment feature makes a mistake or gets completely flipped (which frequently happens after database updates), you have to step in manually:

1. Check Your Primary Tree Relationships: Click on your own profile within the tree linked to your DNA. Select Edit > Edit Relationships and verify that both your mother and father are explicitly marked as Biological. If they are unlinked or set incorrectly, the algorithm's parental sorting will completely break.
2. Fixing Entire Flipped Sides: If Ancestry completely inverted your parents (labeling your known maternal cousins as paternal), go to your DNA main page, look for the By Parent section, and click Edit Parent. This allows you to toggle the parent labels back to their true identities globally.
3. Manually Labeling Individual Matches: Open the profile of the mislabeled match. Click Edit Relationship (the button next to "Connect to Tree"). Here, you can manually switch the parental assignment to strictly Paternal or Maternal based on your paper trail.
   • Note: If you change a "Both Sides" match to a single side, Ancestry may display a red exclamation point. This is just the software warning you that your manual entry conflicts with its automated algorithm. If your paper trail is solid, ignore the warning—your genealogy research is more accurate than their binary switch.

Have you run into the "Both Sides" label on your own match list? Which of these scenarios turned out to be the culprit behind your tree's confusion?

If you have another workaround or tip that helped you clean up your DNA matches, we would love to hear about it and add it to our list! 🌄

If you have deep roots in the American South or the Appalachian mountains and you open up AncestryDNA, 23andMe, or MyHeritage, you are likely in for a shock.

One of the most common observations among Appalachian DNA testers is: "Why do I have so many matches?"

While the average test-taker might have a few thousand total matches, people with deep Southern or Appalachian heritage frequently log 50,000 to well over 100,000 matches, with pages upon pages of "4th–6th cousins" who look like complete strangers.

There is a perfect storm of history, geography, and biology that explains exactly why this happens. Let's break down the main reasons your genetic network is so massive.

1. The Great Migration

When people migrated out of places like Pennsylvania, Virginia, and North Carolina into the deep South and Appalachia, they didn't travel as isolated, random individuals. They traveled in highly organized family clans, church congregations, and whole neighborhoods.

Historians call this chain migration, and it acted like a genetic funnel.

Because mountains, rivers, and specific trails (like the Wilderness Road or the Great Valley Road) dictated the routes, the exact same pool of families moved together over multiple generations:

• They cleared land together in Virginia in 1750.
• Their children moved together to North Carolina by 1780.
• Their grandchildren settled the river valleys of East/Middle Tennessee or Kentucky by 1810.

The DNA Effect: Because the same pool of families stayed in close geographic proximity across multiple states and a hundred years of moving, their DNA never truly diversified. You aren't just matching people whose ancestors stayed in one county; you are matching thousands of descendants of the people who moved along that entire migration pipeline.

2. Endogamy and Pedigree Collapse

In genetics, endogamy occurs when a group of people marries within the same local population over many generations. In Appalachia and parts of the rural South, this wasn't necessarily a matter of choice; it was driven by geography.

When your ancestors settled in isolated mountain valleys, river basins, or small farming communities in the 1700s and 1800s, their marital options were limited to whoever lived within walking or horseback distance.

Because of this, families intermarried repeatedly. The Halls married the Greens, whose kids married the Bakers, whose grandkids married back into the Halls. Over 250 years, this creates pedigree collapse. Instead of having distinct branches on your family tree, the same ancestral couples appear multiple times on different branches.

This does not equate to "inbreeding" or close-cousin marriage.

Instead, it means that many families became interconnected through dozens or even hundreds of relationships over time.

The DNA Effect: When populations practice endogamy, small segments of DNA get passed down and preserved at a much higher rate than usual. You and a match might share a 15 cM segment of DNA, making you look like a 4th cousin on paper. In reality, you might actually be 7th cousins through three different lines simultaneously. The testing algorithms see that concentrated pool of shared DNA and flag them as a closer relative than they actually are.

3. High "Genetic Persistence" (The Survival of Ancient Segments)

This is where the biology gets really fascinating. Usually, every time a child is born, their parents' DNA is shuffled through a process called recombination. Over generations, this shuffling normally breaks down distant ancestral DNA into pieces so small that they disappear entirely.

But in the Southern and Appalachian gene pool, something different tends to happen: Segment Persistence.

Because the founding population was relatively small and highly interconnected, certain specific segments of DNA became incredibly stable across the entire region.

>

The DNA Effect: You carry "sticky" segments of DNA that have survived completely intact from ancestors who lived in the early 1700s—or even back in Europe. When a DNA platform scans your profile, it spots these identical segments in other testers. The algorithm assumes you share a recent ancestor (like a 4th cousin), when in reality, you both just inherited a highly resilient, ancient piece of DNA that has been bouncing around the region's gene pool for three centuries.

This persistence completely breaks many ethnicity calculators. DNA companies determine your ethnicity by comparing your DNA to modern reference panels (people living in Europe today whose families have been in the same spot for generations).

But because your Appalachian or Southern lines preserved those ancient segments, they no longer match the modern population of the exact region your ancestors actually left.

Instead, the algorithm looks at that old, un-shuffled chunk of DNA and mislabels it—often throwing your percentage into a completely different country (like assigning you heavy English or Scandinavian percentages) simply because that's where that specific, ancient genetic signature happens to show up in modern reference panels today.

In short: your ethnicity pie chart is often wrong because your DNA is a snapshot of 18th-century Europe, but the algorithm is comparing you to the 21st century.

4. Massive Family Sizes

Another thing to consider: sheer mathematics. Early pioneer families who moved into the backcountry of Virginia, North Carolina, Kentucky, and Tennessee during the 18th and 19th centuries had exceptionally large families.

It was entirely common for a single pioneer couple to have 10, 12, or even 14 children who survived to adulthood.

When you multiply those numbers across 7 to 10 generations from the mid-1700s down to today, a single colonial couple can easily have hundreds of thousands of living descendants today. If your ancestors were among these early, highly prolific lineages, you are related to an enormous percentage of the people who trace their roots to those same counties.

Why This Is Good News:

While these patterns can make research more challenging, they can also be incredibly helpful.

The more connections that exist between families, the more opportunities we have to:

• Verify relationships
• Confirm family traditions
• Identify unknown ancestors
• Solve DNA mysteries
• Break through brick walls

A DNA match that seems unrelated to your research today may become the key to solving a problem years from now.

If you have Appalachian roots and your DNA results seem unusually interconnected, you're not alone.

In many cases, the explanation isn't an error in the test.

It's history. 🌄

Between 1820 and 1930 alone, around 4.5 million people immigrated from Ireland to the United States. More than 30 million Americans—about a tenth of the total population—claim some Irish ancestry, so it’s no surprise that many people feel a kinship with the Emerald Isle and are eager to learn more about their heritage.

While many associate Irish immigration with big cities like New York, Boston, and Chicago, one group of immigrants from Ireland had a major impact on the Appalachian region.

A much earlier group from Ireland had a major impact on the Appalachian frontier. These immigrants are commonly known in America as the Scotch-Irish or Scots-Irish. Although they were part of the broader Irish diaspora, they differed greatly in their origins, their religious background, and their contributions to American culture.

The roots of the Scots-Irish story reach back to the early 1600s, during the reign of King James VI of Scotland, who also became King James I of England in 1603. After years of conflict between the English Crown and Gaelic Irish leaders, the Flight of the Earls in 1607 opened the way for the Crown to seize large amounts of land in Ulster, the northern province of Ireland.

One of James's methods for quelling rebellion was to seize land from the Gaelic (or native) Irish in the area known as Ulster and make it the property of the British crown. The goal of this scheme, called the Plantation of Ulster, was to displace the Irish population and turn the land over to Presbyterians from southern Scotland, who would work the land as sharecroppers.

>“This was a dead-end for the Scots-Irish in Northern Ireland because they were essentially powerless,” said Director of the Stephenson Center, Kathy Olson. “The new inhabitants of Ireland couldn't own land and they were required to tithe to the Anglican Church of England—not the national church of Scotland, which was the Presbyterian church.”

Many of Ulster's Scottish settlers came from the Scottish Lowlands and the Anglo-Scottish borderlands. They were largely Presbyterian, not Anglican, and many carried with them a borderland culture shaped by clan conflict, tenant farming, cattle raising, religious dissent, and suspicion of centralized authority. Over time, their descendants in Ulster became known as Ulster Scots. In America, they became known as Scotch-Irish or Scots-Irish.

Migration between Scotland and Ireland continued throughout the 1600s as the Scottish Presbyterians, the British Anglicans, and the Irish Catholics fought over land and sovereignty.

Life in Ulster was not the promised land many settlers had imagined. The Scots Presbyterians were Protestant, but they were still religious dissenters under an Anglican establishment. They faced restrictions under the Church of Ireland, paid tithes to a church that was not their own, and often remained tenant farmers rather than landowners. Economic pressures, rising rents, periodic crop failures, and religious limitations created a powerful incentive to leave.

A wave of Scottish immigrants to Ulster following a famine in the 1690s led to Scottish Presbyterians becoming the majority community; despite their numbers, however, they were denied political power. They resented the restrictions placed on them by the Church of England and turned their attention to a land that promised both economic opportunity and religious freedom.  

The 1690s brought additional hardship. Famine in Scotland pushed more migrants into Ulster. The Williamite War in Ireland, including the Siege of Derry in 1689 and the Battle of the Boyne in 1690, reinforced the political and religious divisions that would shape Ulster for generations.

By the early 1700s, many Ulster Presbyterians began looking west across the Atlantic for land, autonomy, and religious freedom.

Large-scale Scots-Irish migration to North America began in the early 1700s, especially around 1717 and 1718. Many arrived through colonial ports, then moved inland rather than settling permanently in coastal cities.

From Pennsylvania, many traveled south and west along what became known as the Great Wagon Road. This migration route carried settlers through the Cumberland Valley, the Shenandoah Valley, the Valley of Virginia, and into the Carolina backcountry, eventually feeding into the Appalachian uplands of Virginia, North Carolina, Tennessee, Kentucky, and beyond. Along the way, Scots-Irish settlers mixed with German, English, Welsh, Swiss, Dutch, African, and Native communities.

This migration pattern mattered. Much of the region was shaped by inland migration down the valleys, gaps, rivers, and old Native paths of the Appalachian backcountry.

By the 1770s, the Scots-Irish had become one of the most important populations on the colonial frontier. Estimates suggest that at least 250,000 Scots-Irish lived in the American colonies by the time of the Revolution.

The Appalachian region became a haven for those who had suffered under oppressive British rule.

Having lived through religious restrictions, land insecurity, rent pressure, and imperial control in Ulster, many Scots-Irish were deeply skeptical of centralized power. This did not mean every Scots-Irish person became a Patriot, but many frontier Presbyterian communities became strong supporters of American independence.

For this reason, many of these Scots-Irish immigrants played a fundamental role in securing an American victory during the Revolutionary War.

At the Battle of Kings Mountain, which took place in 1780 near Kings Mountain, North Carolina, descendants of Scots-Irish immigrants to Tennessee and Virginia were instrumental in defeating the opposing Loyalist forces. President Theodore Roosevelt later referred to the victory as the “turning point of the American Revolution.”

Over time, Scot-Irish culture—which is itself a blend of Scottish and Irish traditions—blended with other European, African, and Native American cultures to create the distinctive collection of folklore, art and handicraft, and cuisine that has come to represent Appalachia. However, we can still identify some cultural threads that are uniquely Scots-Irish.

>“It would not be an exaggeration to say that the Scots-Irish made the defining contribution to Appalachian culture in terms of shaping the region's cultural identity as distinct from lowland American culture in terms of language, music, religion, agriculture, etc.,” Olson said.

Bluegrass music specifically, with its strong reliance on storytelling and instruments like the fiddle, was heavily influenced by music traditions from both Scotland and Ireland. The Appalachian quilting tradition can also be traced back to Scots-Irish culture, as can the practice of making moonshine.

In the book Appalachian Home Cooking: History, Culture, and Recipes, author Mark Sohn wrote, “For the Scots-Irish, whiskey-making was linked to freedom. They came to Appalachia in search of freedom, and they brought not only their whiskey-making knowledge but also their worms and stills.”  

Several Appalachian food staples, like buttermilk and potatoes, also originated with the Scots-Irish immigrants. Even aspects of Appalachian language, like pronouncing pen and pin the same way and referring to valleys as “bottoms,” are remnants of the Scots-Irish dialect.  

The Scots-Irish were not the only people who made Appalachia, but they were one of the region’s defining populations. Their history helps explain many recurring themes in Appalachian genealogy: repeated surnames, Presbyterian and later Baptist church records, migration from Pennsylvania into Virginia and the Carolinas, movement through the Shenandoah Valley, frontier militia service, land disputes, large kin networks, and families who moved repeatedly in search of land.

For genealogists, this history matters because ethnicity estimates alone rarely explain Appalachian identity. The paper trail, migration route, church affiliation, surname cluster, neighbors, land records, and community history may tell a story that an ethnicity estimate cannot. The Scots-Irish legacy in Appalachia is not just a matter of ancestry. It is a story of migration, religion, land, conflict, adaptation, and the formation of a new regional culture in the mountains.

Sources: Lees McRae College, Library of Congress, National Museums Scotland, Discover Ulster-Scots, NCpedia, National Park Service

Last names cited in this book:

• BURNETT (198)
• SHARP (140)
• PARSONS (95)
• CLARK (72)
• RULE (62)
• PIERCE (40)
• BURNETTE (37)
• BURNET (36)
• VARNELL (30)
• PEARCE (29)
• WILLIAMS (21)
• HOUSEHOLDER (20)
• BAKER (16)
• GIBSON (15)
• BARNETT (12)
• EVANS (12)
• ANN (11)
• GATEWOOD (10)
• TROTTER (10)
• BAXTER PARSONS (9)
• BOYD (9)
• BLACK (8)
• HALL (8)
• JENKINS (8)
• SCOTT (8)
• TARWATER (8)
• FRANKLIN (7)
• KEEBLE (7)
• mc (7)
• WIFE (7)
• JOHNSTON (6)
• MARIE (6)
• ROBERTS (6)
• WILSON (6)
• BIRTHS (5)
• JANE (5)
• LEE (5)
• PARSON (5)
• SHOEMAKER (5)
• TEMPLE (5)
• ATCHLEY (4)
• BROWN (4)
• BRUCE (4)
• BURNET de LEYS (4)
• COLEMAN (4)
• COUNTY (4)
• EUGENE (4)
• INGLIS (4)
• JONES (4)
• KING (4)
• KOUNS (4)
• LYNN (4)
• MARRIAGES (4)
• MAY (4)
• mc CONKY (4)
• PIERCE DAUGHTER (4)
• PORTER (4)
• RENO (4)
• SCATES (4)
• SEIVERS (4)
• SMITH (4)
• SUE (4)
• VEITCH (4)
• WELLS (4)
• BARBER PARSONS (3)
• BARGER (3)
• BAXTER WILLIAMS (3)
• BURNARD (3)
• CHURCH (3)
• COPPOCK (3)
• CRAWFORD (3)
• DAVIS (3)
• DEATHS (3)
• GRIGSBY (3)
• HARVEY (3)
• HENDERSON (3)
• JAMES (3)
• JOHNSON (3)
• LEATHEM (3)
• LETITIA (3)
• LONES (3)
• MARGARET LETITIA (3)
• MARTIN (3)
• MATTHEWS (3)
• MAULE (3)
• MAXWELL (3)
• mc PHERSON (3)
• MURRELL (3)
• PATTERSON (3)
• PEGRAM (3)
• PORTER PARSONS (3)
• REAGAN (3)
• RIVER (3)
• ROBERT (3)
• RULE: (3)
• RUN (3)
• RUTHERFORD (3)
• SHIELDS (3)
• STUART (3)
• TURNER (3)

I have my own thoughts and opinions on this but wanted to open the board for discussion. Despite there having been a good chunk of Scottish immigration to colonial America (Scotch-Irish) if we're talking DNA results from the general area of England and Scotland, it's almost always mostly English with a little bit of Scottish. I'm flipped on that, I have significantly more Scottish ancestry than English. Which checks out with my paper trail. I got A LOT of Scotch-Irish going on. But I don't see that often. What's you guy's opinions as to why that could be? (not sharing my opinion simply because I want to see what people say that isn't just debating with me lol)