National
High-prominence brands
In our 100-business pilot, AI answers supported facts about a named business more often than they mentioned that business in an unbranded search. Those are different outcomes.
Start with ChatGPT Search. We kept national, regional and local-target businesses separate before combining their results.
High-prominence brands
Multi-location organizations
Businesses targeted in local questions
ChatGPT Search · signed-in Pro · September 6, 2026 UTC. Positive answers / all answers; two runs per question per business. The percentages describe answers, not independent businesses. Business groups differ in prompts, industries and geography—not just prominence.
A supported fact about a named service is not a discovery result. And appearing in an answer is not automatically a recommendation.
Every dot below is one answer. Bright dots mark the stated outcome. The sample is still 100 businesses—not 400 independent businesses.
Two different measures, not a before-and-after test. This does not estimate how much adding a name causes an answer to change. It does not measure whole-answer accuracy.
Source: saved answer analysis v2. ChatGPT Search on Pro, September 6, 2026 UTC. 100 businesses × two runs per question type. Unresolved cases remain in the denominators.
The practical lesson is to test both questions and keep the results separate. The OpenAI API and Perplexity arms also showed more named-service fact support than unbranded target mentions, but they used different configurations and dates.
We compared later Website Readiness scores with the existing answers. There was no consistent higher-score, more-citations pattern across the three surfaces.
For ChatGPT, the lowest and highest score groups were almost level. Other surfaces differed, and the pattern changed when limited-confidence scores were removed.
These are cohort-relative bands, not universal score thresholds. Source: readiness supplement v1.
Dates are UTC. Later measurements are not snapshots of the websites at answer-collection time.
Not established does not mean “no effect.” This small, selected comparison cannot prove that readiness has nothing to do with citations—or that improving a score increases them.
The original collection-time website measurements were unavailable for this analysis. On September 9, the frozen 60 local targets received a separately dated assessment using unchanged SIGIL/λ-12 in an isolated local Worker with local Chromium and paid probes disabled. These are not recovered September 6–7 page snapshots or production-edge measurements.
The batch returned 54 numeric scores. Four assessments were unable to retrieve representative evidence; two URLs were not attempted after prior non-retryable tool safety blocks. No missing value became zero. These outcomes describe collection limitations, not judgments that the businesses are unsafe or invalid.
Saved-evidence screening retained 47 businesses for the main exploratory comparison. Seven measured cases had identity, changed-page, location or purpose-classification concerns. Their original scores remain in an all-numeric sensitivity view. The screening was AI-assisted and recorded before executing the join, but after earlier outcome review—not blinded or preregistered before outcomes were known.
The screened group’s unbranded official-site citation rates do not show a consistent higher-score/more-citations pattern across all three surfaces. That is not proof that readiness has no effect, that low scores help, or that website diagnostics have no value.
| Cohort-relative score band | Businesses | ChatGPT Search · Pro | OpenAI API · web search | Perplexity Sonar |
|---|---|---|---|---|
| ≤49 | 17 | 8/34 (23.5%) | 3/34 (8.8%) | 4/34 (11.8%) |
| >49–76 | 19 | 7/38 (18.4%) | 7/38 (18.4%) | 8/38 (21.1%) |
| >76 | 11 | 5/22 (22.7%) | 3/22 (13.6%) | 5/22 (22.7%) |
Removing limited-confidence scores leaves 44 screened businesses, including only nine in the highest score band. The higher-versus-lower citation advantage seen for the API and Perplexity in the main view no longer appears in this sensitivity view. Small cells limit interpretation; this is not a population estimate.
| Cohort-relative score band | Businesses | ChatGPT Search · Pro | OpenAI API · web search | Perplexity Sonar |
|---|---|---|---|---|
| ≤49 | 16 | 8/32 (25.0%) | 3/32 (9.4%) | 4/32 (12.5%) |
| >49–76 | 19 | 7/38 (18.4%) | 7/38 (18.4%) | 8/38 (21.1%) |
| >76 | 9 | 3/18 (16.7%) | 1/18 (5.6%) | 2/18 (11.1%) |
All seven held cases fall in the middle band, so including them changes that group without changing the low/high groups. This sensitivity preserves questionable measurements for inspection; it does not certify their identity, location or classification.
| Cohort-relative score band | Businesses | ChatGPT Search · Pro | OpenAI API · web search | Perplexity Sonar |
|---|---|---|---|---|
| ≤49 | 17 | 8/34 (23.5%) | 3/34 (8.8%) | 4/34 (11.8%) |
| >49–76 | 26 | 7/52 (13.5%) | 7/52 (13.5%) | 8/52 (15.4%) |
| >76 | 11 | 5/22 (22.7%) | 3/22 (13.6%) | 5/22 (22.7%) |
Other outcomes are not identical to citation outcomes: in the main screened comparison, Perplexity target mentions are 8/34 (23.5%) in the lowest band and 11/22 (50.0%) in the highest. Named-service fact support is lower in the highest than lowest band on all three surfaces. Neither pattern identifies the effect of improving a website.
No intervention was applied, no confounding adjustment was made for industry, geography or prominence, and the scores were measured after the answers. This supplement cannot substantiate a promise that raising a Readiness score increases citations—or the opposite claim that readiness has nothing to do with citation. A causal question needs a separate prospective design with contemporaneous measurements, repeated outcomes and an appropriate comparison group.
Run an unbranded question alongside the named-business question. A successful fact check should not substitute for a discovery test.
A mention and a citation are different. Check that the linked page belongs to the intended business and supports the claim beside it.
A website diagnostic is not proof of visibility. This study does not show that a website edit or a BoostGeo feature increases citations, traffic or revenue.
The full results are here when you want to go deeper—including other surfaces, repeated runs, uncertainties and the original report.
National / high-prominence · 20 businesses · 40 answers per question type, per surface
Positive answers / all answers; two runs per business for each question type. All denominators include unresolved cases. Source: answer analysis v2. ChatGPT: September 6, 2026 UTC; OpenAI API and Perplexity: September 7 UTC. These are different configurations, not a controlled provider ranking.
The cohort and question register were frozen before the full answer collection; the operational dry run is excluded. Each target received an unbranded discovery question without supplied target-site content and a named-business question about one service. The protocol called for new temporary conversations for consumer repetitions, without prior turns, memory or custom instructions.
Consumer ChatGPT Search: 400 records dated September 6, 2026 UTC, signed-in Pro, labeled “GPT-6, medium thinking.” Collection combined 351 human-operated captures and 49 browser-controlled captures through the consumer interface. They are disclosed as different operator modes, not different independent samples.
OpenAI API with web search: 400 records dated September 7 UTC, model identifier gpt-5.4-mini-2026-03-17. Perplexity Sonar: 400 records dated September 7 UTC, model label sonar. All preserved records report en-US and search invoked. Recorded configuration is not proof of identical search behavior or a verified physical search location.
Review was AI-assisted. All 600 named-service facts have individual review coverage. Discovery citation assessment combines 158 individual assessments with 442 deterministic checks showing no official link in the preserved answer. Discovery mention/role labels received targeted corrections, not exhaustive second individual review.
Some review passes exposed first decisions or selection context. This is not independent human double review or fully blind review. Source checks performed on September 9 are supplemental, not collection-time snapshots. Consumer transcripts have no provider finish metadata; preserved nonempty text alone does not independently prove complete interface capture.
This selected 100-business cohort is not a representative sample of businesses worldwide, all ChatGPT users, or any national business population. Repetitions increase observations, not independent businesses. Industry cells are not used for winner/loser rankings.
Six citation-support outcomes remain unknown: one unbranded and five named-business observations. They remain in the displayed denominators. A failed source check is not evidence that a business lacks the service.
One consumer named-business capture exactly duplicates a discovery response and is flagged as a possible prompt/paste mismatch, not counted as a supported primary fact. It remains in the main frozen dataset. Excluding it changes ChatGPT named-service fact support from 185/200 (92.5%) to 185/199 (93.0%); the original response is preserved and no replacement was invented.
Additional sensitivities cover a frozen name/domain mismatch, temporal branding changes, a parent/affiliate boundary, strict entity matching and unresolved citations. They are retained in the evidence package; the principal sensitivities and limitations are reported here. They do not turn this sample into a controlled experiment.
An official-site citation establishes at most a narrow nearby proposition under this rubric. It does not certify every sentence, an organization’s independence, professional credentials, treatment effectiveness or the quality of a recommendation.
An answer to “Does this business offer this service?” starts with a named target. An answer to “Which businesses offer this service in this area?” does not. These illustrative question templates test different things; neither is an exact quotation from a collected answer.
BoostGeo studied 100 businesses using a frozen discovery question and a frozen named-service question for each. Each question was run twice on three named surfaces, producing 1,200 preserved observations. The independent business sample is 100—not 1,200.
The useful distinction in this pilot is between discovery, citation and support for a specific fact. A successful named-business answer should not be treated as evidence that the business will also appear when its name is absent from the question.
The study used a purposive quota design: 20 national/high-prominence businesses, 20 regional/multi-location businesses and 60 local-target businesses. These groups are shown before the combined cohort. Their questions, industries and geographies differ, so differences are not controlled estimates of the effect of prominence.
| Surface | Unbranded target mention | Unbranded official citation | Named-service fact supported | Named-business official citation |
|---|---|---|---|---|
| ChatGPT Search · Pro | 28/40 (70.0%) | 20/40 (50.0%) | 38/40 (95.0%) | 39/40 (97.5%) |
| OpenAI API · web search | 10/40 (25.0%) | 6/40 (15.0%) | 37/40 (92.5%) | 39/40 (97.5%) |
| Perplexity Sonar | 22/40 (55.0%) | 2/40 (5.0%) | 38/40 (95.0%) | 40/40 (100.0%) |
| Surface | Unbranded target mention | Unbranded official citation | Named-service fact supported | Named-business official citation |
|---|---|---|---|---|
| ChatGPT Search · Pro | 10/40 (25.0%) | 8/40 (20.0%) | 39/40 (97.5%) | 39/40 (97.5%) |
| OpenAI API · web search | 11/40 (27.5%) | 8/40 (20.0%) | 40/40 (100.0%) | 40/40 (100.0%) |
| Perplexity Sonar | 15/40 (37.5%) | 8/40 (20.0%) | 38/40 (95.0%) | 38/40 (95.0%) |
The local-target group spans Philadelphia, San Diego, Denver, Charlotte, Nashville and Portland, Oregon. A local-target assignment describes the study’s question context; it does not guarantee the company operates in only one market. Later identity and service-area concerns remain disclosed, not silently repaired by replacing businesses.
| Surface | Unbranded target mention | Unbranded official citation | Named-service fact supported | Named-business official citation |
|---|---|---|---|---|
| ChatGPT Search · Pro | 36/120 (30.0%) | 21/120 (17.5%) | 108/120 (90.0%) | 110/120 (91.7%) |
| OpenAI API · web search | 21/120 (17.5%) | 13/120 (10.8%) | 104/120 (86.7%) | 106/120 (88.3%) |
| Perplexity Sonar | 38/120 (31.7%) | 17/120 (14.2%) | 110/120 (91.7%) | 112/120 (93.3%) |
Across all three tested surfaces, support for the named service proposition was more frequent than an unbranded mention of the target. The two columns describe different tasks—not an accuracy contest between question types or a causal benefit of naming a business.
| Surface | Unbranded target mention | Unbranded official citation | Named-service fact supported | Named-business official citation |
|---|---|---|---|---|
| ChatGPT Search · Pro | 74/200 (37.0%) | 49/200 (24.5%) | 185/200 (92.5%) | 188/200 (94.0%) |
| OpenAI API · web search | 42/200 (21.0%) | 27/200 (13.5%) | 181/200 (90.5%) | 185/200 (92.5%) |
| Perplexity Sonar | 75/200 (37.5%) | 27/200 (13.5%) | 186/200 (93.0%) | 190/200 (95.0%) |
The surfaces used different models and collection dates. These figures are observations of the recorded configurations, not a ranking of providers, a test of every current model, or an estimate for all users.
Agreement counts businesses whose two runs have matching non-null labels. Matching absence and matching “not established” count as agreement; two unknown labels do not. Agreement is not proof of correctness or stability across weeks.
| Surface | Unbranded mention agreement | Named-service fact agreement |
|---|---|---|
| ChatGPT Search · Pro | 81/100 (81.0%) | 95/100 (95.0%) |
| OpenAI API · web search | 78/100 (78.0%) | 99/100 (99.0%) |
| Perplexity Sonar | 93/100 (93.0%) | 100/100 (100.0%) |
Treat “Can it check a fact about my business?” and “Does my business appear without being named?” as separate questions. Record both outcomes instead of allowing a strong result on one to stand in for the other.
Keep the question wording, location, surface, model label, date and answer when testing. Check that a cited page belongs to the intended organization and supports the claim beside it. Repeat the same question to observe variation; do not keep only the answer you prefer.
This pilot does not demonstrate that a particular website edit, markup format or BoostGeo feature increases citations. Website Readiness measurements and observed AI-answer visibility should remain separate evidence.
The original collection-time website measurements were unavailable for this analysis. On September 9, the frozen 60 local targets received a separately dated assessment using unchanged SIGIL/λ-12 in an isolated local Worker with local Chromium and paid probes disabled. These are not recovered September 6–7 page snapshots or production-edge measurements.
The batch returned 54 numeric scores. Four assessments were unable to retrieve representative evidence; two URLs were not attempted after prior non-retryable tool safety blocks. No missing value became zero. These outcomes describe collection limitations, not judgments that the businesses are unsafe or invalid.
Saved-evidence screening retained 47 businesses for the main exploratory comparison. Seven measured cases had identity, changed-page, location or purpose-classification concerns. Their original scores remain in an all-numeric sensitivity view. The screening was AI-assisted and recorded before executing the join, but after earlier outcome review—not blinded or preregistered before outcomes were known.
The screened group’s unbranded official-site citation rates do not show a consistent higher-score/more-citations pattern across all three surfaces. That is not proof that readiness has no effect, that low scores help, or that website diagnostics have no value.
| Cohort-relative score band | Businesses | ChatGPT Search · Pro | OpenAI API · web search | Perplexity Sonar |
|---|---|---|---|---|
| ≤49 | 17 | 8/34 (23.5%) | 3/34 (8.8%) | 4/34 (11.8%) |
| >49–76 | 19 | 7/38 (18.4%) | 7/38 (18.4%) | 8/38 (21.1%) |
| >76 | 11 | 5/22 (22.7%) | 3/22 (13.6%) | 5/22 (22.7%) |
Removing limited-confidence scores leaves 44 screened businesses, including only nine in the highest score band. The higher-versus-lower citation advantage seen for the API and Perplexity in the main view no longer appears in this sensitivity view. Small cells limit interpretation; this is not a population estimate.
| Cohort-relative score band | Businesses | ChatGPT Search · Pro | OpenAI API · web search | Perplexity Sonar |
|---|---|---|---|---|
| ≤49 | 16 | 8/32 (25.0%) | 3/32 (9.4%) | 4/32 (12.5%) |
| >49–76 | 19 | 7/38 (18.4%) | 7/38 (18.4%) | 8/38 (21.1%) |
| >76 | 9 | 3/18 (16.7%) | 1/18 (5.6%) | 2/18 (11.1%) |
All seven held cases fall in the middle band, so including them changes that group without changing the low/high groups. This sensitivity preserves questionable measurements for inspection; it does not certify their identity, location or classification.
| Cohort-relative score band | Businesses | ChatGPT Search · Pro | OpenAI API · web search | Perplexity Sonar |
|---|---|---|---|---|
| ≤49 | 17 | 8/34 (23.5%) | 3/34 (8.8%) | 4/34 (11.8%) |
| >49–76 | 26 | 7/52 (13.5%) | 7/52 (13.5%) | 8/52 (15.4%) |
| >76 | 11 | 5/22 (22.7%) | 3/22 (13.6%) | 5/22 (22.7%) |
Other outcomes are not identical to citation outcomes: in the main screened comparison, Perplexity target mentions are 8/34 (23.5%) in the lowest band and 11/22 (50.0%) in the highest. Named-service fact support is lower in the highest than lowest band on all three surfaces. Neither pattern identifies the effect of improving a website.
No intervention was applied, no confounding adjustment was made for industry, geography or prominence, and the scores were measured after the answers. This supplement cannot substantiate a promise that raising a Readiness score increases citations—or the opposite claim that readiness has nothing to do with citation. A causal question needs a separate prospective design with contemporaneous measurements, repeated outcomes and an appropriate comparison group.
The cohort and question register were frozen before the full answer collection; the operational dry run is excluded. Each target received an unbranded discovery question without supplied target-site content and a named-business question about one service. The protocol called for new temporary conversations for consumer repetitions, without prior turns, memory or custom instructions.
Consumer ChatGPT Search: 400 records dated September 6, 2026 UTC, signed-in Pro, labeled “GPT-6, medium thinking.” Collection combined 351 human-operated captures and 49 browser-controlled captures through the consumer interface. They are disclosed as different operator modes, not different independent samples.
OpenAI API with web search: 400 records dated September 7 UTC, model identifier gpt-5.4-mini-2026-03-17. Perplexity Sonar: 400 records dated September 7 UTC, model label sonar. All preserved records report en-US and search invoked. Recorded configuration is not proof of identical search behavior or a verified physical search location.
Review was AI-assisted. All 600 named-service facts have individual review coverage. Discovery citation assessment combines 158 individual assessments with 442 deterministic checks showing no official link in the preserved answer. Discovery mention/role labels received targeted corrections, not exhaustive second individual review.
Some review passes exposed first decisions or selection context. This is not independent human double review or fully blind review. Source checks performed on September 9 are supplemental, not collection-time snapshots. Consumer transcripts have no provider finish metadata; preserved nonempty text alone does not independently prove complete interface capture.
This selected 100-business cohort is not a representative sample of businesses worldwide, all ChatGPT users, or any national business population. Repetitions increase observations, not independent businesses. Industry cells are not used for winner/loser rankings.
Six citation-support outcomes remain unknown: one unbranded and five named-business observations. They remain in the displayed denominators. A failed source check is not evidence that a business lacks the service.
One consumer named-business capture exactly duplicates a discovery response and is flagged as a possible prompt/paste mismatch, not counted as a supported primary fact. It remains in the main frozen dataset. Excluding it changes ChatGPT named-service fact support from 185/200 (92.5%) to 185/199 (93.0%); the original response is preserved and no replacement was invented.
Additional sensitivities cover a frozen name/domain mismatch, temporal branding changes, a parent/affiliate boundary, strict entity matching and unresolved citations. They are retained in the evidence package; the principal sensitivities and limitations are reported here. They do not turn this sample into a controlled experiment.
An official-site citation establishes at most a narrow nearby proposition under this rubric. It does not certify every sentence, an organization’s independence, professional credentials, treatment effectiveness or the quality of a recommendation.
BoostGeo designed and conducted this pilot and sells website-analysis and AI-visibility software. That commercial interest should be considered when interpreting the report. The study is not evidence that using BoostGeo improves citations, traffic or business outcomes.
This report publishes aggregate findings, chart data and methodology without named-business scores, rankings, raw answers or source URLs. Raw captures, frozen registers, hashes and reviewer decisions are retained internally for audit; they are not included in public downloads to avoid identifiable business-outcome joins and unnecessary reproduction of third-party content.
Published September 10, 2026. BoostGeo is the editorial and corrections owner. Collection and AI-assisted evidence review are described above; this is not a claim of peer review or independent human double coding. Version 1 retains the questionable capture in the main denominator and reports the exclusion sensitivity. Material corrections will be dated here.
BoostGeo designed and conducted this pilot and sells website-analysis and AI-visibility software. That commercial interest should be considered when interpreting the report. The study is not evidence that using BoostGeo improves citations, traffic or business outcomes.
This report publishes aggregate findings, chart data and methodology without named-business scores, rankings, raw answers or source URLs. Raw captures, frozen registers, hashes and reviewer decisions are retained internally for audit; they are not included in public downloads to avoid identifiable business-outcome joins and unnecessary reproduction of third-party content.
Published September 10, 2026. BoostGeo is the editorial and corrections owner. Collection and AI-assisted evidence review are described above; this is not a claim of peer review or independent human double coding. Version 1 retains the questionable capture in the main denominator and reports the exclusion sensitivity. Material corrections will be dated here.
For a correction or methodology question, contact BoostGeo and identify the finding concerned.
Download aggregate chart data (JSON)
Download methodology and limitations (text)
Suggested attribution: “BoostGeo, AI Search Visibility: 100-Business Study (2026).” Link to this report and retain its sample and date qualifications.
Published September 10, 2026 · Version 1. Report a correction.
The 1,000-site Website Readiness study examines captured homepage evidence. This pilot examines public AI answers about a separate 100-business cohort. Neither substitutes for the other.
Explore AI Visibility · Read the practical GEO guide · All BoostGeo research