Skip to content

AI search visibility versus SEO, explained through measured answers

Our July 2026 study logged 5,160 citations across 1,753 unique domains in 860 answers about 85 software companies on one engine. Read the dated evidence.

Most comparisons of these two things are definitional. This comparison draws on three published datasets. Sources and verification limits are stated beside the findings. Broadcastwell sells GEO work, which is a reason to read the method section, and a reason we put the DOIs on the page.

0.313
mean pairwise agreement between engines
63.3%
1,416 of 2,238 vendor mentions, one engine only; 142 questions. Interval not reported in the published source.
92.1%
258 of 280 buyer questions triggered an answer in Google AI Overviews. Interval not reported in the published source.
SEO competes for a position that always exists. AI search visibility competes for a mention that may not exist for anyone.

That sounds like a phrasing difference and it is not. A ranked list has ten slots and somebody fills all of them. A generated answer names whoever the engine decided to name. A vendor can be absent from that answer.

Data table: Question, Ranking, Being named
QuestionRankingBeing named
What the surface isAn ordered list of linksA written answer that names a few vendors
What you occupyA position, which always exists for someoneA mention, which may exist for nobody
How many winTen slots, ranked, all visibleBetween three and fifteen names, unranked, depending on the engine
What the unit isRank for a keywordNamed or not named, out of a question set someone chose
Who decidesOne index per engine, broadly stable between checksRetrieval plus generation, and the same question can return a different set of firms
What a source doesA link earns authority that lifts a pageA source can be cited in an answer that names someone else

Answer lengths in the third column are measured, not illustrative. See section 03.

The practical consequence is that the two disciplines optimise against different feedback. Rank moves in small increments and is broadly stable between checks. A named count is a proportion out of a denominator you chose, and it can move for reasons that have nothing to do with anything you did. Reporting the second like the first is where most of this category's overclaiming comes from.

In classical search, checking two engines mostly tells you the same thing twice. In generated answers it does not.

Volume III scored 853 answers and computed vendor-set agreement across every engine pair. The mean pairwise Jaccard was 0.313, with a 95 percent confidence interval of 0.295 to 0.330, over 590 pair observations. On the three-engine subset of 142 questions carrying 2,238 vendor mentions, 63.3 percent of mentions were made by exactly one engine and only 17.5 percent by all three. Of 32 companies testable on two or more engines, 14 were visible on some and invisible on others. Vendor-mention shares: 1,416 of 2,238 from one engine and 392 of 2,238 from all three, across 142 questions. Interval not reported in the published source.

That is the single most consequential difference from SEO for a buyer of these services. A one-engine report is not a category reading. It is a reading of one engine, and the odds are close to even that another engine names a different set of firms entirely.

The 2026 State of Generative Engine Optimization, Volume III. DOI 10.5281/zenodo.21789120.

Volume III initially suggested that engines disagree with each other about twice as much as they disagree with themselves. After controlling for answer length, the conclusion held for Google AI Overviews but not for Claude. That distinction belongs in any responsible reading of cross-engine divergence.

Data table: Engine, Vendors named per answer
EngineVendors named per answer
Google AI Overviews4.8
Claude8.8
Perplexity10.7
ChatGPT14.7

ChatGPT's figure rests on 18 answers. Treat it as indicative. Volume III, DOI 10.5281/zenodo.21789120.

Engines name very different numbers of vendors. An engine compared with itself is length-matched by construction. Two different engines are not, and Jaccard between similar-sized sets runs mechanically higher. So part of any raw within-versus-between gap is an artefact of list length rather than a real disagreement.

Controlling for it separated the two results. Google AI Overviews held: a gap of plus 0.258 on raw Jaccard, and plus 0.193 on an overlap coefficient normalised by the smaller set. Claude did not: plus 0.165 raw fell to plus 0.002 on the overlap coefficient, which is not significant. The honest conclusion is that divergence is engine-specific, and that any cross-engine divergence number published without a length control is suspect. That includes conclusions that look stronger before the control is applied.

A common instinct carried over from link building is to find the sites the engines cite and get onto them. The measured shape of the citation pool makes that mostly unworkable.

In Volume I, the top ten domains accounted for 609 of 5,160 citations (11.8%). The study was collected 18 to 23 July 2026. Volume III used a different question set on 4 August 2026.

Volume I DOI 10.5281/zenodo.21537014; Volume III DOI 10.5281/zenodo.21789120. Compare each study with its own recorded base and method.

Read the deposited Volume III results.

Which sources matter is category-specific. The per-stat figures are on the statistics page.

A search-result link and a visit are separate events. Likewise, a citation in a generated answer does not establish that a user or engine visited the source.

An answer can cite a vendor domain without naming that vendor. Citation and naming counts describe different observed outcomes.

The current measurement protocol is on the methodology page, with its scope and limitations. This commercial page uses the general finding: source inclusion and vendor recommendation must be scored separately.

The practical test for any tool or agency in this category: ask whether it reports a named count beside its citation count. A citation count alone does not establish whether a vendor was named, or whether leads or revenue changed.

