How to Verify AI Citations: A Procedure That Catches Fake References (2026)

Why this stopped being a small problem in 2026

A student on r/PhD described spending an hour hunting through databases for a journal article an AI tool had cited for a methodology claim. It had authors, a year, the exact volume number. The paper did not exist. That thread ran to 84 replies, which tells you how familiar it was.

What changed in 2026 is the other end: the consequences. In May, a policy change at arXiv — that authors submitting papers with hallucinated citations can lose the ability to submit — was widely reported and argued over in a 117-comment thread on r/AskAcademia. We are summarising a discussion here, not quoting the policy text, so check arXiv's current moderation policy yourself before relying on the detail. Papers have been retracted over fabricated references, and reviewers now check reference lists as a routine first pass. One reviewer described three non-existent papers in a single manuscript, and called it the third such manuscript in a year.

Prevalence figures are circulating and should be treated carefully. That same reviewer cited a 2026 audit of roughly 2.5 million PubMed papers reporting fabricated references in about one paper in 277; we have not verified that number against the audit itself, so treat it as an order of magnitude.

What matters for you is simpler. Your examiner is now primed to check, and in a thesis a reference to a source that does not exist is not a formatting slip. It is a claim you cannot support, and depending on your institution it can be handled as misconduct rather than as an error.

Why a language model invents references

This is not a bug that will be patched next month, and understanding why tells you where to look. A language model produces a citation the same way it produces a sentence: by predicting what plausibly comes next. A reference is one of the most regular structures in academic text — surname, initials, year, title, journal, volume, issue, page range, DOI. A model that has seen millions of them can assemble a new one that fits the pattern perfectly, with a page range of the right length and a volume number of the right size for that journal's age.

Plausibility is the objective. Existence is not. Nothing in that process consults a database unless the tool has been built to do so. This has an uncomfortable consequence: how real a citation looks tells you nothing about whether it is real, because looking real is precisely what the system optimises for. The DOI is generated the same way as the title — a well-formed string, not a resolved record.

The same mechanism explains the near-misses: real author names attached to titles they never wrote, a real paper moved to a different journal or shifted by two years, two papers merged into one reference. None of that is lying. It is pattern completion with no ground truth underneath.

Three failure modes, and why the third is the worst

Lumping these together is why people check badly. They are found in different ways.

One: the reference does not exist.Fabricated end to end — authors, title, journal, volume, pages, DOI, none of it resolves to anything. This is the easiest to catch and the one most checking advice covers. A resolving DOI or a hit in the journal's own archive settles it in under a minute.

Two: the reference exists, but the details are wrong. A real article attributed to the wrong authors, dated to the wrong year, placed in the wrong journal, or given a page range from a different issue. This is caught less often, because when you search the title you find something close and stop there. The damage is that your bibliography sends a reader to a record that does not exist, which reads as carelessness at best.

Three: the reference is real and correctly described, but it does not support your claim. Nothing in your bibliography looks wrong. Every DOI resolves. The only way to find it is to open the paper and read it. This is the dangerous one, and it is the one no metadata check and no citation-checking tool that only compares strings can catch — a real 2019 article on nurse retention in three Dutch hospitals, cited for a general statement about healthcare staff turnover across Europe.

Worth saying plainly: humans produce failure mode three without any AI involved, by citing a paper because three other papers cited it that way. AI tools have made it far more common.

The verification procedure, in order

Run these in sequence and stop as soon as a reference fails. The order is deliberate: the cheap checks come first.

1. Resolve the DOI. Paste it after https://doi.org/ in your browser. It should land on a publisher page whose title, authors and year match your reference. A DOI that returns an error is close to conclusive. A DOI that resolves to a different paper is failure mode two, not a win.

2. Search the title in the journal's own archive, not a search engine.This is the step people get wrong. General search results are full of aggregator pages, citation farms and, increasingly, AI-written pages that reproduce fabricated references — so a search that finds “something” is weak evidence. Go to the journal's site, open the volume and issue, and read the table of contents. For books, use the publisher's or a library catalogue. Our guide to academic sources and databases lists where each field is indexed.

