What Citation Laundering Is
Citation laundering is a structural failure mode of AI-answer citation. An aggregator publishes a listicle that recaps facts about many vendors — "11 Best AI Security Tools," "Vendor X vs Vendor Y." An AI engine retrieves that listicle, mines a fact about your brand from inside it, and cites the aggregator as the source — not your own page, where the fact originated.
Your authoritative claim gets attributed to someone else's content. The citation has been laundered: it passed through a third party and came out wearing that third party's name.
A Concrete Example
An AI engine answers a buyer's question and states "Vendor B supports SOC 2." It cites Vendor A's "11 Best AI Security Tools" roundup as the source. But Vendor A has no SOC 2 data about Vendor B — Vendor A copied it from Vendor B's own trust page months ago. Vendor B's trust page says exactly the same thing, first-hand. The engine had the original and the copy both available, and it cited the copy.
Multiply that across every fact in the answer and you get a citation graph where aggregators look like primary sources and the brands that actually published the facts look like they said nothing.
Why It Hurts
It inflates aggregator authority
Every laundered citation teaches the model that the aggregator is the place category facts come from. The aggregator's perceived authority compounds — on the back of facts it never originated.
It dilutes your first-party brand equity
The work of publishing proof — the trust page, the benchmark, the capability doc — is supposed to build a citable, authoritative footprint for your brand. When the credit routes to an aggregator, that footprint is being built for someone else.
It breaks attribution
If you cannot see that a fact about your brand is being sourced through an aggregator, you cannot tell which of your content is actually moving AI answers. Citation laundering makes the measurement problem harder, not just the equity problem.
Why AI Engines Do It
Not malice — structure. Aggregator listicles are dense, category-shaped, and well-linked: a single page recaps twenty vendors in the exact comparative format a category query asks for. That makes them high-relevance for category-level answers and easy to retrieve, so the engine reaches for the convenient summary over twenty separate first-party pages. Aggregators are genuinely useful for category-level framing — the failure is narrow and specific: citing them as the source for a fact about an individual vendor named inside the listicle.
What To Do About It
- Make the first-party source unmissable. The fact should live on a clearly named, well-structured page on your own domain — "/security," "/integrations" — so the engine has a clean original to cite.
- Match the buyer's phrasing. Engines pattern-match the query to the source. If the aggregator phrases the claim the way buyers ask it and your page does not, the aggregator wins the citation.
- Watch where your facts get sourced. Track, per claim, whether the engine cites you or an aggregator. A claim sourced through a listicle is a laundered citation to reclaim.
- Treat it as a Strategic AEO Plan move. Reclaiming a laundered citation is a close-a-gap play: a named page, a named claim, a named buyer — exactly the kind of action the weekly loop is built to ship.
The Takeaway
Citation laundering is what happens when the convenient source beats the correct one. Your brand made the claim; an aggregator gets the credit; the model learns the wrong lesson about where category facts come from. Fixing it is not about out-publishing aggregators — it is about giving the engine a first-party source so clean it has no reason to launder.