FamilyTreeDNA Appears in 69.2% of AI Answers. Here's Our Five-Step Plan to Improve Its AI Visibility.

Answer Capsule

In November 2026, FamilyTreeDNA appeared in 388 of 561 AI answers included in the DNA Testing Kits benchmark (69.16%). It received 205 recommendations (36.54%), with 100 Top 3 placements and 3 first-place recommendations. A mention means the company appeared in an answer; a recommendation means the answer affirmatively endorsed it.

Our plan compares the company with its competitors, checks conflicting AI claims against reliable sources, and identifies website pages, third-party sources and buyer questions to address. The historical results show how the figures changed across available months. Different monthly samples limit those comparisons, and conflicting AI claims require verification before corrections are proposed.

Current AI visibility

Questions This Section Answers

• How do FamilyTreeDNA mentions, recommendations and placements compare with its DNA Testing Kits peers?

FamilyTreeDNA recorded 388 mentions (69.16%) and 205 recommendations (36.54%) across 561 answers included in the benchmark. Top 3 placements numbered 100; first-place recommendations numbered 3. Framing among its mentions was 221 positive, 167 neutral and 0 negative.

FamilyTreeDNA is named in most answers and recommended in a substantial share, so the brand is clearly on the shortlist. The gap sits in position: it rarely takes first place, and its shortlist presence is far larger than its top placements. Reach and endorsement are different measures, and the endorsement rate should not be read as conversion.

For the agency, this points to a positioning problem rather than an awareness problem. Proposed work would examine which buyer questions produce recommendations without first place, then build briefs that give the company a clearer reason to be named first.

What changed since last month

Questions This Section Answers

• How did FamilyTreeDNA counts and coverage differ across the available monthly snapshots?

From October 2026 to November 2026, FamilyTreeDNA's mention count fell from 426 to 388, while its recommendation count fell from 325 to 205. The recommendation rate was 57.73% and 36.54% respectively.

The November sample shows fewer mentions and a markedly lower recommendation rate than October. Top-three placements also eased, while first-place counts stayed very low in both months. The movement is worth watching, but the monthly samples are separate selections, so the difference in answer totals does not explain the change in counts or rates.

The agency would treat this as a signal to investigate, not a conclusion. Proposed work includes checking whether the drop concentrates in particular question types or services, and comparing the wording of recommending answers against those that only mention the company.

Step 1. Measure

Questions This Section Answers

• What should the agency measure and verify first for FamilyTreeDNA?

AI answers contained 4 conflicting claims about FamilyTreeDNA: 0 critical, 0 high, 3 medium, 1 low. Of these, 0 were rated critical or high priority; the critical claims are included in that total. These ratings help prioritize fact-checking. They do not establish that a company or publisher made an error.

The recorded answers contain a small set of conflicting claims about FamilyTreeDNA, mostly rated medium priority. Those ratings are a triage aid for fact-checking; they do not show that the company or any publisher made an error. The first useful step is a visibility comparison that shows where the company is named, recommended and placed first.

Alongside it, the agency would build a claim list with an owner and an evidence requirement for each item. That lets the client decide what to verify first rather than reacting to every discrepancy at once.

Step 2. Make the website consistent

Questions This Section Answers

• Which recorded claim differences about FamilyTreeDNA should be verified before proposed page edits?

Both columns quote AI answers, not verified company facts. Resolve the entity, date and source before deciding whether a correction is warranted; different dates can explain an apparent conflict.

The disputed topics cluster around raw data upload fees, whether ethnicity refinement carries a charge, how Y-DNA and mtDNA testing is described, and database size. Both recorded versions are AI claims, not verified facts, and different dates could account for an apparent conflict. Entity and date need resolving before any correction is considered.

The agency would verify each topic against current primary sources and prepare conditional page briefs. Where the company's own wording is confirmed, a brief would set out clearer language; where it is not, the item stays open rather than entering a correction queue.

Step 3. Align the external narrative

Questions This Section Answers

• Which cited third-party pages are relevant to fact review for FamilyTreeDNA?

These pages were selected because they relate to the company in the captured answers. Their current contents still need checking before any correction request. A page linked to a conflicting claim is not necessarily its cause, and the same answer may contribute to more than one row.

