Vendors love citations. Buyers should too — when they mean something. A numbered source next to an answer looks like grounding: the model is not freelancing, the claim has a home, the customer can check. In practice a large share of citation UI fails a test you can run in under a minute: open the link and ask whether the page actually contains the claim the assistant just made.
That gap matters because citations do more than inform. They lend confidence. A fluent answer with a badge feels more trustworthy than the same sentence without one, even when the badge points at a homepage that never mentions the policy. Decorative sources are worse than no sources — they borrow the aesthetics of accountability without providing any.
The only two checks that matter
When you evaluate a vendor, including us, pick three answered questions that carry sources and open each one. You are checking two independent properties. They fail separately, and sales decks often demonstrate only the first.
- The link resolves to a real, current page on the site you care about — not a 404, not a login wall, not a generic marketing URL.
- The page contains the specific claim. Not “something about shipping”, but the rate, the window, the exclusion the answer asserted.
Common citation failures
You will see the same patterns across tools. None of them require you to inspect the model. They require you to click.
| What you see | What it usually means | Pass the claim check? |
|---|---|---|
| Deep link to the policy paragraph | Retrieval found the right chunk | Often yes |
| Link to a section hub (“Shipping”) | Topic match, claim unverified | Only if the claim is on that page |
| Homepage or /help root | UI checkbox, not grounding | Almost never |
| PDF or doc with no highlight | Source exists; claim may not | You still have to search the file |
| Broken or stale URL after a recrawl gap | Ops problem wearing a citation badge | No |
The citation glossary entry is the short definition. The evaluation version is harsher: if a sceptical customer cannot settle the dispute from the linked page alone, the citation did no work.
Why “we cite sources” is not a feature
Feature matrices treat citations as a boolean. That is how you end up comparing a product that links the exact paragraph with one that sprinkles related URLs under every answer. Both rows say “citations: yes”. Only one changes what a customer can do with doubt.
Ask vendors to show a citation that survives the claim check on your content — not on their demo site. Then ask what happens when retrieval is weak: do they suppress the source, omit the answer, or still emit a confident paragraph with a vague link? The third behaviour is how hallucination gets a credibility costume.
“A citation should make an answer easier to falsify. If it only makes the answer feel safer, it is marketing.”
What good looks like in a live widget
- The source URL matches the site you indexed, including the right locale or product line.
- The claim appears in plain text on that page — not only in an image, a collapsed accordion the crawler missed, or a PDF the assistant paraphrased loosely.
- Multiple citations, if shown, are few and specific. A pile of related links is a search results page wearing a chat skin.
- When the system is unsure, it refuses rather than citing a neighbour page. See refusal.
If you are building the content side of this, the practical companion is writing pages an assistant can retrieve from — our guide on docs your bot can answer from is the ops version of the same idea.
A five-minute citation audit
Before you trust a shortlist, run this on every vendor that claims grounded answers:
- Ask three factual questions you can verify from your site.
- For each answer with a source, open the link in a private window.
- Highlight the sentence that supports the claim — or note that you cannot.
- Ask one question your site does not cover. If you still get a citation, fail the vendor for that turn.
Score the tool on how often step three succeeds, not on whether the UI has a footnotes component. Matter Chat should pass the same audit on your pages; if a citation of ours points at something that does not contain the claim, treat it as a product bug, not a nit. The point of a source is proof. Everything else is chrome.
