What to Do When Claude Hallucinates Citations or Sources

Claude can generate a citation, a source name, a URL, a quote, that sounds completely plausible and is entirely fabricated.

This isn't Claude being dishonest, it's a byproduct of generating text that's statistically likely to look like a real citation, without necessarily being grounded in a verified, currently-accessible source.

This checklist covers recognizing a fabricated citation, understanding why it happens, and verifying or correcting it before you rely on it.

How to Use This Checklist

• Treat every citation from Claude as unverified until you've checked it, this habit matters more than any single step below.
• Run through Recognize whenever a citation seems important enough to act on or repeat elsewhere.
• Use Verify and Correct to confirm or fix it before using it.
• If you're working with citations regularly, it's worth building this checklist into a standing habit rather than a one-off check.

Recognize the Red Flags

1. An implausible or suspiciously tidy URL. A link that looks generic, oddly formatted, or that you can't recall having seen in a real search result is worth a second look.
2. An oddly specific page number or section reference. Precise-sounding details like "page 214" or "section 3.2" attached to a source you can't independently confirm are a common hallucination pattern.
3. A source that doesn't turn up when you search for it. If a quick search for the title, author, or publication doesn't surface anything matching, treat the citation as unconfirmed.
4. A quote that seems too perfectly on-point. A quote that lines up exactly with your argument, worded suspiciously smoothly, is worth checking against the actual source rather than taken at face value.
5. Multiple citations bundled together with no way to tell them apart. A long list of sources dropped into one answer, with no individual verification cues, increases the odds that at least one is fabricated.
6. No live web access was used to generate the answer. If Claude answered purely from its training without an active search or research tool, any specific citation is inherently more likely to be a plausible reconstruction rather than a checked reference.

Why It Happens

1. Claude generates the most statistically plausible continuation of your request. For a request implying a citation, that continuation looks exactly like a real citation, structurally, even when no specific source was actually retrieved and verified.
2. Without live web or research access, there's no verification step in the loop. A citation produced from training data alone is a best guess at what a real source in that space would look like, not confirmation that a specific document exists with that content.
3. Specificity increases plausibility, not accuracy. More precise-sounding details (page numbers, exact dates, exact phrasing) make a fabricated citation feel more credible without making it more true.

Verify and Correct

1. Search for the source independently. Before repeating or citing it anywhere, put the title, author, or claimed URL into a real search yourself and confirm it exists and says what was claimed.
2. Ask Claude directly whether it's certain or inferring. A direct question like "are you certain this source exists, or is this your best guess at what one might look like?" often prompts Claude to flag uncertainty it didn't surface unprompted.
3. Ask Claude to state its confidence level. Explicitly requesting a confidence rating, or a note on whether a claim is well-established versus inferred, tends to produce more honest hedging than an unprompted answer.
4. Re-ask with a research or web-search tool enabled, if one is available to you. An answer grounded in an actual live search is meaningfully more reliable than one generated from training data alone.
5. Ask for a different kind of support if the citation can't be confirmed. Instead of a specific source, ask for the general claim stated as such, without attaching a fabricated citation to it, this is often more honest than a shaky reference.
6. Treat an unverified citation as a starting hint, not a fact. Even a plausible-looking citation is, at best, a lead for where to look, not something to repeat as confirmed until you've checked it yourself.
7. Correct downstream uses. If you already used a since-debunked citation somewhere (a document, an email, a report), go back and fix or remove it rather than letting it propagate.

Gotchas

• Assuming a confident tone means a verified fact. Claude's phrasing doesn't reliably signal certainty; a fabricated citation can be stated just as confidently as a real one.
• Only checking citations that "feel" suspicious. Some fabrications are entirely unremarkable-looking. Spot-checking based on gut feeling alone will miss some.
• Re-asking the same way and expecting a different answer. Simply repeating the request often reproduces a similar fabrication. Ask the verification questions above instead of just re-asking.
• Treating a real-sounding publication name as proof. Fabricated citations often use real, well-known publication or author names attached to content that publication never actually produced.

FAQs

Related

• Why Claude Answers Get Worse: A Mental Model - the broader context-quality mechanism this symptom relates to.
• Fixing Hit Context and Length Limits in Long Conversations - another common everyday symptom in long threads.
• Troubleshooting Quick-Reference Checklist - the fast symptom-to-fix map for this whole section.

Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.