How to Fix 404 Errors From ChatGPT in WordPress

Someone asks ChatGPT a question. It gives a genuinely helpful answer, recommends your site—your site!—and hands over a link. The visitor clicks, lands on your page and… « 404 – Not found ». The link never existed: the AI made it up. This isn’t a rare glitch, it’s now a measured, documented pattern across every AI assistant, and it’s quietly costing you the most motivated visitors you’ll ever get. The good news: catching those invented URLs and turning them into working redirects takes about ten minutes to set up. Let me show you.

The essentials

• SE Ranking analyzed 145,463 URLs cited by ChatGPT (December 2025): 1.34 % returned a client error, and 91 % of those errors were 404s.
• ChatGPT links to dead pages about twice as often as Google’s AI Overviews (1.22 % of cited URLs vs 0.56 %) and roughly twice as often as classic organic results (0.65 %).
• In a separate real-world audit, Go Fish Digital found 3.35 % of visits sent by ChatGPT landed on a 404—about one broken visit for every 30 clicks, across 18,000+ landing pages.
• The fix is not blocking AI—it’s logging your 404s with their referrer, then redirecting the invented URLs to the closest real page.
• Blaminhor Essentials does this natively: 404 monitor with referrer and hit count, plus a one-click 301—and a WP-CLI mirror (wp blaminhor redirections 404-list).

Why does ChatGPT send visitors to pages that don’t exist?

Because a language model doesn’t look up URLs—it predicts them, one piece at a time, exactly like it predicts the next word of a sentence. When an assistant wants to link to your pricing page and hasn’t stored the real address, it completes the pattern with what a pricing URL usually looks like: /pricing, /plans, /tarifs. Often the guess is right. When it’s wrong, the model has just invented—« hallucinated », in AI jargon—a page you never created.

Three flavors of this problem show up in the data:

• Pure inventions: URLs that never existed anywhere. The model assembled a plausible slug out of thin air.
• Stale memories: the page existed when the model was trained, but you’ve since renamed, merged or deleted it. The AI’s snapshot of your site is months or years old.
• Mangled copies: a real URL with a typo, a truncated ending, or two paths spliced together.

And it’s not just ChatGPT, even if it’s the biggest offender. The SE Ranking study measured dead links across ChatGPT (1.22 % of cited URLs), Google’s AI Mode (0.87 %) and AI Overviews (0.56 %)—all above zero, and the assistants people click from the most sit at the top. Search Engine Journal summed it up: AI search sends users to 404 pages nearly three times more often than Google’s classic results.

How do you find the 404s that AI assistants create?

The magic word is « referrer »: when a visitor clicks from ChatGPT, their request carries chatgpt.com as the referring site—so a 404 log that records referrers shows you exactly which dead URLs the AI is sending people to. The same goes for perplexity.ai, Claude’s claude.ai, or Gemini traffic. No referrer guessing games, no log-file archaeology: the source is written on every hit.

The catch is that WordPress doesn’t record any of this by default. Your classic options each have a hole in them:

• Google Search Console shows 404s that Googlebot crawled—not the ones your human visitors hit five minutes ago from an AI answer.
• GA4 can track 404 hits, but only after you build a custom event setup around your error template. Nobody does this before they have the problem.
• Raw server logs contain everything… on hosts that let you access them, in a format you’ll be grepping at midnight.

A server-side 404 monitor closes the gap: it sits in WordPress itself, notices every request that ends as « page not found », and stores the path, the referrer, and how many times it happened. That last number matters—a URL hit 47 times is a pattern worth fixing; a URL hit once is probably a bot typo you can ignore.

Redirect, rebuild, or ignore: what do you do with each 404?

Not every 404 deserves a fix. Sort each URL by what it tried to reach, and give it one of four answers: a 301 to the closest real page, a brand-new page, a deliberate 410, or nothing at all.

The 404 you’re looking at	What to do	Why
Close real equivalent exists (/pricing → your /plans page)	301 redirect	Passes the visitor—and any link signals—to the right destination
Recurring URL with real intent, no equivalent (AI keeps inventing /api-docs)	Create the page	The AI is showing you demand; Go Fish Digital found these worth building
You deleted it on purpose and want it forgotten	410 Gone	Tells crawlers « stop asking », faster de-indexing than a 404
One-off garbage, bot probes, random strings	Nothing	An honest 404 is the correct answer to a meaningless question

