Skip to main content

AI visibility

What Can AI Visibility Measurements Actually Tell You?

Appearing more often in a report does not by itself show that real customers see or choose your brand more often. This guide helps you read visibility metrics and separate the content, tool, and investment decisions they may support.

If you are assessing an AI visibility report, choosing a measurement tool, or considering what your content team should prioritise, start here.

An evolving guide I have brought together my existing articles and observations on this topic here. I will continue to develop the guide with new data, corrections, and articles.

Read the guide from the beginning

First identify the event you are counting

A brand name, source link, and product recommendation can appear in the same answer. They still do not say the same thing. Start reading a report by naming the event being counted.

Mention
The brand or site name appears in the answer.It does not mean there has been a positive assessment or a user preference.
Citation
The answer presents a page as a source.It does not prove that a user saw or clicked the link, or trusted the content.
Recommendation
The product or brand is presented as an option in the answer.The recommendation belongs to that question and context; it is not a general measure of expertise or market ranking.

The source of the data also changes its scope. A report a provider supplies from its own product and responses to prompts selected by a third-party tool are different observations. First-party data does not cover everything; you still need to know which products, queries, and events it covers.

Related article

In this article, I use this distinction to interpret Bing data

What Is AI Citation Share? What Bing's Data Actually Reveals

On sites I managed, I observed search performance and Bing citations move together. In the article, I explain the limit of that finding and why it cannot be generalised to all AI products or to a shared internal mechanism.

Opens in a new tab
A researcher compares search results with a gauge and handwritten notes on a desk

Which user does a prompt test represent?

A defined test shows the answer to a specific question under specific conditions. Whether it represents a real user’s conversation needs separate justification. Running more prompts does not automatically correct a poorly represented context.

A hypothetical hosting search

The tool’s single-turn test

“Which hosting provider would you recommend for WordPress?”

The tool may run this question using its selected model and settings, then count the brand names in the answer.

The user’s decision conversation

  1. They first research the options.
  2. They then explain their budget, visitor volume, and support needs.
  3. Finally, they compare two options that fit their own conditions.

We cannot assume the two paths will produce the same recommendation. A single-turn test is still useful, but its conclusion needs to fit its name and scope.

Ask for the test conditions before the score

Sample
Who selected the questions, and from which source? What supports the claim that they represent a particular user and decision stage?
Setup
Which product or API, model, language, region, web access, and conversation context were used?
Counting
Is the count a brand-name mention, a source link, or a recommendation? Ask what the denominator is and how repetitions are treated.
Comparison
Are the prompt set and conditions the same across periods? If the model, questions, or settings changed, the report should show it.

Related article

I explore the difference between this test and a user experience in a separate article

Do AI Visibility Tools Really Work? What They Actually Measure

Using the hosting example, I examine the limit of single-turn prompts, the tasks tools may be useful for, and the information an honest test report should contain. You can use it when assessing a report or tool proposal.

Opens in a new tab
A testing device samples prompt cards beside a landscape of disconnected conversation bubbles.

A changing chart does not explain its cause

If a visibility score rises after you update a page, you may think the change worked. That is an explanation to investigate. Changes to the test conditions, the product, or other pages in the same period may also have affected the result.

Observation
During a content-removal exercise, the AI visibility signals I examined fell before classic search visibility.
My initial explanation
I attributed the difference to pages being retrieved live at query time.
Revision with new evidence
The timeline on Google’s side did not match that explanation. The observation of an early decline remained; I had to withdraw my explanation of the internal mechanism.

This does not establish a fixed delay for every page, a separate AI index, or faster discovery of new content. You can retain an observation while changing the hypothesis that explains it. Write those two separately in your report.

Related article

In this article, I explain how I corrected my own explanation

AI Visibility Dropped Before Search: The Google Data That Changed My Theory

I show the comparison I made with Google data after examining Bing and which conclusion held up. It is a concrete example of how to reassess the explanation you have formed for a chart when new evidence arrives.

Opens in a new tab
Two clocks on opposite sides of a torn timeline show different rhythms of change

What should you do with this signal?

When you see a decline under the same test conditions, first find the affected questions and pages. An access issue, outdated information, ambiguity in the brand name, or a change in the test may be investigated. The score can start that investigation; it cannot by itself tell you which explanation is correct.

Separate a technical experiment from a proven return

For a proposed new file, content representation, or markup, write down which behaviour of which product you expect to change. Keep the provider’s documentation, your own observation, and a hypothesis you have not yet tested separate. Requests for the file are not the same as being cited in an answer or achieving a business outcome.

An alternative content representation may be worth testing if your existing infrastructure can produce it at low cost and it has other uses too. If it requires a separate publishing pipeline and ongoing maintenance, you need to show more clearly why the expected benefit justifies that work.

Related article

I examine this boundary in my llms.txt experiment

llms.txt Was Never the Point

I explain the experiment I set up with knowledge bases, Markdown, and JSON representations, what I learned, and why I did not draw a visibility promise from it. You can weigh the conditions under which a technical idea is worth testing.

Opens in a new tab
A blue caliper compares a stack of pages with a single loose sheet.

Link the content decision to the reader’s need

It may make sense to answer a question that appears in a visibility test. First examine whether it corresponds to a real reader need. If your content explains a decision, solves a problem, or conveys a verifiable experience, it has value independent of the visibility metric.

Make the decision to participate in a community in the same way. Join when you can make a meaningful contribution to people’s discussion. Pages and messages made only so that a model recommends you more often can push the people you want to help into the background. Technical clarity and good information architecture should support that purpose.

Related article

I address content and channel choices more broadly in this article

Getting Your Brand Recommended by AI Is the Wrong Goal. What Is the Right One?

Using examples from Reddit, technical SEO, and content production, I separate a useful contribution from interventions made for visibility. You can reassess the goal of “having AI recommend us” by asking what you will help the reader with.

Opens in a new tab
Two people turn a useful blue answer sheet into a decision while recommendation traces fade in the background.

A short note to accompany a visibility report

Complete the fields below before sharing a score with the team or allocating budget on its basis. Keeping an unknown field visible is more useful than creating a certainty the report does not support.

Decision
Which content, technical improvement, or tool decision will we make with this report?
Scope of the measurement
Which product, period, language, prompt set, and conditions were used? If this is a first-party report, what is the scope defined by the provider?
Observed event
Did we observe a mention, citation, recommendation, visit, or business outcome? What did we not observe?
Explanation and uncertainty
Do we know why it changed, or do we have a hypothesis to test? What other explanations are possible?
Next check
Which page or test condition will we examine? What additional evidence and maintenance cost would change our decision?

If your note makes a claim about a real user or business outcome, show separately which data supports it. If you have only prompt results, limit your decision to what that sample can show.

Return to the guide sections

All articles in the guide

The articles provide the foundations for this argument, from the scope of measurement to the content decision. Continue with the question most relevant to you.

Opens in a new tab

Where to go next?

This guide opens one part of the decision. These two related topics can help you examine another part of the same decision.

Writing beyond the guides

Other essays on AI, software, operations, and business decisions sit outside these guides too.

Browse all essays