AI Hallucinations

Why LLMs confidently make things up, why grounding reduces but doesn't fix it, and what hallucinated URLs and brand errors mean for your SEO.

First published: Jun 24, 2026 · Last updated: Jul 21, 2026 · Advanced
demand #6 in How Search Works#10 in AI Search#45 on the site
1 evidence signal on this page

An AI hallucination is when a language model states something confidently that's factually wrong, fabricated, or unsupported — invented citations, made-up URLs, wrong facts about your brand. It's not a bug; it's a side effect of next-token prediction, which optimizes for plausible-sounding text, not truth. Grounding and RAG cut hallucination a lot (73–86% in some benchmarks) but the best grounded models still fail ~10–15% of the time, and bigger models can be more confidently wrong, not less. For SEO it shows up three ways: AI assistants send users to 404s ~2.87x more than Google (and 3.6% of Ahrefs' AI traffic went to pages that don't exist); AI answers can state wrong facts about your brand to a prospect before they ever reach you; and AI content you publish unverified can hallucinate and feed the next model. The fixes are tactical — redirect hallucinated URLs, monitor what AI says about you, and publish clear, verifiable, entity-rich content AI can ground on.

TruthfulQA foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. that scale alone did not make the tested models more truthful on its benchmark. Evidence for this claim TruthfulQA found that language models can reproduce common human misconceptions and that larger models were not automatically more truthful on its benchmark. Scope: TruthfulQA's benchmark, model set, and 2021 results; not a current cross-model error rate. Confidence: high · Verified: Lin et al.: TruthfulQA NIST treats confabulation as a risk to measure and manage, not as a product-specific fixed error rate. Evidence for this claim NIST's Generative AI Profile identifies confabulation—the confident presentation of false or erroneous content—as a generative-AI risk. Scope: NIST risk-management terminology and guidance; not a product-specific incidence estimate. Confidence: high · Verified: NIST: Generative AI Profile

TL;DR — Hallucination is a characteristic of next-tokenA token is the smallest unit of text (or image/audio/video) an LLM processes — roughly 4 characters, or about ¾ of an English word. A context window is the maximum number of tokens (input plus output) a model can hold at once, like its short-term memory. prediction, not a bug you can patch out. Models optimize for plausible continuations, not truth, so they confidently produce false statements when training signal is thin. groundingGrounding is anchoring an AI model's answer to source documents it retrieves at the moment you ask — not to the patterns frozen into its weights during training. Retrieval-Augmented Generation (RAG) is the most common way to do it. and RAGRAG is the retrieve-then-generate pattern behind AI search: the system retrieves relevant passages from an external index at query time, injects them into the model's context, and generates an answer grounded in those sources — without changing the model's weights. reduce it (73–86% in some benchmarks) but don’t eliminate it — the best grounded models still fail ~10–15% of the time, and TruthfulQA found larger models can produce more convincing falsehoods. For SEO it’s measurable: AI sends users to 404s ~2.87x more than Google, 3.6% of our AI traffic at Ahrefs went to non-existent pages, and citation error rates across AI search enginesAI search uses large language models and retrieval-augmented generation (RAG) to synthesize an answer from multiple sources rather than returning a ranked list of links. Examples include Google AI Overviews, ChatGPT Search, and Perplexity. run north of 60%. The fixes are tactical: redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. hallucinated URLs, monitor brand answers, and publish verifiable, entity-clear content.

What hallucination actually is

An AI hallucination is output that’s confidently stated but factually incorrect, fabricated, or unsupported by any source. The cleaner technical term is confabulation — borrowed from neuropsychology, where it means producing false accounts with genuine confidence and no intent to deceive. That precision matters: the model isn’t lying. It has no notion of truth to lie about. It’s running the one task it was trained for — predicting the next token — and sometimes the most probable token is false.

This is the single most important framing on this page: hallucination is an inherent byproduct of language modeling that prioritizes plausibility over factual accuracy. It emerges from LLMsA large language model (LLM) is a deep-learning model trained on massive text corpora to predict the next token and generate human-like text. LLMs use the transformer architecture and power AI search features like Google's AI Overviews (Gemini) and Bing Copilot (GPT-4). functioning as designed, not from implementation failures. You don’t fix it the way you fix a bug. You reduce it.

Why it happens — the mechanism

LLMs are trained on a next-token objective: given a sequence, predict the most probable next token. That’s a language completion task, not a fact retrieval task. The model optimizes for what text sounds like it should follow, not what is true. When the training signal for a specific fact is thin — rare events, niche topics, anything that changed after the model’s knowledge cutoffA knowledge cutoff (or training data cutoff) is the date after which an LLM was no longer trained on new data. The model has no awareness of anything that happened later — unless the system bolts on live retrieval (RAG/web search) to fetch it at query time. — the model fills the gap with statistically probable language. If a sequence looks like a question, the probability mass overwhelmingly favors generating an “answer-shaped” response over admitting uncertainty, regardless of whether the model actually has the knowledge.

