You search Ancestry's public trees for your third-great-grandfather, click View all, and there he is in dozens of trees with the wrong parents. You know they are wrong. You have the record. And you can't change a single one of those trees.
Ancestry's own help page on public trees sets out the scale: "There are over 100 million family trees on Ancestry, most of which are public." Two sentences later: "Trees created by Ancestry members are not checked for accuracy." Nobody is coming to clean this up. Our post on sources you can trust covers how one guess turns into thousands of copies. This one is about what you can do once it has.
Set the goal honestly. You will not get forty owners to edit their trees. What you can do is put the correct version, with its record, in the places the next researcher will actually look.
Fix your own tree first, and write down why.
Before you tell anyone else they are wrong, make sure the record really breaks their version and not just your assumption. The most common cause of a wrong ancestor spreading is two people with the same name in the same place, merged into one. Our guide to same-name ancestors walks through pulling them apart: ages that don't fit, a spouse who appears in both households, a man who is in two counties in the same census year.
Then write the reasoning down in a few paragraphs. The Board for Certification of Genealogists calls this a proof argument: "a detailed, written explanation of the evidence and reasoning used to reach a genealogical conclusion". Yours can be short. Say what the copies claim, which record contradicts it, and why that record outranks a tree with nothing attached. You will paste versions of this paragraph into every message, comment and reason statement that follows, so write it once and write it well.
Keep the wrong version in your notes, marked as disproven, with the reason. Hints will offer it to you again. So will well-meaning cousins. A note that says why you rejected it saves you from re-arguing the case with yourself in two years.
On Ancestry you can't edit their trees, but a comment stays put.
Before you write to anyone, click View all and look at the list. Open the trees that attach a record to the wrong fact first: those owners did some research and can be persuaded by better evidence. Trees with nothing attached copied the claim from somewhere else, and their owners are the least likely to answer, so a public comment does more there than a message.
Ancestry gives you two tools. The first is a message: select the owner's username at the top of the tree or profile page, then Message. Keep it short and specific. Name the person, the record, where to find it and the one fact it changes. Some owners copied the branch years ago without looking, and will fix it the day the evidence lands in their inbox. Some will never answer.
The second tool is a comment on the person in their tree, and it matters more than it looks. Ancestry's help page on comments says: "If your tree is public, comments about deceased people can be seen by anyone who can view the tree." The owner can hide your comment, but the same page explains what that does: "Hiding a comment removes it from your view, but other people with access to your tree can still see it." So while the tree stays public, an owner who hides your comment hides it only from themselves. It works on deceased people only, because comments about living people are private.
Write it for the stranger who arrives next, not for the owner. One or two sentences, the record and where it is held, no accusation. "The 1850 census shows two men of this name in this county; the one who married Mary was born about 1812, not 1806" will persuade a careful reader. "This is wrong, please fix" persuades no one.
Shared trees are where a correction actually sticks.
On Ancestry every tree is someone's private copy. On FamilySearch and WikiTree there is one profile per person, and that is where your fix can become the version everyone sees. Apart from a few locked historical figures, any signed-in FamilySearch user can edit a deceased person's profile, and every change is logged with the contributor's Contact ID. When you change a name, date or place, the help article asks you to "Enter a reason statement". Use your proof paragraph there, and attach the record as a source.
Read the change history before you edit. If the date has been flipped back and forth, message the people in that log first and show them the record, because a sixth flip without a conversation just becomes a seventh. Then follow the profile so you hear when it changes. Our guide to judging a FamilySearch profile covers reading that history in more detail.
On WikiTree the same logic applies with a stricter culture. Members sign an Honor Code before they edit, which commits them to real citations and civil disagreement. Explain the change on the profile itself and contact its Profile Manager before you disconnect anyone.
Make the correct version easy to find.
The copies will not disappear. What changes over time is what a careful searcher finds next to them. Keep your own Ancestry tree public with the record attached to the corrected fact. Leave the comments. Make sure the shared-tree profiles carry the source and the reason. A researcher who clicks View all and finds forty trees saying one thing and one tree saying another, with the census page attached, has a reason to open the record. That is all you need from them.
This is also the habit worth building into everything you add from now on: a fact goes on the tree with its record, or it goes on as a lead. It is the same rule behind Deep Research, which attaches the record to every fact it proposes, so a conflict shows up as two records side by side rather than as one confident date.
