What Is a Hallucinated URL?
A hallucinated URL is a hyperlink an AI system fabricates — a path on your domain (or someone else's) that looks plausible but has never existed. LLMs learn URL patterns from billions of links during training, so when a user asks for a source, models without live retrieval often generate one that matches the pattern rather than reality: yourdomain.com/pricing-2026 or /docs/api/quickstart on a site that never had docs.
Why do hallucinated URLs happen?
Language models are next-token predictors, and URLs are among the most formulaic text on the web. Common site structures — /pricing, /features, /blog/{slug} — appear so often in training data that the model can complete a convincing path for any domain. Retrieval-backed engines mostly cite real fetched links, but chat modes without browsing, coding assistants, and answers composed partly from memory still emit invented ones. The behavior is a URL-shaped case of confabulation: fluent, confident, wrong.
How do you detect hallucinated URLs in your logs?
Your server logs are the ground truth. Look for:
- 404 responses on paths you never published, especially recurring ones with clean, human-readable slugs.
- Referrers from AI surfaces —
chatgpt.com,perplexity.ai,copilot.microsoft.com— landing on nonexistent paths. - Clusters: the same phantom URL hit repeatedly is a signal one engine keeps generating it for a popular prompt.
A monthly query grouping 404s by path and referrer usually surfaces the pattern in minutes; teams doing regular log analysis treat recurring AI-referred 404s as a standing report.
How do you turn phantom 404s into traffic?
Every hit on a hallucinated URL is a real person with real intent whom an AI sent to you. The fix is mechanical: 301-redirect each recurring phantom path to the closest genuine page. /pricing-plans redirects to /pricing; an invented /docs/integrations/slack goes to your actual integrations page. Some teams go further and publish a real page at a frequently hallucinated path when the intent is clear and no equivalent exists — effectively letting the models tell you what content users expect.
Example
After ChatGPT repeatedly cited a nonexistent /comparison/competitor-x page for one SaaS brand, the team saw dozens of AI-referred 404s per week in their logs. They shipped a real comparison page at that exact path; the 404s became sessions, and the page itself began earning citations — a case of hallucination revealing demand. Related failure modes are cataloged across this glossary.
Frequently asked questions
- Why do LLMs invent URLs instead of admitting they don't know one?
- Models generate the statistically plausible next token, and URL patterns are highly predictable — /pricing, /docs/getting-started, /blog/{topic}. Without retrieval verifying the link exists, the model completes the pattern confidently.
- Should you redirect hallucinated URLs or return 404?
- Redirect the recurring ones. A visitor arriving from an AI answer had real intent; a 301 to the closest real page recovers that visit. Reserve 404s for one-off noise and keep redirects out of your sitemap.
Keep exploring
See how AI engines talk about your brand — track mentions across ChatGPT, Perplexity, Claude, Gemini and 5 more. Start with Menra