A report lands on an executive's desk saying citations are up. The executive hears "links from AI", checks the analytics, sees no change in referral traffic, and stops trusting the report. Nobody lied. Three different objects were wearing the same word.
Mentions, citations, and links are separate things inside an AI answer. They are produced by different parts of the system, they move independently, and they are worth different amounts to you. Separating them is the cheapest reporting improvement available in this discipline.
Three definitions
Use these verbatim if they help.
A mention is any occurrence of your brand name in the text of an assistant's answer, whether or not it is attributed to a source.
A citation is an attribution the assistant attaches to part of its answer, pointing at a specific source document it used or claims to have used.
A link is a clickable URL presented to the user, which they may or may not click.
The relationships are one-directional and lossy. A mention need not carry a citation. A citation need not point at a page that mentions you. A citation need not be rendered as a clickable link, and a link is not always a citation, because assistants also surface links that are suggestions rather than attributions.
| Mention | Citation | Link | |
|---|---|---|---|
| What it is | Your name in the answer text | An attribution to a source | A clickable URL |
| Whose page | Yours or anyone's | Usually someone's page, sometimes yours | Whatever the interface shows |
| Requires a source? | No | Yes, by definition | No |
| Clickable? | No | Sometimes | Yes |
| What it signals | The model associates you with the question | The answer leaned on a specific document | A route the user could take |
One further distinction worth holding separately: a mention is not the same as a recommendation. Being named in a list of "other options in this space" and being named as the suggested answer are different outcomes, and when a mention isn't a recommendation covers why aggregating them flattens the finding that matters.
How each one appears in a real answer
Take an illustrative answer to "what tools handle recurring invoice reminders for small agencies?" The output might name four products in prose, attach a numbered marker to a sentence about pricing models, list three source cards under the answer, and present one of those cards as a clickable domain.
In that single response you have four mentions, one citation attached to a specific claim, three source attributions in the panel, and one clickable link. Different measurement approaches would produce four different numbers from the same screen, and all four would be defensible under some definition. That is exactly why your report has to state which definition it used.
Presentation varies by assistant and by surface, and it changes without notice. Some interfaces show inline numeric markers, some show source cards below the answer, some show a hover panel, some show a domain name with no clickable target, and some show nothing at all for the same underlying retrieval. The same model accessed through an API rather than a consumer interface may return source metadata in a completely different shape, or none. Verify the current display behaviour of any assistant you report on against provider documentation before you write a definition into a template. Two practical consequences. First, a citation-count comparison across assistants compares interface conventions as much as it compares your standing. Second, any measurement method that reads citations off a rendered screen inherits that interface's conventions, which is one reason a reproducible method should prefer authorized, documented interfaces and record what each response format does and does not expose.
Why they do not move together
If mentions and citations tracked each other, one metric would do. They do not, and the reasons are structural.
-
Mentions can come from the model's own parameters. An assistant can name well-known brands in a category without retrieving anything, in which case there is nothing to cite. Answers assembled this way produce mentions with no citations at all.
-
Citations often point at third parties. A comparison article, a community thread, or a review site can be cited as the source for a sentence that names you. You gained a mention; someone else gained the citation.
-
Retrieval and answer text are separate steps. A document can be retrieved and cited while contributing little to the sentence that names a brand, and a document can shape an answer without surviving into the displayed source list.
-
Interface rules cap what is shown. If a surface displays three source cards, the fourth source does not exist as far as your count is concerned, regardless of what the system used.
So the four common patterns are all real, and each means something different:
| Pattern | Likely reading |
|---|---|
| Mentioned, not cited | The model associates you with the category; nothing of yours was pulled in |
| Cited, not mentioned | Your page informed the answer, but the answer named someone else |
| Both | The strongest position available in a single answer |
| Neither | You are absent from both the model's associations and the retrieved set |
"Cited, not mentioned" is the pattern most often misread. Your content is doing work and your brand is not collecting the benefit. That usually points at content that answers the question without clearly identifying who is answering it.
What each one is worth to you
Value depends on what you are trying to achieve, and none of the three converts to traffic on a fixed rate.
A mention is brand presence at the moment of decision. It puts you in the consideration set of someone who may never visit your site. It cannot be clicked and will usually not appear in your analytics at all, which makes it real but hard to attribute.
A citation is evidence that a specific document of yours entered the answer. It is the most useful diagnostic signal of the three, because it is actionable: it tells you which page did the work, and it lets you find out which sources dominate your category when the cited domain is not yours.
A link is the only one that can produce a session. Whether it does depends on placement, on whether the user's question was already answered, and on interface behaviour you do not control.
The important caution: a citation does not guarantee referral traffic, and no honest ratio between the two exists as a general figure. Users in assistant interfaces frequently get what they came for from the answer itself. Anyone quoting a click-through rate for AI citations should be asked for the sample, the assistants, the dates, and the method, and the figure should not be reused outside those conditions. We are not going to invent one here.
It also does not follow that a citation is worth what a traditional inbound link is worth. They are different objects. A citation is an attribution inside a single answer to a single user, generated at query time, and it may not persist to the next identical query. Treating it as an equivalent asset to a durable hyperlink imports assumptions that do not hold.
How to phrase this in a report
Write the definitions into the report itself, once, near the top. Then use the words consistently.
Wording that survives scrutiny:
- "Brand mention rate: the share of sampled answers naming us, whether or not a source was attributed."
- "Citation rate: the share of sampled answers attributing at least one claim to a page on our domain."
- "These are different measures. A rise in one does not imply a rise in the other."
- "Citations are not links, and are not expected to appear in referral traffic. We report them as an answer-composition signal, not an acquisition channel."
- "Counts are taken from [assistants], via [interface or API], on [dates]. Display conventions differ between assistants and can change."
Wording to strike out: "AI backlinks", "citations earned" without a definition, any blended "AI visibility score" that silently mixes the three, and any sentence implying a citation will send traffic. For choosing which of these to lead with in a given report, see which metric answers which question.
FAQ
Is an AI citation a backlink? No. A backlink is a persistent reference on a page that other systems can crawl. A citation is an attribution generated inside one answer for one user at one moment, and it may not repeat for the same question.
If the assistant names us but cites a review site, whose win is it? Both, differently. You gained a mention. The review site gained the citation, and its page is the one feeding the answer, which tells you where the influence in your category currently sits.
Should we report citations if they send no traffic? Yes, as a diagnostic rather than a channel. Citation data tells you which of your pages assistants actually use, and which third-party sources dominate your category. Label it clearly so nobody expects sessions from it.
Why does our citation count differ between two tools? Almost always definitions and surfaces. One may count source cards, another inline markers, another only clickable URLs, and they may sample different assistants on different dates. Ask each for its counting rule before reconciling the numbers.
In Plain English
A mention is your name in the answer. A citation is the assistant attributing part of its answer to a source. A link is something a user can click. They are produced differently, they move independently, and only the third can send a visit. Citation display varies by assistant and by surface, so any count carries its interface's conventions with it, and a citation on its own is not a promise of referral traffic.
This is for anyone writing or reading an AI visibility report, and for anyone about to compare two tools whose numbers disagree. Use it the moment someone says "citations" without saying which of the three they mean, which is usually the first time the word appears in a meeting.
Next step: add the three definitions to the top of your reporting template and check which one your current tool is actually counting. Explore the glossary for the rest of the vocabulary, and read the AI search fundamentals hub for how answers get assembled in the first place.
Primary-source verification
Checked July 28, 2026. The operational and factual guidance above was reviewed against the primary references below. Provider features, prices, policies, interfaces, jurisdictions, and account-specific results can change; recheck the controlling first-party document and your own account or measured data before acting.
- Google Search: AI features and your website - How Google describes eligibility, preview controls, and appearance in its AI search features.
- Google: common crawlers and special-case user agents - Current Googlebot and Google-Extended identities and controls.
- OpenAI: overview of OpenAI crawlers - Current GPTBot, OAI-SearchBot, and ChatGPT-User descriptions and publisher controls.
- Anthropic: web-crawler controls - Current ClaudeBot, Claude-SearchBot, and Claude-User descriptions and controls.
- Perplexity: crawler and user-agent documentation - Current PerplexityBot and Perplexity-User descriptions and controls.
- Apache HTTP Server: mod_log_config - Authoritative Apache access-log fields and formats.
- nginx: HTTP log module - Authoritative nginx access-log configuration and variables.
- Google Analytics: traffic-source dimensions - Current GA4 source, medium, campaign, and default-channel definitions.
- FTC: Endorsement Guides Q&A - Current U.S. regulator guidance on endorsements, disclosures, and reviews.
- FTC: Consumer Reviews and Testimonials Rule Q&A - Current U.S. rule guidance on deceptive review practices.