ChatGPT Is Wrong About My Business. How Do I Fix It?

By the Alphaa team — we build an AI agent that checks what ChatGPT, Gemini, Claude and Perplexity say about local businesses. Last updated 31 July 2026.

Short answer: You cannot edit what an AI model says, because there is no dashboard, support ticket or API that reaches inside ChatGPT, Claude, Gemini or Perplexity to correct a fact about you. What you can do — and what actually works — is fix the public sources those engines read, make every one of them agree, and then re-check the answer over the following weeks. The fix is upstream of the model, not inside it.

First: which kind of wrong is it?

It is either stale training memory or bad live retrieval. Before you change anything, work out where the error is coming from. There are two mechanisms, and they have completely different repair times.

• Stale training memory. The model absorbed a slice of the public web during training, and that snapshot is frozen at a cutoff date. If it says you are "permanently closed" because you were, briefly, in 2023, it is reciting an old snapshot. Nothing you publish today edits that snapshot.
• Bad retrieval. Most assistants now fetch live web pages at the moment you ask and summarise what they find — retrieval-augmented generation. If a stale directory listing, an old location page or a competitor's comparison article is what gets retrieved, the model faithfully repeats a wrong source. This is the fixable case, and it is the more common one.

How to tell them apart in two minutes

Run this test in the engine that is getting it wrong:

1. Ask the question plainly: "What are the opening hours for [business name] in [city]?"
2. Ask it again with an explicit instruction to search and cite: "Search the web and give me your sources for that."
3. Read the citations it returns.

If the second answer is correct and cites your website, the error was training memory surfacing when no search ran — annoying, but it fades as engines lean harder on live retrieval. If the second answer is still wrong and names a source, you have found your culprit: that specific page is what needs fixing. If it cites nothing and hedges, the engine has too little to go on about you at all, which is a different problem — see how AI actually identifies your business.

What wrong information do AI engines most often give about businesses?

The six most common errors are closed-or-moved flags, wrong hours or phone numbers, entity collisions, invented services, stale pricing, and wrong ownership or staff.

• Closed or moved. An old "permanently closed" flag or a previous address that still lives on a directory nobody has logged into for four years.
• Wrong hours or phone number. Usually a legacy listing with a disconnected line, or holiday hours that were never reverted.
• Entity collision. The model has merged you with a similarly named business — a different franchise of the same chain, or a company with your name in another state. This is the hardest one, and the one that most often produces confidently wrong detail.
• Invented services. The model lists something you do not offer, generally because it generalised from your category rather than reading your page.
• Stale pricing. A three-year-old blog post or an old PDF price list still ranks and still gets retrieved.
• Wrong ownership or staff. A departed partner still named as principal, usually because a press release or bar/association directory outlived them.

How do you correct wrong AI information about your business?

Fix each error at its source, starting with your Google Business Profile and then your own site's canonical facts. Work top to bottom. The order matters — the earlier items are re-crawled most often and carry the most weight, so fixing them first changes answers soonest.

1. Google Business Profile. Claim it if you have not, then correct name, address, phone, hours, and category. If it is wrongly marked closed, use the reinstatement flow rather than creating a second profile — duplicates make entity collision worse, not better.
2. Your own site's canonical facts. Put your legal name, address, phone, hours and service list in plain HTML text on a page that is easy to find, and mirror it in LocalBusiness JSON-LD schema with name, address, telephone and openingHoursSpecification. Add a sameAs array pointing at your own verified profiles — that is the machine-readable way of saying "these listings are all me."
3. The specific source the engine cited. If step one of the diagnosis named a page, go fix that page. Most directories have a "suggest an edit" or claim flow. This single step resolves more cases than everything below it.
4. The other major listings. Apple Business Connect, Bing Places, Yelp, and the two or three directories that dominate your industry. Stale entries here keep re-seeding the wrong fact after you have fixed everything else.
5. Old pages on your own domain. Do not simply delete a stale location or pricing page — a deleted page can linger in caches and third-party copies with no corrected version to replace it. Update it in place, or 301-redirect it to the current page so the correct fact inherits the link.
6. An explicit disambiguation sentence when you have an entity collision. One plain line on your about page — "[Your business] in [city] is independently owned and is not affiliated with [similarly named company]" — gives a retrieval system something concrete to separate you on. It reads as helpful to humans too, which is the test for whether a tactic is legitimate.

How long does a correction take?

Honestly: it depends on the mechanism, and nobody can promise you a date.

• Retrieval-driven errors: often days to a few weeks, once the corrected page has been re-crawled. The engine is reading live; when the source changes, the answer can change.
• Directory-driven errors: gated by that directory's own moderation queue, which can run from 48 hours to several weeks.
• Training-baked errors: persist until the model is retrained or until live retrieval reliably overrides them. You do not control that schedule. What you can do is make the correct version so consistent and easy to retrieve that the model prefers it.

Expect variation between engines and between phrasings of the same question — that is normal model behaviour, not a sign your fix failed. We wrote about why identical questions produce different answers in why AI answers change every time.

What wrong AI information can you not fix?

You cannot rewrite a model's weights, make an engine ignore honest negative reviews, or guarantee the exact wording of an answer.

• The model's weights. No vendor can reach in and rewrite them. If someone offers to, that is the clearest snake-oil signal there is.
• Honest negative reviews. You can respond to them; you cannot make an engine ignore them, and attempting to suppress them tends to backfire publicly.
• Guaranteed wording. Even with perfect sources, you influence probabilities, not output. Anyone selling a guaranteed AI answer is selling something that does not exist.

How do you know a correction has worked?

A correction is not done when you submit the edit; it is done when the answer changes. Keep a simple log: the exact question, the engine, the date, and the answer you got. Re-run the same three or four questions monthly across ChatGPT, Claude, Gemini and Perplexity, and record the result verbatim. That log is the only real evidence you have — and it is also what tells you which of your fixes did the work. If you want the manual method for capturing those answers, see how to see what ChatGPT says about your business.

What else do owners ask about fixing wrong AI information?

Can I contact OpenAI or Google to correct a fact?

There is no general correction channel for business facts. Google Business Profile has its own edit and redressal routes for its data, but the assistants themselves take corrections only by re-reading public sources.

What if a competitor is spreading the wrong information?

Treat it as a source problem. Correct the record where you can, publish the accurate fact clearly on your own site, and get it corroborated elsewhere so the consensus moves.

Does the wrong answer disappear everywhere at once?

No. Retrieval-driven errors clear within days to weeks once the sources change, while anything baked into training knowledge persists until the model is updated.

Do I need to ask for the old page to be removed?

Where you control it, yes, and redirect it. A contradicting page that stays live keeps feeding the engine the fact you are trying to correct.

What actually fixes a wrong AI answer?

Fixing the source does, because a wrong AI answer is almost always a wrong source, not a broken model. Diagnose which source, fix it at the origin, make every other public record agree, and then verify over weeks rather than hours. That is unglamorous work, and it is the only version of this that actually holds — because the next time an engine looks you up, it reads the same public record you just corrected.

The key takeaway is to trace each wrong answer to the public source feeding it, correct it there, make every other record agree, and re-check monthly until the answer changes.

Run the free AI check →