Several cited pages appear repeatedly alongside FamilyTreeDNA in the captured answers, including a buying guide and a video review. Citation does not establish that a page influenced an answer, and a page linked to a conflicting claim is not necessarily its cause. Current contents still need checking before any request is made.

The agency would review the most relevant pages first, confirm what they currently say, and prepare evidence-backed requests only where a genuine discrepancy is found. Publisher responses and no-change decisions would be recorded separately.

Step 4. Optimize priority company pages

Questions This Section Answers

• Which observed FamilyTreeDNA website pages should receive review briefs?

The company's website was cited 125 times across 44 distinct page addresses; the table shows 8 pages selected for review. Zeros in the answer columns mean no matching answers were recorded. A cited page is not automatically a page that accompanied a recommendation.

The company's own site is cited across many pages, with the homepage and the autosomal upload pages appearing most often. Citation counts differ from the number of answers that recommend the company, so a cited page is not automatically one that accompanied an endorsement. The listed pages are a starting shortlist, not a verdict on their content.

The agency would draft page briefs using approved facts and the questions buyers actually ask, then check existing coverage before proposing anything new. Pages with no recorded recommending answers would be reviewed for clarity rather than assumed to be weak.

Step 5. Publish around buyer questions

Questions This Section Answers

• Which observed buyer questions support content briefs for FamilyTreeDNA?

These are recorded answer observations, not search volume, verified demand, or proof of missing website content.

The observed questions centre on accuracy, heritage discovery, family-tree research and regional suitability, including Middle Eastern ancestry. These are recorded answer observations, not search volume or proof of missing website content. FamilyTreeDNA is mentioned in most of these answers and recommended in many, so the opportunity is to sharpen how it is described rather than to assume absence.

The agency would check existing coverage for each question, then prepare content briefs that answer the buyer's actual comparison directly. Each brief would use approved facts and avoid claims the company cannot support.

Our 90-day action plan

Questions This Section Answers

• How should the agency sequence the proposed FamilyTreeDNA work and judge completion?

The first month establishes the baseline scorecard, a scoped fact-review register and a shortlist of pages and sources, each with an owner and review status. The second month turns confirmed findings into approved page briefs and justified publisher requests, with edits, no-change decisions and responses recorded separately.

The final month produces buyer-question content briefs and a fresh scorecard. Completed work would be reported separately from measured answer outcomes, and no visibility gain would be promised, since the samples and answer behaviour limit what can be attributed.

Methodology

Questions This Section Answers

• How are FamilyTreeDNA answer metrics and citation populations defined?

This report covers 2026-11. The exact dates when the original AI answers were collected have not been verified. The visibility rates use 561 answers that met the benchmark's inclusion rules. A company is recommended only when the answer both endorses it and uses positive wording. Top 3 and first-place counts are part of those recommendations, not extra recommendations.

An answer can mention or recommend several companies, so company counts cannot be added to find the number of distinct answers. The net sentiment score is positive minus negative mentions, divided by all company mentions; it describes answer wording, not customer satisfaction.

The wider citation analysis covers 800 captured answers and 5891 appearances of cited URLs. Citation appearances across all captured answers differ from the number of benchmark answers citing a page and the number that also recommend a company. The current contents of cited pages and disputed company claims still need independent verification.

Monthly sample coverage:

The answer samples differ between months. These comparisons show how the recorded results changed; they do not establish why they changed.

The report covers a single month, and the exact dates the answers were collected have not been verified. A company counts as recommended only when an answer endorses it with positive wording; top-three and first-place counts sit inside those recommendations rather than adding to them. Answers can name several companies, so company counts cannot be summed into distinct answers.

Monthly samples differ, so comparisons show how recorded results changed, not why. Cited pages and disputed claims still need independent verification.

Our first three priorities

First, verify the disputed fee, testing-availability and database-size claims against current primary sources before any correction is considered, and keep ambiguous matches out of the queue. Second, review the most-cited external pages for what they currently say, then prepare evidence-backed requests only where a real discrepancy is confirmed.

Third, build page and buyer-question briefs around accuracy, heritage and family-tree comparisons, checking existing coverage first. Throughout, the agency would keep completed work separate from measured visibility, since the monthly samples cannot show that any change came from the work itself.