Methodology — version 1.0


Version 1.0Updated
Frozen version

This version stays frozen for the whole of any data collection that uses it. Every change produces a new version, published before the collection that uses it and recorded in the version log at the bottom of this page.

In short. Visibilitas measures how often businesses, professionals and creators are named in the answers of AI assistants. It does so by submitting a fixed set of questions to 6 engines, several times and within a declared period, and by recording full answers and sources. The methodology — questions included — is published before each data collection and does not change while collection is under way. This page describes what we measure, how, and within which limits.

01What do we measure?

We measure presence: whether, how often and in what way an entity (a business, a practice, a professional, a news outlet, a journalist, a creator) is named in the answers that AI engines give to questions asked by a generic user in the market a report covers. A "mention" is a recognizable reference to the entity in the text of an answer; sources (the links the engine attaches) are recorded separately.

Rankings measure presence in the answers of AI engines. They do not confer titles, credentials or any judgment of professional quality.

02Which engines do we query?

EngineProviderHow it builds the answerCites sources
ChatGPTOpenAIModel only: answers from what it has learned, without searching the webNo
ChatGPT SearchOpenAISearches the web at the moment of the questionYes
GeminiGoogleModel grounded in Google Search resultsYes
Google AI OverviewsGoogleAI summary generated above the search resultsYes
PerplexityPerplexity AIAnswer engine built on web searchYes
CopilotMicrosoftAssistant with built-in Bing searchYes

The distinction between ChatGPT and ChatGPT Search matters. The first shows what the model learned during training; the second shows what it finds on the web at the moment of the question. An entity that appears only in the search-enabled modes is visible but not yet learned by the model; an entity named by the model alone has entered its knowledge. This is why the two modes are counted separately.

If an engine cannot be reached, or delivers no answers during the collection period, the report says so, with the number of missing answers. Missing data is never estimated or interpolated.

03Which questions do we ask?

Each report uses a fixed set of prompts, designed to mirror the way people actually ask an AI assistant for a recommendation: by category, by city, as a direct request and as a concrete problem. The number of prompts and their complete list are part of the report's frozen protocol, and are published in the dataset before collection begins.

The prompts:

  • are written in the language of the market the report covers, from the point of view of a generic user (no personal account, no history);
  • never name a specific entity (no "tell me about Business X" in a ranking collection);
  • stay identical from one report to the next within the same series; any change produces a new version of the methodology, published before the report that uses it.

Rankings of news outlets, journalists and creators

Some reports rank the outlets, journalists and creators of a field (for example artificial intelligence) instead of businesses. For these reports:

  • each category uses one plural question, for example "Who are the most authoritative journalists covering artificial intelligence in the United States?", repeated many times rather than reworded many ways;
  • the question never asks for a number of names: the engine answers with the list it chooses, because asking for a fixed number pushes engines to fill the list with invented names;
  • when a question uses a word such as "authoritative", the result is always attributed to the engines: a ranking shows whom AI engines name when they are asked that question. It is not a judgment by Visibilitas, and we do not measure authority itself.
The six engines queried and their statusEvery month, the same fixed set of prompts is submitted to six engines: ChatGPT and ChatGPT Search by OpenAI, Gemini and Google AI Overviews by Google, Perplexity, and Copilot by Microsoft. At version 1.0 of the methodology all six are queried and none is suspended. Only ChatGPT answers without citing sources. The same data is in the table “Which engines do we query?” above.EVERY REPORTPROMPTSFixed setCADENCEMonthlyChatGPTOpenAIno sources citedChatGPT SearchOpenAIcites sourcesGeminiGooglecites sourcesGoogle AI OverviewsGooglecites sourcesPerplexityPerplexity AIcites sourcesCopilotMicrosoftcites sourcesqueriedsuspended — none at version 1.0

Data is collected monthly. The methodology in force is frozen and published before each collection. Declared status of each engine at version 1.0. An engine that cannot be reached during the collection period is declared suspended in the report, with the number of missing answers: missing data is never estimated.

04How do we collect the answers?

  • Collection uses our own tools and specialized third-party platforms for monitoring AI engines, selected to keep collection across the different engines as simultaneous as possible within the declared period.
  • Visibilitas checks and verifies the collected data continuously, keeps complete raw copies and publishes them: responsibility for the published data rests entirely with Visibilitas, whatever collection tool was used. Any error report is addressed to us, through the correction procedure.
  • Location: the country of the report (United States for US reports), and the city or metro area named in the prompt when the question is local. Language: the language of the market.
  • Repetition: each prompt is submitted to each engine several times, on different days within the declared period. The number of repetitions is stated in every report. A single answer is an anecdote; recurrence is a measurement.
  • Collection period: stated in every report (start and end date).
  • For every answer we keep: full text, list of cited sources, engine, date.

