When an AI assistant gets your business details wrong, preserve the answer, establish the correct fact and investigate the public records that may be contributing to the mistake. Correct what you control, request changes from relevant external publishers and test again under recorded conditions. You can improve the evidence available without promising that every future answer will immediately change.
The priority is the consequence for a customer. A wrong office address, unavailable service or invented professional qualification deserves a different response from a slightly awkward description of your business. Treat the problem as an accuracy issue with a documented resolution process, rather than a contest to persuade one chat conversation to say something nicer.
Capture the mistake before trying to fix it
Save the full question and answer, the platform, date and time, visible sources and any relevant settings. Record whether web search was used when that is visible. Include the location specified in the question and enough surrounding conversation to understand whether an earlier message shaped the answer. A cropped screenshot of the wrong sentence may lose the context needed to investigate it.
Keep the evidence in an internal record. If the answer exposes personal information or makes a serious allegation, avoid circulating it more widely than necessary. The people investigating need the exact text; a public social post repeating the error may create another version that readers encounter.
Distinguish what you observed from what you infer. “The answer gave our previous address on this date” is an observation. “The assistant copied a particular directory” is an inference unless the available evidence establishes that relationship. Even a citation beside the answer may support only part of the statement.
OpenAI’s guidance on checking search sources acknowledges that cited results can be outdated or incorrect. Use citations as investigation leads, then inspect them. Asking the assistant where it found a claim may be useful, but the explanation is not a substitute for checking the actual pages.
Establish a reliable version of the business facts
Before contacting anyone, agree on the correct information internally. Businesses sometimes discover that the website, reception script and business profile disagree because the underlying operational decision was never documented. An address may be a registered address, a mailing address or a place customers can visit. Those meanings are not interchangeable.
Create a compact record of the affected fact, its correct wording, the responsible person and the supporting evidence. For opening hours, distinguish reception availability from service delivery. For geographic coverage, distinguish a physical office from a place you travel to. For qualifications, use the exact credential and its relevant holder rather than a broad label that sounds more impressive.
A hypothetical mobile veterinary service illustrates the problem. An assistant says customers can bring animals to its administrative address. The business must first confirm that no public appointments take place there. The correct statement is about the service model, not merely a different street address. Replacing one location without explaining mobile visits would leave the central confusion unresolved.
Our guide to business entity information covers the broader task of making business identity understandable. In a correction project, start with the narrow fact causing harm and then check the related records that could recreate it.
Classify the error so the response fits
Useful categories include outdated information, confused identity, unsupported inference and misleading context. An old phone number is usually an outdated record problem. A qualification belonging to a similarly named business may indicate identity confusion. A claim that you offer a service because you wrote an article about it is an inference problem.
The category influences the work. Outdated information calls for replacement and removal of obsolete instructions. Identity confusion may require clearer business names, locations and ownership relationships. An unsupported inference may need the website to distinguish educational content from services offered, especially if a page currently leaves that distinction vague.
Also assess urgency. Wrong directions to a public location can affect customers immediately. A false claim about emergency availability can have a more serious consequence than a misspelt brand name. Put the operational issue in front of the right person while the marketing team investigates the information trail.
Do not assume every unwanted answer is a factual error. An assistant may omit your business or describe a competitor favourably without making a verifiably false statement about you. Those observations belong in a visibility review. The correction workflow is strongest when it focuses on facts that can be stated and evidenced clearly.
Inspect the obvious sources and the quieter duplicates
Start with linked sources, then inspect the pages a customer would naturally use to verify the fact. These can include your contact page, location pages, service pages, business profiles and relevant directory entries. Search for the exact incorrect detail, such as the previous phone number, rather than only searching the business name.
Look beyond the current navigation. An old downloadable brochure, archived service page or outdated staff biography may still be public. A footer can repeat a former address across many pages. An image can contain information that has changed even though the surrounding text is current. A booking provider may display its own version of your hours.
Record source candidates without claiming certainty about the assistant’s internal process. The useful question is whether each public record is accurate and worth correcting for readers anyway. You do not need to prove a particular page caused the answer before fixing a clearly obsolete instruction on your own website.
Avoid trying to erase legitimate historical material merely because it contains an old fact. A dated announcement about a former office can remain accurate as history. It may need a clear update or link to the current contact details, rather than being rewritten to imply the business never moved. Context can resolve a contradiction more honestly than deletion.
Sometimes the investigation finds no public page containing the exact error. Record that result rather than inventing a source explanation. The answer may combine details, misunderstand context or rely on information you cannot identify from the visible response. You can still improve a confusing owned page and submit relevant platform feedback without claiming to have located the origin.
In that situation, write a correction statement for readers, not a page designed to argue with an assistant. A clear account of your actual services and contact arrangements is useful. Repeating the false claim throughout several new pages may make the website harder to understand and create more material that needs maintenance. One authoritative explanation, supported by consistent records, is a more manageable editorial choice.
Keep separate statuses for source correction and answer observation. The source work can be complete while the answer remains unresolved. An external publisher can accept a correction while the updated page has not yet been observed in a later answer. These distinctions prevent a team from reopening finished tasks simply because a different part of the process still has uncertainty.
They also make handovers easier. A colleague should be able to see which records were checked, which requests are pending and which observations still need review. Without that separation, the task can become an endless instruction to check AI again, with nobody knowing what evidence would justify a different next step.
Correct the pages and profiles you control first
Update the authoritative page for the fact and the repeated references that depend on it. If your contact page changes, check the footer, location pages, appointment instructions and downloadable materials. Confirm that any structured information generated by the website reflects the visible content. A clean contact page is not enough if a plugin continues publishing an old phone number.
For Google, verified Business Profiles can be edited to update information such as hours, addresses and contact details. Use the account authorised to manage the actual business. Do not create duplicate profiles or fictitious locations as a shortcut around an inaccurate record.
Keep the correction specific. If a service has been discontinued, explain the current service scope where customers are likely to look. Avoid leaving a prominent promotional page with a small contradictory note at the bottom. If the old URL remains useful, it can explain the change and direct readers appropriately, subject to your website plan.
The best wording answers the customer’s practical question. “Appointments are provided at your property within our stated service area” may resolve more confusion than a generic sentence saying the business information was updated. The correction should improve the website even if the assistant never revisits the disputed answer.
Request external corrections with concise evidence
For a directory, partner site or publisher you do not control, identify the legitimate edit or support route. Provide the URL, the precise incorrect statement, the correct replacement and evidence suitable for that organisation’s review. A focused request is easier to assess than a long complaint about AI in general.
Separate factual corrections from promotional requests. Asking a publisher to replace an obsolete phone number is different from asking it to endorse you or add favourable claims. Do not present a marketing preference as proof that an independent description is false. Keep a record of what was requested and when, including any confirmation received.
Some publishers may require ownership verification or their own investigation. Follow that process and avoid sending confidential documents unnecessarily. If a record is genuinely disputed or involves professional status, have the appropriate person supply the evidence. The marketing team should not invent a credential or make legal assertions to accelerate a change.
A practical directory and profile cleanup prioritises records customers are likely to use and records containing consequential mistakes. There is little value in spending days chasing an obscure harmless variation while the booking platform still sends customers to the wrong place.
Notify discovery systems without promising a refresh date
After meaningful website changes, make sure the updated pages remain accessible and can be discovered. Depending on the site and account access, this may include checking the sitemap and requesting inspection or recrawling through the relevant tools. Treat these as technical follow through, not a guarantee that an assistant will use the new version.
Google’s recrawl guidance makes clear that a request does not guarantee immediate inclusion. Repeating the same request does not create a reliable deadline. Record what was submitted so the team can later distinguish an unsubmitted change from a submitted change awaiting further observation.
For participating search engines, IndexNow can notify them of changed URLs. Notification is different from indexing, and each search engine makes its own decisions. It is not a direct instruction to every AI assistant to replace an answer.
Avoid broad technical changes made in frustration. Blocking crawlers, removing important pages or excluding a whole site from search may have consequences beyond the incorrect answer you are trying to fix. If a control is being considered, define the desired outcome and assess its scope separately from the accuracy correction.
Test the correction with a stable question
Retest the original question under conditions you can describe. Record the same business name, location and service context. Use a fresh conversation when that is part of your method, and note the visible product or search mode. The aim is a comparable observation, not an attempt to reproduce a perfectly controlled laboratory environment.
Keep the first result, including an unchanged or disappointing answer. Repeating the question until a favourable answer appears and retaining only that screenshot creates a misleading record. If you run several observations, keep all of them and report the pattern within that small sample.
A changed answer is evidence that a different answer appeared. It does not prove which correction caused it or establish that every user will now see the same information. Conversely, one repeated error does not establish that the source corrections failed; the public records may be accurate even while the answer remains inconsistent.
A prompt tracking set can make this work more orderly. Keep accuracy tests separate from broad category visibility tests so an improvement in correct opening hours does not disappear inside a score based on whether your business was recommended for unrelated questions.
Work through a complete hypothetical correction
Consider an illustrative architecture practice that moved from a public studio to appointments at a new location. An assistant gives the former address and says visitors can drop in. The team saves the answer and confirms two correct facts: the current address and the requirement to book an appointment. No claim is made here about a real practice or a measured result.
The investigation finds a current contact page, an old project brochure, an outdated directory entry and a footer that still names the former studio. The team corrects the footer, adds a clear appointment instruction to the contact page and updates the brochure’s contact section. It asks the directory to amend its record using the publisher’s normal process.
The task record distinguishes completed website changes from the pending directory request. It also notes the page review and any discovery notification. When the original prompt is checked again, the team records whether the answer gives the right address, the right visiting arrangement and a relevant source. Those are separate checks because one can improve while another remains wrong.
If the next answer omits visiting instructions entirely, the team does not mark the whole issue resolved. It records that the wrong address was not observed and that appointment accuracy was not established by that response. This modest wording gives the business a dependable record and a clear reason for any further action.
Decide when the work is complete enough
Completion should be defined by actions and observations you can verify. Your owned records are corrected, important external requests have been made or resolved, and the agreed test has been repeated with its outcome recorded. Remaining uncertainty about future assistant answers should be stated rather than hidden behind an absolute success claim.
Some problems need escalation beyond marketing. Serious false allegations, impersonation or exposure of private information may require the platform’s relevant reporting route and advice appropriate to the issue. Keep the factual correction evidence intact. Do not promise a removal outcome that depends on another organisation’s assessment.
Assign ongoing ownership of the business facts most likely to change. A staff member updating opening hours should know which pages and profiles depend on them. A service change should trigger a review of relevant booking and promotional content. Preventing contradictory records is usually more manageable than repeatedly investigating the same error after publication.
Star Digital AI Marketing’s AI visibility reporting service can bring accuracy observations into a broader review of how your business is represented. If an assistant is publishing the wrong details, contact our team to discuss the evidence, correction priorities and a sensible way to monitor what happens next.