One trap to step around: do not mass-redirect every 404 to your homepage. Google treats those as soft 404s, and the humans feel it too—they asked for something specific and got dumped at the front door. Redirect only when there’s a genuinely close match, and let the rest 404 with dignity. If you’re hazy on what a 404 actually is, I’ve got a whole definition article for you.

The second row of that table is the counterintuitive one, and it’s my favorite: a hallucinated URL that keeps coming back is free market research. If ChatGPT keeps inventing yoursite.com/templates because that’s what it expects a site like yours to have, real people keep wanting that page. Some SEOs now deliberately build the pages AI keeps making up—the AI already promised the content on your behalf; you just have to keep the promise.

How do you set this up in WordPress with Blaminhor Essentials?

The Redirections module of Blaminhor Essentials ships a 404 monitor and a one-click « redirect » action on every logged entry—here’s the whole setup, and the honest fine print.

1. Install Blaminhor Essentials and enable the Redirections module (it’s modular: everything you don’t enable stays off and loads nothing).
2. In the module settings, switch on the 404 monitor and pick a retention window—30 days by default, 1 to 365 if you want more or less history.
3. Let it run for a few days. Real traffic does the discovery for you.
4. Open the 404 Monitor tab: entries are sorted by hit count, and each row shows the path, first/last seen dates, and the referrer—this is where chatgpt.com gives the game away.
5. On any row worth fixing, click the redirect action, type the target URL, done. The 301 is live immediately, and the entry disappears from the log—resolved is resolved.

Because the redirect engine runs before the monitor logs anything, a URL you’ve just fixed stops appearing in the list—the log only ever contains your remaining problems, not your solved ones.

If you live in a terminal (or you let an AI assistant handle your maintenance), every step has a WP-CLI mirror:

wp blaminhor redirections 404-list
wp blaminhor redirections 404-to-redirect 7 --target=/new-page/

The fine print, because you should know what a tool does before trusting it:

• The monitor logs the path only, never query strings—cleaner grouping, and no personal data from URLs ending up in your database.
• It records GET and HEAD requests only, and caps the table at 5,000 distinct URLs, so a bot flooding you with random paths can’t bloat your database.
• A daily cleanup purges entries older than your retention window.
• Redirect rules support plain matches and regex—and a regex that fails at runtime is automatically disabled and logged instead of silently breaking your site.

I set the whole flow up on a clean test site while writing this article: enabled the monitor, hit a handful of invented URLs with a ChatGPT referrer, watched them stack up in the log with their hit counts, then clicked one into a 301. The redirect answered instantly on the next request, and the log entry was gone. From « the AI invented a URL » to « that URL now lands somewhere useful » is genuinely one click.

Can you stop AI assistants from inventing your URLs in the first place?

Not really—the invention happens inside the model, on infrastructure you’ll never touch. What you control is the landing. Still, two habits shrink the problem over time:

• Keep your URLs boring and stable. Every slug change creates a future stale memory in some model’s training data. When you do rename a page, ship the 301 redirect the same minute.
• Help the models learn your real structure. An llms.txt file hands AI crawlers a curated map of your actual pages—no guarantee they’ll use it, but it’s your structure, stated plainly, at a standard address.

And to be clear about the tempting nuclear option: blocking AI crawlers doesn’t fix this. Hallucinated links come from what models already learned or guess—blocking future crawls just means fewer citations for you, while the invented URLs keep coming. If AI assistants are sending you visitors, the winning move is to catch them, not to lock the door.

One click between a lost visitor and a won one

Every hallucinated URL is a visitor who was promised your content and hit a wall instead. You can’t stop AI assistants from guessing—but a 404 log with referrers turns their guesses into a to-do list, and a one-click 301 clears that list faster than ChatGPT can refill it.

The 404 monitor is one module among twenty-plus in Blaminhor Essentials, the modular free plugin I build precisely for this kind of quiet, unglamorous problem—enable what you need, ignore the rest, pay nothing.