When an AI tool states something false about a client, the fix is to correct the source the tool draws on, because the AI output itself cannot be edited. Find the source, correct it through that source's own process, report the answer through the engine's feedback channel, and re-test across engines until the error stops. A wrong answer a prospect sees is a visibility problem, not an internal drafting error.
Originally published October 3, 2026. Updated November 4, 2026.
How is this different from a normal factual error in a draft?
A factual error in an agency's own draft is caught and fixed before anything ships, through the review discipline covered throughout this series. A factual error an AI engine states to an outside user, such as a prospect asking ChatGPT what a company does and receiving an inaccurate answer, is public-facing and has to be fixed at the source the engine draws on, not in an internal document.
What are the six steps to correct an AI error about a client?
The six steps below run from confirming the error to checking that it is gone. Each is expanded in the sections that follow.
Reproduce and document the error across engines.
Trace which source the wrong claim comes from.
Correct that source through its own process.
Report the answer through the engine's feedback channel.
Strengthen the client's own reference pages so the right fact is easy to find.
Re-test on a schedule and log the result.
How does a team first discover this kind of error?
Most often a client, a reporter or a prospect mentions that an AI tool told them something incorrect, so ask clients during check-ins whether they have ever received a surprising or inaccurate AI answer about the brand. An agency can also catch errors earlier by running its own prompts on a regular schedule, asking each major engine what it says about the client.
When an error appears, reproduce it before acting. Run the same prompt several times in ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews, and record which engines produce the error and how consistently. A single screenshot from one engine does not show the full picture, because each system uses different sources and modes.
How do you find the source of the wrong answer?
Find the source by reading the citations the engine shows and by matching the wrong claim to pages on the web. Perplexity and Google AI Overviews display their sources directly, and ChatGPT shows links when it uses search. An AI answer is a synthesis of training data and, for engines with live retrieval, current web pages, so the fix has to target the page that holds the wrong fact.
Likely source of the error
Who can correct it
Route
Wikipedia article
Wikipedia's volunteer editors
Talk page edit request with a conflict-of-interest disclosure and an independent source
Client's own website or old bio
The client
Edit the page directly and keep the date current
Old press release or news article
The publisher or wire service
The outlet's own corrections process
Business directory or profile
The listing owner
Edit the profile in the platform, such as a verified Google Business Profile
No identifiable source
No one directly
Report the answer through the engine's feedback control and strengthen the client's reference pages
How do you correct the underlying source?
Correct the source through the process that source accepts, and cite an independent, authoritative reference wherever the platform requires one. The route depends on who owns the page.
For Wikipedia, anyone with a conflict of interest, including an employee, a client or a paid agency, should not edit the article directly. Wikipedia's conflict-of-interest guidance asks such editors to disclose the relationship and request changes on the article's Talk page, using an edit-request template, with the inaccurate statement, the proposed wording and supporting sources. Paid editing is allowed only with disclosure, and undisclosed paid editing is prohibited. See EPR's guide to Wikipedia in the first 24 hours of a crisis for the process.
For the client's own website, correct it first, since engines that retrieve live pages read what is there when they next fetch it. For a third-party article, contact the outlet through its published corrections process rather than a general inquiry.
Can you report the error to the AI company?
Yes, most engines have a feedback control, but these controls are a signal rather than a guaranteed fix. Google documents a path for AI Overviews: use the thumbs-down control, choose Report a problem, pick a category and add details. ChatGPT, Perplexity and Microsoft Copilot also have feedback controls on their answers.
Most major AI companies do not offer a per-fact correction process for brands comparable to a newsroom's corrections desk. OpenAI's personal-data removal request addresses information about a person under privacy law and is not a business correction tool. The reliable path is still the source correction in the previous section, with the engine report as a supplement. Include the prompt, the answer and the authoritative source in each report.
How long does a correction take to show up?
Timing varies by engine, and no AI company publishes a correction timeline. The table describes the mechanism in each case, which is EPR's explanation rather than a measured result.
Engine behavior
What has to happen before the answer changes
Engines with live web retrieval, such as Perplexity, ChatGPT with search and Google AI Overviews
The source page is corrected, then re-crawled or re-fetched. Cited answers can then reflect the correction.
Engines relying more heavily on training snapshots
The error persists until the model is retrained or the engine retrieves a corrected source
A correction rarely appears instantly, which is why the source fix matters more than arguing with the tool about a single wrong answer. Re-test on a schedule rather than once.
How do you prevent the same error from recurring?
Prevent a recurring error by giving engines a clean primary source and by checking secondary sources on a schedule. Three habits help.
Publish one current, well-sourced reference page on the client's own site, such as an accurate about page and an updated bio, so engines have a primary source to cite.
Keep facts consistent across the website, social profiles, directories and press boilerplate, so engines do not have to choose between conflicting versions.
Add the Wikipedia article, if one exists, and the main directory profiles to a quarterly brand review, and keep a log of each prompt, engine, answer and date.
What should a PR team do if ChatGPT or another AI tool says something false about a client?
Reproduce the error across engines, identify the source the answer is drawing on, and correct that source through its own process. Then report the answer through the engine's feedback control and re-test.
How long does it take for an AI answer to reflect a correction?
It varies. Engines that retrieve live web pages can reflect a corrected source once it is re-fetched, while engines relying on training snapshots may keep the error until they are retrained.
Can an agency contact an AI company directly to request a correction?
Most major AI companies do not offer a per-fact correction process for brands the way a news outlet does. Use the engine's feedback control for a signal, and rely on correcting the underlying source.
Can a PR agency edit a client's Wikipedia article?
Not directly if there is a conflict of interest. Wikipedia's guidance is to disclose the relationship and request changes on the Talk page, and undisclosed paid editing is prohibited.
How can a team catch these errors before a client reports one?
Run a standard set of prompts, such as who founded the company and what it does, across the major engines on a regular schedule, and ask clients during check-ins whether they have seen a surprising AI answer about the brand. AI Communications Master Hub: the master pillar for this series.
Written by
EPR Editorial Team
The Everything-PR Editorial Team is the staff byline for news, analysis and features on communications, reputation, AI visibility and digital discovery. Everything-PR has published since 2009. Every article is reviewed by a human editor before publication. Coverage follows the Editorial Policy, and substantive corrections are noted on the article under the Corrections Policy.