Microsoft Research’s Ece Kamar makes the empirical version of this point: models hallucinate more around facts that are less common in the training data. The long tail is where confabulation lives. Your obscure product SKU, a recent rename, a founder who left last quarter — exactly the facts least represented on the web are the ones a model is most likely to get confidently wrong.

The types worth keeping straight

  • Factual hallucination — the stated fact is simply wrong.
  • Citation / attribution hallucination — the model cites a source it didn’t use, misattributes a quote, fabricates a byline, or invents a URL. The most directly measurable SEO version.
  • Entity / brand hallucination — wrong names, dates, stats, pricing, or company facts, stated with confidence.
  • Intrinsic vs. extrinsic (the Ji et al. taxonomy): intrinsic output contradicts the source provided; extrinsic output cannot be verified from the source — neither confirmed nor contradicted, a fabricated addition.

Reading hallucination claims correctly

Five distinctions get flattened in most hallucination coverage, including earlier drafts of this page. They matter because they change what “fixed,” “grounded,” or “cited” actually means when you’re evaluating a tool or a claim.

  • Name the reference. “Hallucination” isn’t one failure mode. It can mean contradiction of the supplied context, an unsupported addition the context neither confirms nor denies, or a plain world-factual error — and those three aren’t interchangeable (Ji et al.’s survey is the source taxonomy). A checker built to catch one of the three will quietly miss the other two.
  • Factuality is not faithfulness. Factuality tests a claim against an external, real-world reference — is it true? Faithfulness tests a claim against the evidence you actually supplied — is it supported by that evidence? An answer can pass one and fail the other: faithfully summarizing a wrong source, or stating something true that the supplied evidence never backs. FActScore’s atomic-fact method — breaking a long answer into individually checkable claims — exists because a single holistic score hides that split.
  • A citation existing isn’t groundingGrounding is anchoring an AI model's answer to source documents it retrieves at the moment you ask — not to the patterns frozen into its weights during training. Retrieval-Augmented Generation (RAG) is the most common way to do it.. Citation quality is really three separate checks: does the citation exist and resolve, does it actually entail (support) the specific claim sitting next to it, and does the answer cover every claim that needed a citation in the first place (the breakdown Gao et al.’s ALCE work uses). A visible, clickable footnote can pass the first check and fail the other two — which is exactly the gap behind the 60%+ citation-error numbers above.
  • RAG failures have named stages, not one label. When a RAG-backed answer is wrong, the cause is one of: the evidence was never in the corpus, it was chunked so the needed fact got split across a boundary, it existed but wasn’t retrieved, it was retrieved but ranked too low to reach the generator, or it reached the generator and got misused anyway (RAGTruth’s taxonomy of RAG errors). “The AI hallucinated” collapses five different root causes — and different fixes — into one word.
  • Benchmark percentages don’t travel. Every rate on this page — 73–86%, ~85–90%, 58% vs. 94% — is scoped to a specific task, dataset, reference policy, judge, prompt set, corpus, model, model version, and test date. Don’t quote “model X is Y% accurate” as a portable fact outside that benchmark’s own evaluation contract; a different judge, corpus, or model version can move the number substantially.

What the research shows

  • TruthfulQA (Lin et al., 2021) established the inverse-scaling problem. Across 817 adversarial questions, the largest model of the day (GPT-3-175B) was only 58% truthful vs. a 94% human baseline — and crucially, “larger models produce more imitative falsehoods because they are better at learning the training distribution.” Bigger isn’t safer. A bigger model is better at reproducing the popular misconceptions baked into web text, so it can be more confidently wrong, not less. (This is directly relevant to your brand: if wrong information about you circulates online, more capable models are better at absorbing and replicating it.)
  • Ji et al. survey (2022/2023) is the gold-standard academic taxonomy — intrinsic vs. extrinsic hallucination across summarization, dialogue, QA, translation, and LLMs.
  • Lanham et al. (2023), from Anthropic, found chain-of-thought reasoning isn’t always faithful: “as models become larger and more capable, they produce less faithful reasoning on most tasks.” The step-by-step explanation a model shows you doesn’t necessarily reflect how it actually reached the answer — it can be post-hoc rationalization. So “the AI explained its reasoning” is not proof the answer is grounded.
  • FACTS Grounding (Google DeepMind, Dec 2024) is the number that anchors the grounding debate: even given explicit source documents, the best models scored only ~85–90% grounded. That remaining 10–15% is misreading, misinterpreting, or failing to use the retrieved content — not confabulating from nothing.

Does grounding (RAG) solve it? No — it reduces it