3. Check the authors really write on this.Search the first author's name plus the topic in Google Scholar, or find their institutional page or ORCID profile. The recombination failure is obvious here: a real, well-published researcher who has never worked on your subject. If the author has no traceable record at all, treat the journal with suspicion too — see how to find credible sources for what a thin publication trail usually means.

4. Check that the volume, year and pages exist. If your reference says volume 47 (2019), pages 233–251, confirm that volume 47 of that journal is in fact 2019, and that those page numbers fall inside that issue rather than past the end of it. Fabricated references pick a plausible volume and an arbitrary page range, and the two frequently do not fit together.

5. Check the item type. A “journal article” that turns out to be a conference paper, a preprint or a book chapter means the metadata was assembled rather than copied. Fix it: a preprint cited as peer-reviewed changes what your evidence is worth.

The step everyone skips: open it and read the sentence

Steps one to five tell you a paper exists. They tell you nothing about whether it says what you claimed it says. The procedure for that is mechanical: take the sentence in your draft that carries the citation, open the source and find the passage it rests on — search the PDF for your key term rather than reading the whole paper — then compare the two. There are three outcomes.

• The source states it directly. Note the page number while you are there; a footnote style will need it anyway.
• The source states something adjacent. This is the common case. The original says “in a sample of 214 nurses in three Dutch hospitals, X was associated with Y”; your draft says “X increases Y”. The original hedges and covers 2015 to 2019; yours does neither. Fix your sentence, not the citation.
• The source does not state it at all.Often the claim is in the source's own literature review, citing someone else. Then you cite the original, or you mark it explicitly as a secondary citation — our APA 7 guide covers the wording for that.

This is the step that catches the half of the problem the existence checks miss: the tool found a real paper and then drifted while summarising it. The reference survives every metadata check and still misrepresents the literature.

Doing this on a list of sixty references

Be realistic about the cost. The full six-step check runs two to four minutes per reference, and longer whenever step six means actually reading something. Sixty references is an afternoon at minimum. That is why it cannot be done the night before, and why it should not be done uniformly.

Triage instead. Full check on:

• anything an AI tool suggested, summarised or formatted for you;
• anything you cannot remember downloading and opening yourself;
• anything load-bearing — your method, your central definition, any number you quote.

Steps one and four alone are enough for sources you found yourself, read in full and imported from the publisher. Keep the results in a spreadsheet rather than in your head: one row per reference, columns for DOI resolves, found in archive, pages check out, claim verified, date checked. It is dull, and it means that when a supervisor asks whether you verified your sources you have an answer with a date on it.

What to do when a reference fails the check

Fabricated. Delete it, then deal with the orphan it leaves behind: a sentence in your draft with nothing under it. Resist the obvious move of searching for a source that says the same thing and pasting in the first result — that is precisely how failure mode three gets created. Either find a source you have read that supports the claim, or narrow the claim to what you can support.

Wrong details.Correct the entry from the publisher's record, not from your reference manager's automatic import and not from the AI tool's output. Auto-import is where a lot of wrong years and missing issue numbers come from in the first place.

Real, but does not support the claim. Rewrite your sentence to what the source actually says. The honest version is nearly always more specific, and more specific reads better.

Already submitted. Say so yourself, before it is found during marking. Name the reference, explain how it got in, and bring the corrected passage. Self-reported errors and discovered ones are handled very differently, everywhere.

An honest question to end on

The reason almost nobody does this properly is not laziness. It is timing. Verification happens at the end, on a list of sixty references, under deadline, weeks after you inserted each citation. By then you cannot remember which ones came from a tool and which you read yourself. The check belongs at the moment you insert the citation, when there is one reference to look at and you still remember where the claim came from: resolve the DOI as it is typed, confirm the record matches, and flag the sentence when the source does not appear to say what you attached to it.

We are considering building exactly that, running while you write rather than as a final pass. It would not write anything for you and it would not remove your responsibility for the claim. It would just refuse to let a reference into your document quietly. If you would use that, tell us.