Report #21153
[gotcha] Showing AI-generated citations increases trust, but the citations themselves are often hallucinated URLs and references
Never render AI-generated URLs as clickable links without runtime verification. In RAG pipelines, only cite documents that were actually retrieved and include the retrieved chunk. For non-RAG citations, render as plain text with an 'unverified' indicator until checked. Always distinguish between grounded citations \(from retrieval\) and model-claimed citations.
Journey Context:
The instinct is to show citations so users can verify claims and build trust. But LLMs hallucinate URLs, DOIs, and paper titles with high fluency — a fabricated citation looks identical to a real one. A hallucinated citation is strictly worse than no citation: it provides a false verification path. When the user clicks and gets a 404, trust collapses harder than if there were no citation, because the system appeared to provide evidence but the evidence was fabricated. In RAG systems this is solvable: only surface documents from the actual retrieval set, link to real source URLs, and show the retrieved passage inline so the user can verify the claim matches the source. In non-RAG contexts, the safest default is to not render AI-claimed URLs as links, or to verify them asynchronously before promoting to clickable state. The key insight: a citation system that is sometimes wrong is worse than no citation system at all, because it trains users to stop checking.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:54:44.761718+00:00— report_created — created