05How do we count mentions?

Every answer is read in full and every mention is attributed to an entity after disambiguation: namesakes, multiple locations and name variants are resolved by hand before counting. Doubtful cases are left out of the count and noted in the dataset.

Metrics per entity:

MetricDefinition
Recurrencein how many answers the entity appears, out of all answers collected
Breadthon how many different engines the entity appears at least once
Positionwhere it appears when the answer is a list (first half / second half)
Agreementhow far the engines agree in naming it for the same questions

How rankings of outlets, journalists and creators are ordered

  • Verification first. Every name is checked before it is counted: it must be a real, identifiable outlet, person, channel, podcast or newsletter, active in the field of the report. Names that cannot be verified, or that an engine invented, are never ranked: they are counted separately and reported.
  • Order. Entities are ordered by Recurrence across all the answers of their category; ties are broken by Breadth. Position in a list is recorded but not used for the order.
  • Threshold. An entity enters a ranking only if it is named in at least 5% of the answers of its category.
  • No index. The AI Presence Index described below is not used for these rankings: two of its components, citations of the entity's own domain and technical readiness of its website, describe a business with a website and do not apply to a person or an account.

06The AI Presence Index

The metrics combine into a single score, the AI Presence Index, which orders the rankings of businesses and professionals.

The index is a whole number from 0 to 100, calculated over a rolling 4-week window and recomputable from the same data we publish. The formula is versioned: its version label is printed on every report, and any change in weights or formula produces a new, explicit version, never a silent change. The version in force is v1.

Components and weights (v1)

ComponentWeightWhat it measures
Mentions35share of answers that name the entity
Citations as a source25the entity's domain is cited as a source
Share of presence in answers15presence relative to the other entities
Technical readiness of the website15how readable the website is for AI systems
Sentiment10quality of the mention

The score is the sum of each component multiplied by its weight, rounded to the nearest whole number.

How each component is normalized (0–100 scale)

  • Mentions: percentage of answers in which the entity appears, capped at 100.
  • Citations as a source: use of the entity's domain among cited sources, relative to the most-cited domain in the report — min(100, domain_use% / leader_domain_use% × 100). It is 0 if the domain does not appear among cited sources.
  • Share of presence in answers: the entity's presence divided by the sum of the presence of all entities in the report, multiplied by 100. It is 0 if the entity is absent.
  • Technical readiness of the website: schema markup (40) + AI crawlers not blocked (30) + signals of editorial content (20) + meta description (10). If the website cannot be reached, it is 0.
  • Sentiment: 0–100 scale.

When sentiment cannot be measured

Below 3 mentions — including zero mentions — sentiment cannot be measured reliably: it is excluded, and its 10 points are redistributed proportionally over the other four components (35/25/15/15 on a base of 90, that is 38.9% / 27.8% / 16.7% / 16.7%). In that case the report says "not yet measurable (insufficient mentions)", not a number. A component worth zero, on the other hand, counts as zero: the data says zero, not "no data".

Calculation window

The window is 28 days. If the available history is shorter — for example in a first report — the available history is used and the report states the actual window.

The published formula is the formula used: no component is kept private.

07What do we NOT measure?

  • The professional quality, competence or results of the entities named.
  • Titles, credentials or specializations: presence in AI answers is not a title.
  • Whether what the engines say is correct: we record what they answer, we do not certify it. Errors found in the answers are noted in the dataset.
  • The traffic, inquiries or customers that mentions generate.

08Stated limits

  1. Engine volatility. AI systems change models and search mechanisms without notice: two reports far apart in time are not fully comparable, and comparisons over time should be read as trends, not as absolute measures.
  2. Sampling. A fixed set of prompts does not exhaust the ways people ask; it measures a fixed, declared sample of representative wordings.
  3. Collection infrastructure. Part of the collection runs through specialized third-party platforms. Malfunctions, delays or missing engines are stated in the report; the raw data stays in our hands and is published in full, and the collected data is checked continuously.
  4. Non-determinism. The same prompt can produce different answers at different times: repetition across days, prompts and engines exists precisely to reduce the weight of any single answer.

09Reproducibility

Results are obtained solely by querying AI engines, with a public methodology that is defined and published before each data collection. Prompts, dates and raw data can be downloaded: anyone can repeat the collection and verify the results.

The dataset of every report is published in /data/ under a CC BY 4.0 license.

10Version log

VersionDateChanges
1.022 October 2026First publication (English).