What to do when Gemini gets a fact about you wrong

You cannot edit Gemini's memory, so the fix has two parts: correct or remove the page the wrong fact came from, and make the right version so easy to find that it is the obvious thing to repeat. If the wrong fact came from training rather than a page, it can stay until the model is updated, and your job is to keep the correct version dominant until then.

First, find out where it came from

Ask the question again and look for links under the answer. If Gemini shows sources, open them. Often the wrong fact is sitting there in plain sight on a page you had forgotten about.

If there are no links and the answer is still confident, one of two things is happening. Either the answer came from training, which means the fact was widely written somewhere before the model was built, or the model filled a gap with something that sounded right. Both look identical from outside, so treat them the same way.

Where the Gemini app offers a way to check the answer against Google Search, use it on the sentence that is wrong. It will not tell you the source, but it will often tell you whether there is a page behind the claim at all, which decides your next hour of work.

The seven places a wrong fact usually lives

In rough order of how often they turn out to be the source, check the following seven.

• An old pricing page of your own that is still indexed, often at a URL nobody links to any more.
• A directory or marketplace listing nobody has updated since the day somebody signed up for it.
• A press release from a funding round, a rebrand or a launch, which lives on wire sites you do not control.
• A PDF or brochure still sitting on your own server. These are indexed, they are rarely updated and almost nobody checks them.
• A comparison page written by a competitor, which may be out of date rather than dishonest.
• Your Google Business Profile and any structured company data attached to it, including an old category or a phone number that has changed.
• A Wikipedia or Wikidata entry, if you have one. These are read widely and copied even more widely.

Work down the list rather than starting with the one that annoys you most. The annoying source is often not the source.

A worked example

This one happened to us. On 6 August 2026 ChatGPT was asked about clawlaw.in, our sister company. Its website and its app store listing carried different plan names and different prices for the same product. ChatGPT noticed the contradiction and said so in its answer. Nothing was hidden and nothing had to be dug out: two public pages of ours disagreed, and the assistant reported the disagreement to the buyer.

That is the worst version of a wrong fact. The buyer is not simply given an old price. The buyer is told that the company's own prices do not match, which reads as carelessness about the exact thing they were about to pay for.

Here is the order that works from there. Correct the pricing page on your own site first and put a last updated date on it. Then make the store listing match it word for word, plan names included, because a near match is still a contradiction. Then search the old price as an exact phrase in quotation marks and work through every copy it returns: your own old blog posts first, then any PDF still sitting on your server, then the third party directories, which are slowest because you have to find out who owns the login.

Now search the old price again. If it still appears anywhere, you are not finished. When it appears nowhere, re-ask the Gemini question weekly and record the answer word for word. The answer in ordinary Google Search will usually change before the Gemini answer does, because Gemini's live half runs through Search.

What to change

• Correct the fact on your own site first, in plain text, on a stable URL, with the date it was last updated.
• State it identically everywhere. When two of your own pages disagree, you have handed the model a choice, and it will sometimes choose the old one.
• Remove or redirect the old page rather than leaving it live and unlinked. An unlinked page is still an indexed page.
• Update the third party listings by hand: directories, review profiles, your Google Business Profile, your company pages on social platforms. This is dull and it is the part that works.
• Where a fact matters commercially, such as pricing or coverage, give it its own page so there is one clear thing to cite.
• Use the feedback control under the Gemini answer. It is worth doing and it will not fix anything today.

What you cannot do

You cannot make a competitor change their comparison page. You cannot have a fact deleted from a model. And you cannot get a promise from anyone that a specific answer will change by a specific date, because the assistants change how they behave without announcing it.

You also cannot fix this with a page that argues with the assistant. A page headed "what Gemini gets wrong about us" is a page about Gemini, not a page about your price. Publish the plain fact instead, on a page built for the question a buyer asks.

What you can do is make the correct version the cheapest thing for the model to find and quote. That is the whole mechanism, and it is slower than people expect.

How to tell whether it worked

Re-ask the same question in a fresh chat, once a week, and record the answer word for word. Watch three things: whether the wrong fact is still there, whether the links now include your corrected page, and whether Google Search itself has picked up the change. Because Gemini's live half runs through Search, Search usually updates first and Gemini follows.

If the fact came from training, expect no movement for a long time, and keep checking anyway. Expect the same fact to reappear occasionally even after it looks fixed, which usually means one more copy of the old version is still out there.

Common questions

How long does a correction take to show up?

There is no published answer and anyone who gives you a number is inventing it. What is predictable is the order: your own page changes immediately, Google Search reflects it after a recrawl, and a grounded Gemini answer can follow after that. A fact that lives in the model's memory rather than on a page is on a different and much longer timescale.

Does the thumbs down feedback button actually do anything?

Google does not publish what happens to individual reports, so treat it as a useful signal rather than a fix. Send it, then go and correct the page. The page is the part you control.

What if the wrong fact is on a competitor's page?

Ask them first, politely and in writing, with the correct value and a link to your own page stating it. Out of date competitor pages are more often stale than malicious. If they refuse, your remaining lever is to make your own statement of the fact clearer, better placed and dated, so there is a better source available for the same question.

Two runs give different answers. Is the fact fixed or not?

Neither, yet. Variation between runs is normal, so a single clean answer is not proof. Record five readings over five weeks. A fact is fixed when the wrong version stops appearing across a run of readings, not when it is absent once.

Should I delete the old page or redirect it?

Redirect it to the page that states the correct fact, unless the old page still has a reason to exist, in which case correct it in place. Deleting leaves a gap and loses whatever links pointed at it. Leaving it live and unlinked is the worst of the three, because it is still indexed and still says the wrong thing.

Is this the same work as fixing it on other assistants?

Mostly yes, and that is the good news. Correcting the source page and removing the contradictions helps on every engine at once. What differs is speed: an engine that always retrieves live tends to reflect a correction sooner than one answering from memory, so use the fastest engine as your early warning that the fix has landed.

What to do first

Take the wrong fact and search it as an exact phrase in ordinary Google search, in quotation marks, today. Every result is a copy you have to deal with. Write them in a list, assign an owner to each one, and start with the copies on your own domain, because those you can fix this afternoon without asking anybody.