This is the nuance most coverage botches. grounding — anchoring an answer to documents the system retrieves at inference time, usually via RAG — is the primary mitigation, and it works: web-search access reduced hallucination by 73–86% across tested models in grounding benchmarks. But it does not eliminate hallucination, and it fails in different ways than a bare LLM:

  • it can misinterpret the retrieved passage,
  • select the wrong passage,
  • combine multiple sources incorrectly, or
  • fail to recognize an adversarial or nonsensical query.

Google’s Elizabeth Reid drew exactly this line about AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index.: they “generally don’t ‘hallucinate’ or make things up in the ways that other LLM products might” because they’re “built to only show information that is backed up by top web results.” When they get it wrong, she said, it’s “usually for other reasons: misinterpreting queries, misinterpreting a nuance of language on the web, or not having a lot of great information available.” That’s a real distinction — grounded systems fail at retrieval and interpretation more than at pure confabulation — but it is not a guarantee of accuracy. And even RAG-heavy legal research tools have shown hallucination rates up to ~33%, contradicting vendor “hallucination-free” claims. Anthropic says the quiet part plainly in its own developer docs: “while these techniques significantly reduce hallucinations, they don’t eliminate them entirely. Always validate critical information.”

The SEO impact — measurable, and addressable

URL hallucination. This is the most concrete one, and it’s mine to quantify. Analyzing Ahrefs’ own AI referral traffic, I found (in my analysis of Ahrefs’ AI search traffic by page type) that 3.6% of the traffic went to hallucinated pages — pages that don’t exist on ahrefs.com. AI systems (primarily ChatGPT) recommended URLs that were never built. The broader Ahrefs study of 16 million AI-cited URLs (Ryan Law and Xibeijia Guan) puts it in context: AI assistants direct users to 404 pages 2.87x more often than Google Search — ChatGPT’s clicked-through 404 rate was 1.01% vs. Google’s 0.15% baseline. The tactical fix is straightforward: watch referral traffic to 404s, identify hallucinated URLs above a threshold (say, 10 visits/month), and 301-redirect them to the closest real page. You capture traffic the model is trying to send you anyway.

Attribution hallucination. The Columbia/Tow Center study (2025) tested 8 AI search engines and found incorrect answers to over 60% of queries when asked to identify article title, date, publisher, and URL. ChatGPT misidentified 134 articles but signaled uncertainty only 15 times — high-confidence wrong. Over half of some models’ responses cited fabricated URLs. The lesson for SEO: being cited in an AI answer does not mean you were accurately represented. A citation is not comprehension.

The analytics blind spot. This compounds the URL problem. AI traffic is poorly attributed today — some platforms don’t pass referrer data, and Google’s AI Mode used noreferrer, lumping clicks into “Direct”/“Unknown” (Google confirmed that as a bug after I reported it). If hallucinated-URL traffic doesn’t attribute cleanly, you may never see it — the 3.6% finding only surfaced because we had analytics access to look. Fix attribution first, or you’re monitoring blind.

Brand hallucination & reputation. An AI stating wrong facts about your pricing, leadership, or history to a prospect can damage trust before they ever reach your site. Worse, it’s now a negative-SEO vector: Ahrefs’ brand experiment (Makosiewicz) showed that a single seeded Medium article could push some models to propagate misinformation in 37–39% of answers about a brand. “Any growing brand can be knocked off course in AI searchAI search uses large language models and retrieval-augmented generation (RAG) to synthesize an answer from multiple sources rather than returning a ranked list of links. Examples include Google AI Overviews, ChatGPT Search, and Perplexity. results by an upset person with a Medium account.” No links to build or disavow — just false content on an indexed platform.

What to actually do

  1. Redirect hallucinated URLs (the URL-hallucination fix above).
  2. Monitor AI answers about your brand on a schedule — answers shift as models update and as new content gets indexed. One-time audits go stale.
  3. Build entity signals — consistent NAP, schema, Wikidata, official profiles — so grounded systems have clean, verifiable facts to retrieve. This is the single best lever against future brand hallucination.
  4. Verify AI-generated content before you publish it. Unedited hallucinations that reach the web get indexed and can feed the next model’s training — the model-collapse feedback loop. Don’t be a node in it.
  5. Don’t expect crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. blocking to fix it. Blocking GPTBot/ClaudeBot stops future training on your content; it does nothing about facts already in the weights. (See the AI crawlersAI crawlers are bots from AI companies that fetch web pages to train language models, build AI-search indexes, or answer live user questions. They come in three categories, each with its own user-agent tokens and its own robots.txt controls. article for that distinction.)

The honest summary: hallucination is permanent infrastructure, not a passing bug. You can’t make AI stop confabulating. You can make your own facts the cheapest, cleanest thing for it to ground on — and you can catch and redirect the URLs it invents.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.