What the score is
The AI Visibility Score is a single number from 0 to 100. It rolls up the main signals an AI system needs to reliably read, understand, and use a page: whether bots can reach it, whether the important content is in the HTML response, whether the page has enough trust signals to be attributed, and whether the server responds fast enough.
The score is accompanied by a status label — Excellent, Warning, or Critical — which reflects how urgent the findings are. The status matters more than the raw number. A page with a score of 72 and a Warning status is in a different situation than a page with a score of 72 and a Critical status: the first has room to improve, the second has a hard blocker.
The four things it measures
1. Crawlability
Can the major AI bots access this page at all? If robots.txt blocks a bot, or if the live request fails with a 4xx/5xx, the page is unreachable regardless of how good the content is.
2. Content visibility
Is the important content in the raw HTML response? Pages that deliver their content only after JavaScript runs are at a disadvantage because many AI systems fetch the raw response rather than waiting for a browser-rendered version.
3. Authority
Does the page give AI systems enough context to understand what it is and trust it as a source? This includes structured data (JSON-LD), clear page-type classification, author metadata, and publication dates.
4. Performance
Does the server respond fast enough? TTFB (time to first byte) is the most important metric. Slow pages are harder to include reliably in AI retrieval pipelines.
Status labels
| Status | What it means |
|---|---|
| Excellent | No critical blockers detected. The page meets baseline requirements for AI retrieval. |
| Warning | One or more moderate issues found. The page is reachable but something is limiting its visibility or trustworthiness. |
| Critical | At least one hard blocker found. This usually means the page cannot be reached, cannot be read by AI bots, or fails a core requirement. |
When the status is Critical, fix the blocker before anything else. Lower-priority issues will not help while the critical one is unresolved.
How to use the score
Start with the status, not the number. A Critical status always means there is something to fix urgently. An Excellent status means the baseline is healthy — you can then focus on deeper improvements like Authority, Prompt Fit, and content quality.
Use the dimension cards to find what’s dragging the score down. The Overview tab shows a card for each dimension (Crawlability, Content Visibility, Authority, Performance). Each card shows that dimension’s status and links to the detailed tab. If one card is Red or Orange, start there.
Fix Critical items first, then Warnings. The priority issues list on the Overview tab sorts findings by impact. Work from the top.
What the score does not tell you
A high score does not mean your page will be cited by AI. The score measures technical access and structural quality. It does not predict whether your content is the best answer to any specific question. A page that scores 90 but gives a vague or off-topic answer will still be skipped.
A low score does not mean the page is broken. A low score can reflect an intentional configuration choice — like blocking certain bots on purpose, or a product page that does not need structured article data. Use the detail tabs to understand the actual findings.
The score does not update automatically. It reflects the page’s state at the time of the audit. Run a new audit after making changes to measure the impact.
Next steps
- See Reading the Overview tab for a guide to the dimension cards and priority issues list
- See Crawlability if your score is low because of bot access issues
- See Content Visibility if your score is low because of HTML content gaps
- See Performance for the TTFB grade table and what each grade means