Open Dataset

Measured US AI answer-surface visibility, published as a dataset.

This is the United States board: what every answer surface gave back when we put the same 50 buyer questions to each of them from New York, and which domains those answers cited. Each figure sits next to the number of runs it was measured against, and you are welcome to use any of it — in an article, a deck or a study — as long as you name the source.

50 questions15 engines17 surfaces Get your free AI visibility check

What an unciteable number costs. Without a denominator and a date, a figure you quote in an article or a board pack is a risk you inherit from whoever produced it. Every row here comes with the date it was measured and the number of valid runs behind it, which is the reason you can reuse this release and defend it.

The second cost is slower and worse. Without open figures, a market argues from vendor decks for years, and a buyer who wants to be careful has no neutral ground to stand on — so careful buyers lose to confident sellers. Publishing the rows is the cheapest way we know to change that.

Method, sample, limitations

Method

We put one set of buyer-style questions to every answer surface in the panel and recorded what came back: whether the surface answered at all, and which domains it cited. Valid runs differ by surface, so each surface carries its own denominator and we never pool or compare rates across them. Execution details — the wording of the questions and the judgment configuration — stay private; only the aggregates are published.

Sample

50 questions put to 14 answer surfaces from New York on 2026-07-27: 700 planned runs, 695 of them valid. A second block from the same run pools citations across 15 surfaces — 8662 citations in all, from 50 questions at 1 pass per question.

Measured on our sampled query panel — the questions are ours, so the figures can differ from Naver's own internal counts.

Limitations

This run went one pass per question. That answers what each surface returned and how wide its citation pool was. A ranked citation ladder needs a deeper sample, so that row stays empty and states what it is waiting for. The second block counts every citation handed out, so its numbers sit on a different denominator from the per-observation rates other boards publish. These are surfaces observed in one city on one day, so do not generalize beyond the measured scope. Per-surface denominators are printed next to the table.

Why anyone publishes measured numbers here

Nearly every figure circulating about AI search visibility traces back to a vendor deck, and the trail stops there. No denominator, no window, no way to recompute it. Cite one in an article or a board pack and you have borrowed a number you cannot defend, which is a professional risk that lands on you, never on whoever produced it.

This release is the alternative. Every count sits next to the runs it came from, and denominators that differ by surface are never pooled. Where a figure has not been measured well enough to publish, the row stays empty and carries its reason. Where a number has already appeared on one of our research pages, that page is linked at the bottom, so a reader who wants to argue with us has somewhere to start.

Reuse it freely, with attribution. A company that sells measurement should be the easiest one in its market to fact-check, and the same protocol runs behind our commercial panels — 50 questions, 15 engines, 7 runs each.

50

buyer questions, each one asked of every surface in the set

Measured in New York, 2026-07-27

14

answer surfaces watched in one pass, each with its own valid-run count

695 valid runs of 700 planned

8662

citations those answers handed out, pooled across the surface set

1987 separate domains among them

Download as JSON

Version v1 · US market · updated 2026-08-10 · free to cite with attribution. Boards for the other markets we measure sit at /data/index.json.

14 US answer surfaces, and what each one gave back

Measured 2026-07-27 from New York. 50 questions × 1 pass, 700 planned runs. A run counts as valid when the surface returned an AI answer or a result set. Runs where nothing came back stay out of the denominator.

US answer surfaces — valid runs and unique cited domains
SurfaceValid runsUnique cited domains
Perplexity50436
Google Search50263
Bing News5081
Yahoo Search50239
Bing Search50157
YouTube501
ChatGPT50141
Google AI Mode50503
Google short-form video5011
Grok50186
Bing Copilot50363
Google News50635
Claude4914
DuckDuckGo search assist4674

Ranked citation ladder — held until the sample matches

single pass per query — 50 valid observations on the widest surface against the 343 that back the KR and JP ladders. Publishing a ladder on this sample would put a seven-times-smaller denominator under the same heading.

What lifts it: re-run the same 50-query US panel with 7 repeats per query on one surface, as KR and JP were measured.

Which domains US AI answers actually cite

Same run, 2026-07-27, counted a different way: every citation handed out across 15 surfaces, pooled into one list. 8662 citations in total from 50 questions.

Unit: citations pooled across 15 surfaces (denominator: 8662 citations, single pass) — not comparable with the per-observation share used by the KR and JP ladders.

Most-cited domains, pooled across US answer surfaces
DomainCitations
youtube.com1152
semrush.com318
linkedin.com189
instagram.com154
searchenginejournal.com117
reddit.com102
facebook.com92
forbes.com80
explodingtopics.com75
searchengineland.com74
Separate domains cited at least once1987

How to check these numbers yourself

A figure on its own is hard to cite safely, so the conditions it came from and the version history sit right next to it.

Query design — how many questions, asked how many times · Measurement settings — to re-measure on the same spec · Version history — what changed, and when

Query design — how many questions, asked how many times

Each block carries its own question count and repeat count. The table shows what was actually run.

United States panorama, single pass — surface denominators; citation ladder not yet measured 2026-07-27
Query design — how many questions, asked how many times 
Query panel50
Repeats per query1
Planned runs700
Valid observations695
Answer surfaces14
Measurement cityNew York
United States — cited domains pooled across answer surfaces (already published) 2026-07-27
Query design — how many questions, asked how many times 
Queries50
Answer surfaces15
Passes per query1
Total citations8662

The design is what we publish. Question wording and the order they go in travel inside the contract.

Measurement settings — to re-measure on the same spec

Settings that hold across this whole version. The same values ship inside the JSON and CSV downloads.

Measurement settings — to re-measure on the same spec 
MarketUS
Measurement window2026-07
Versionv1
Updated2026-08-10
Blocks2
Schemaciteangle-open-aggregates.v1

Rates carry a Wilson 95% confidence interval. Download the files above and rerun the same formula yourself; the denominator is the observation count in each block's design table.

Version history — what changed, and when

Check here which version a figure you cited belongs to. When a version ships, this list grows first.

  1. v12026-08-10Current

    First publication. The opening version of the US board, carrying 2 measured blocks.

Sources

Figures that already appeared on one of our pages are listed here. When you cite the dataset, please cite the original page as well. A source written in another language carries its language code, and the link opens that original.

  1. US AI cited-domain landscape — what US AI answers actually cite published 2026-08-03

How to cite

Suggested form: CiteAngle, "CiteAngle Open Aggregates: US AI Answer-Surface Visibility, v1 (2026-07)", citeangle.com — with a link to this page. Aggregates are free to redistribute; the underlying sealed run artifacts, query panels and judgment configurations are not part of the release.

Download as JSON

Want your own brand measured on a grid like this? Start with the free visibility check.

Some releases ship as JSON only, with no page of their own. The full list sits at /data/index.json, including the AI answer-surface aggregates our measurement engine produces on its own.

Ready to turn US visibility evidence into a market plan? Tell us the US buyer, target state and decision date.

Request a written proposal