> ## Documentation Index
> Fetch the complete documentation index at: https://areyoufoundbyai.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Visibility vs AI Readiness: what each result measures

> The named share tells you whether AI engines name you. AI Readiness tells you how well your website is set up to be understood. Learn what each result measures and how to read them together.

An Are you found by AI? report answers two different questions. The first is the outcome: when buyers ask AI engines about your category, do the answers name your business? That is measured by the **named share**. The second is the input you control on your own site: is your website set up so AI can understand it? That is **AI Readiness**. Your off-site **Footprint** is scored separately again. Being ready and being named are not the same thing.

## Named share: the headline measure

Named share is the number of countable saved answers that name your business, divided by all countable saved answers. If AI names a business in 7 of 28 countable answers, its named share is 25%.

* Every saved repetition counts. An engine may be asked the same question more than once, and each saved answer counts on its own. There is no majority vote.
* A link to your website on its own does not count as your business being named in the answer.
* Missing or incomplete evidence is left out, never counted as a no.

Read the named share with the questions, engines, date and answer count beside it. A short free scan (2 questions on ChatGPT and Gemini) is a smaller sample than a full check across seven engines. AI answers can vary between runs, so Pro re-asks your pinned questions on the schedule you choose (weekly, monthly or whenever you like) to help you tell an isolated answer from a wider trend.

## The AI Visibility score

Reports, the scan API and the MCP server also return an **AI Visibility score** out of 100. It is an older weighted diagnostic score. It is not a percentage of AI recommendations, and it cannot be converted into a named share.

Its scoring basis: being named in the answer prose counts in full toward your visibility score. A positive result recorded only as a list entry, citation or source title counts half. Older results without this distinction retain their recorded scoring basis.

Public surfaces describe the score with three bands:

| AI Visibility score | Band |
| - | - |
| 60 or more | Visible to AI |
| 25 or more | Partially visible |
| Below 25 | Rarely visible |

The scan API also returns a verdict of `present`, `weak` or `absent`.

## AI Readiness

AI Readiness (out of 100) is how well your website itself is set up to be understood by AI, measured from the site alone. It is composed of five site signals: Citability (quotable content), E-E-A-T (trust and credibility), Technical (site health), Schema (machine-readable business facts) and Platform (AI-ready setup).

A signal that could not be verified, for example because the page could not be read, the site is a JavaScript shell, or robots.txt was unreadable, is left out of Readiness rather than scored zero. Which signals count can therefore differ from scan to scan, and each report states the share each signal carries. See [AI Readiness and Footprint](/docs/concepts/geo-score) for the detail.

## Footprint

Footprint (out of 100) is the separate off-site score: Wikidata and Knowledge Graph entity, Google Business Profile, brand mentions, search demand and referring domains. It is scored beside Readiness, not inside it. The free scan does not measure Footprint, so it shows as not measured rather than zero.

## Why the results diverge

Site checks explain what to work on. Crawler access, readable content, business facts, structured data and independent mentions are separate checks. They are not extra percentages of AI recommendations, and an older weighted score cannot be converted into a named share.

<CardGroup cols={2}>
  <Card title="High Readiness, low named share" icon="clock">
    You can be highly ready yet still rarely named: a well-built site the engines do not yet know or trust. Review the sources saved with the answers to find the independent places where buyers, and engines, could find you.
  </Card>

  <Card title="Low Readiness, high named share" icon="triangle-exclamation">
    The engines name you, but your own site is not making your business easy to understand. Make your name, services, locations and contact details clear and consistent, and check what a crawler receives.
  </Card>
</CardGroup>

None of these checks guarantees a recommendation, and a change in an answer does not by itself prove which edit caused it.

## The results side by side

| | Named share | AI Readiness | Footprint |
| - | - | - | - |
| **Question answered** | Do the engines name you in their answers? | Is your website set up to be understood by AI? | How present is your business off your own site? |
| **What it measures** | Countable saved answers that name you, divided by all countable saved answers | Five site signals, measured from your site alone | Entity, Google Business Profile, brand mentions, search demand, referring domains |
| **Form** | A percentage with its counts | Out of 100 | Out of 100 |
| **How to work on it** | Act on the fix plan, then measure the same questions again | Fix crawler access, readable content, business facts and structured data | Review the sources in your market's answers and the profiles and listings they point to |
| **Measured by** | Asking the engines buyer questions and saving the answers | Reading your website | Off-site checks in the full report |

## Read, fix, measure again

<Steps>
  <Step title="Measure: areyoufoundbyai.com">
    Run a scan to see which engines named you, who they named instead and the words behind each result.
  </Step>

  <Step title="Diagnose: site checks">
    Your AI Readiness signals and Footprint show which checks need attention. The fix plan orders the work.
  </Step>

  <Step title="Fix and measure again">
    Apply the fixes from your report. Pro re-measures your pinned buyer questions on the schedule you choose, so you can compare the same questions and engines over time. Keep changes in coverage separate from changes in results.
  </Step>
</Steps>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.