Carries over: being indexable. Retrieval runs over indexed pages. Crawlability, clean markup, sane information architecture and a site that loads all still matter, because a page an engine cannot read cannot be quoted.
Carries over: publishing things worth quoting. Specific, checkable material with numbers attached is what gets quoted. This is the part of content marketing that survives the transition mostly unchanged.
Does not carry over: rank as the unit. An answer can contain an ordered recommendation, but that position is specific to the observed answer and differs from a search-result rank. Our method records position only when an answer has a discernible order.
Does not carry over: one engine as a proxy. At 0.313 mean pairwise agreement, one engine is not a reading of the category. Five engines is the minimum we work to, and the same wording has to go to all of them.
Does not carry over: a single check. A single check is a sample, not a coordinate. Repeat the same questions on the same engines and report the range.
What was measured. Volume III collected 853 scored answers from 631 searches on 4 August 2026 across ChatGPT, Claude, Perplexity and Google AI Overviews. Current engagements run under method v1.1, described on the methodology page.
Withdrawn agency measurement. Earlier July 2026 agency mention counts have been withdrawn because the underlying answer records could not be reverified. This page makes no claim about how often an AI engine names an agency.
Coverage is uneven and stated. In Volume III, the collection covered 280 questions. Google AI Overviews returned 280 answers, Claude 273, Perplexity 175 and ChatGPT 18. These are the coverage counts reported for 4 August 2026. The ChatGPT figures on this page rest on that small base and are labelled where they appear.
What this does not prove. None of it establishes why an engine names anyone. It describes what was returned. It also describes specific categories over specific windows, which is the reason to measure your own rather than borrow these.
Not peer reviewed. Volume I, DOI 10.5281/zenodo.21537014. Volume II, DOI 10.5281/zenodo.21586091. Volume III, DOI 10.5281/zenodo.21789120. Each carries its data and analysis code. Published open access under CC BY 4.0. Not peer reviewed.
Commercial disclosure. Broadcastwell publishes this page and provides the services described here. Research findings, editorial analysis and commercial claims are clearly separated.

What is the difference between AI search visibility and SEO?

SEO competes for a position in an ordered list of links, and a position always exists for somebody. AI search visibility competes to be named inside a written answer that mentions a handful of vendors and may name nobody at all. The unit of measurement is different: rank for a keyword versus named or not named, out of a question set someone chose. That is why a site can rank respectably and be absent from every answer in its category.

Does AI search visibility replace SEO?

No, and the two are not independent either. Retrieval still runs over indexed pages, so being findable remains a precondition. What changes is that being findable stops being sufficient. In our Volume III collection a Google AI Overview appeared on 92.1 percent of 280 buyer questions, an observed 258 of 280 questions in this sample. Interval not reported in the published source.

Can we just get onto the sites AI engines cite?

In Volume I, the top ten domains held 609 of 5,160 citations (11.8%). Which sources matter remains category-specific. Read the deposited results and each study method before comparing samples.

Do all AI engines give the same answer?

No. Across 590 engine-pair observations the mean pairwise Jaccard agreement on vendor sets was 0.313, with a 95 percent confidence interval of 0.295 to 0.330. On the three-engine subset, 63.3 percent of the 2,238 vendor mentions were made by exactly one engine and only 17.5 percent by all three. Of 32 companies testable on two or more engines, 14 were visible on some and invisible on others. Vendor-mention shares: 1,416 of 2,238 from one engine and 392 of 2,238 from all three, across 142 questions. Interval not reported in the published source.

Is being cited the same as being recommended?

No. An answer can cite your domain while naming a competitor. A citation count alone does not establish whether a vendor was named, or whether leads or revenue changed.

How should we read a divergence statistic from any vendor?

Ask whether it was length-controlled. Engines name very different numbers of vendors per answer, from about 4.8 to about 14.7 in our collection, and Jaccard between similar-sized sets runs mechanically higher. The Claude result of plus 0.165 raw fell to plus 0.002 and lost significance once normalised by the smaller set. A divergence number published without that control is not yet a finding.

One buyer question. One completed repair.

We build one source-backed page or fix for $490. Choose Live or Handoff before payment. We confirm Ready within 60 minutes during business hours. If anything is missing, a member of our team contacts you directly and finishes it with you. The deadline is 48 elapsed hours after recorded Ready.

If we miss the deliverable or deadline, we initiate a full $490 refund within five business days. You keep the work. You may also request a full refund within 30 days of delivery.

Fix one answer, $490

One buyer question. One completed repair.

We build one source-backed page or fix for $490. Choose Live or Handoff before payment. We confirm Ready within 60 minutes during business hours. If anything is missing, a member of our team contacts you directly and finishes it with you. The deadline is 48 elapsed hours after recorded Ready.

If we miss the deliverable or deadline, we initiate a full $490 refund within five business days. You keep the work. You may also request a full refund within 30 days of delivery.

Fix one answer, $490