A business owner posted in r/aeo on November 3 that ChatGPT kept telling people they had a second location. It had closed months earlier. The team had already pulled the page down and pointed it at a redirect. ChatGPT didn't care.
That's the part almost nobody expects going in. Fixing your own site is necessary. It's rarely what's actually holding an old fact in place, though, once an AI engine has learned it. Chasing the wrong source first wastes weeks a different order would have saved.
Why a redirect alone doesn't fix it
A 301 redirect tells a crawler one specific thing. This page moved somewhere else. It says nothing about the business closing. A crawler that reads "moved" has no reason to drop the old fact from whatever it already believes about you.
One reply in that same thread put it plainly. Bots read a quiet redirect as evidence the content is still out there somewhere, just at a new address. So they keep carrying the old claim forward instead of retiring it.
The fix isn't complicated, even if it's easy to skip under deadline pressure. Replace the silent redirect with a page that states the closure or the change in plain language. Pull any LocalBusiness schema still describing the old location too.
Our AI search readiness checklist covers that entity-trust layer in more depth. A redirect that points to a generic "page not found" message does the same quiet damage. It gives a crawler nothing to update its facts with either.
The old fact usually lives in five other places
Your own website is rarely where an outdated answer actually comes from. It gets repeated because the same fact sits, unfixed, somewhere else an AI engine trusts just as much.
Several of those places don't even hold the fact independently. A handful of data aggregators resell the same business record to dozens of smaller directories and apps, local SEO practitioners have reported for years.
One stale entry at the source can echo across a dozen sites that never touched your business directly. Fixing the aggregator, where you can find it, often does more than fixing five downstream copies one at a time.
| Where it hides | What to check |
|---|---|
| Google Business Profile | Hours, address, category, description |
| Review and map sites | Yelp, Apple Maps, Bing Places |
| Industry directories | Healthgrades, trade and local listings |
| Cached pages | Old press mentions, a cached copy of a deleted page |
| Your own structured data | LocalBusiness or product schema naming the old fact |
A chain with several locations has this problem multiplied. That's why our guide to AEO for multi-location businesses treats Google Business Profile accuracy at scale as its own task, not a line item inside a bigger rebrand checklist.
When the engine is confusing two businesses
Not every case is simply an old fact outliving its expiry date. A few trace back to something messier. The engine is blending your current business with a previous owner, an old brand name, or a competitor with a similar name. No single correction fixes that on its own.
That kind of mix-up usually needs a page that spells out the difference in plain language. Picture how a company that changed its name, or bought out a smaller rival, would explain it to a confused customer on the phone. Without that page, a crawler has nothing to read that disentangles the two identities. The blend just continues.
Google's own Business Profile help forum has page after page of owners who posted this exact complaint. They told the community their own site looked fine, and said nothing changed until they found the real source sitting somewhere else entirely.
We'll show you exactly where your brand stands in AI search.
No commitment. $0 due today, cancel anytime. See how ChatGPT, Perplexity, Claude, Gemini, Grok, Google AI Mode, and Google AI Overviews talk about your brand today.
Fix the highest-authority source first, not the easiest one
Several independent writers landed on the same order after watching this play out. Fix Google Business Profile first. Google's own support threads confirm it feeds Google's own AI answers directly, and it's usually the most copied source behind every other directory listing too. Major directories come next, then smaller local listings, then your own site's schema last, since your site was probably already correct.
It's tempting to start with your own site, since it's the one thing you fully control. Resist that. The highest-authority source usually isn't yours. An engine choosing between two conflicting facts tends to trust the one with more independent backing, not the one edited most recently.
This is also why a single edit rarely closes the loop by itself. A regional directory might pull its listing from a data aggregator that only refreshes every few months. The correction you made on Tuesday can sit invisible to that directory for weeks.
Checking who actually feeds a stubborn directory is tedious work. It's faster, though, than repeating the same fix five times and wondering why nothing changes.
A live answer updates faster than a trained one
Not every engine learns at the same speed. That's worth knowing before you panic about a fix that "didn't work."
Engines that retrieve a live page when they answer, including AI Overviews and most of what Perplexity does, can reflect a correction within days of a recrawl. An answer built mostly from a model's training data moves on a different clock, tied to whenever that model gets updated next.
One reply in the r/aeo thread described this as entity reconciliation, and suggested something simple that most teams skip. Keep running the same handful of local-intent questions every week, on every engine you care about. Log both the answer and whatever sources it cites. That log is the only way to tell which correction actually changed which engine's output, instead of guessing.
Treat the live-retrieval engines as your early warning. Say AI Overviews or Perplexity still repeats the old fact two weeks after you fixed the highest-authority source. The real problem probably isn't the model's memory then. It's a directory or a cached page you haven't found yet, still feeding the answer underneath.
Know exactly what AI says about your competitors.
RankControl's Recon Agent monitors competitor citations across ChatGPT, Perplexity, Claude, Gemini, Grok, Google AI Mode, and Google AI Overviews. See where they show up and you don't.
This is a recheck problem more than a one-time fix
The directory sweep and the schema cleanup are the kind of work you do once and mostly forget. Figuring out whether any of it actually changed what AI engines say is the part that keeps costing time. Most teams don't already have a dashboard for that.
Budget for both separately. The sweep itself, across a handful of directories and your own schema, is realistically a half day to a full day of work the first time through. Checking the same questions across several engines every week is closer to an afternoon a week if someone's doing it by hand, and someone has to notice when one of them quietly reverts.
You can run that weekly recheck yourself with a spreadsheet and some patience. Or you can let it run on its own.
RankControl checks every week whether ChatGPT, Perplexity, Claude, Gemini, Grok and Google's AI surfaces are citing your brand, and whether what they say about you still holds up. Brand Control keeps your current facts in one place, instead of scattered across a dozen half-updated listings. AI visibility tracking is where that weekly check actually shows up.
Build the habit in before the next change
Every one of the fixes above is reactive. The cheaper version happens earlier, the next time a location closes, a price changes, or a product gets discontinued.
Add three things to whatever process already covers a closure or a rebrand. Update Google Business Profile and your two or three biggest directories the same day the change goes live, not whenever someone remembers. Publish the explicit change notice before the old page comes down, not after.
That way there's never a window where a crawler sees nothing but a dead link. Delete the old schema in the same commit as the content change too, since a page that reads correctly to a person can still carry stale LocalBusiness markup a crawler reads instead.
None of that stops the problem from ever happening again. Directories still lag, and a cached page can outlive a correction by months. It does mean the next closure costs a week of cleanup instead of the quarter this one probably took.
A cleanup order that holds up
Start with the fix that removes the ambiguity, then work outward.
- Replace any silent redirect from a closed or changed page with an explicit notice, and delete the schema that still describes the old fact.
- Fix Google Business Profile first. It feeds more downstream answers than almost any other single source.
- Work down the list of directories and review sites that still show the old version, starting with the ones that rank or get cited the most.
- Pick five to ten questions a real buyer would ask, and run them on every engine you care about before you start, so you have something to compare against.
- Recheck the same questions weekly for at least a month. A correction that looks dead after one week sometimes shows up on the third or fourth recheck instead.
26 content formats. Published on your domain. Matched to your brand.
Guides, comparisons, listicles, case studies, and more. RankControl generates content that gets cited by ChatGPT, Perplexity, Claude, Gemini, Grok, Google AI Mode, and Google AI Overviews.
