A customer asks ChatGPT for an emergency plumber and sees your former branch phone number. Another asks whether your HVAC company offers 24-hour service and gets the hours from a location that closed after an acquisition. The answer looks like a ChatGPT problem, but the correction usually begins with a public source and one specific location record.
OpenAI says ChatGPT search can rewrite a question into targeted web searches, use third-party search providers, account for general or precise location, and show citations or a Sources panel. That gives operators a practical first move: capture the exact answer, identify the source attached to the wrong fact, and correct that source before testing again.
Important
Do not open a company-wide "ChatGPT is wrong" project. Create one incident for one branch, one fact, one prompt, and one source. A wrong phone number needs a different owner than an unsupported service claim.
If you do not know which locations or prompts are affected, check the priority markets and buyer questions where your brand appears before turning one screenshot into a portfolio-wide conclusion.
Start by separating four kinds of wrong answer
The remediation path depends on what ChatGPT actually did. Treat the answer as evidence, not as a diagnosis.
A cited source contains the wrong fact
This is the most direct case. ChatGPT says the Denver branch closes at 5 p.m. and cites a directory page that still shows the former schedule. Save the cited URL, correct the directory if you control it, and document an outreach or dispute if you do not.
The cited source is correct, but the answer misstates it
Save the source passage and the answer together. Correcting the page will not help when the page is already right. Use ChatGPT's feedback tools, then retest the question in a new search response. Do not rewrite an accurate page to match a one-off bad summary.
No visible source is attached
Run the same question with ChatGPT search enabled and open the Sources panel when it is available. OpenAI notes that search responses may include inline citations and a panel with cited sources and other relevant links. If no source appears, record that limitation rather than guessing which directory or profile supplied the statement.
The answer resolves the wrong branch or market
A correct fact about the wrong location is still an operational failure. Capture the location context ChatGPT used, the requested city or service area, the branch it named, and the customer route it supplied. OpenAI says location can influence search relevance, so the same prompt can produce a different local answer in another market.
The industry source-audit workflow explains how to capture source panels and URLs across engines. For an active correction, keep the scope tighter: one wrong fact and the sources visible beside it.
Build a correction record before changing anything
An HVAC group with 60 locations cannot manage these incidents through screenshots in Slack. The evidence needs to join the answer to the approved branch record and the person who can correct the source.
For each incident, record:
- Prompt, ChatGPT mode, market, test date, wrong statement, cited URL, source type, affected branch, approved value, business owner, source owner, correction date, and planned readback dates
- Customer impact, such as a dead phone route, false open status, wrong service claim, old address, closed branch, or confusion with a similarly named company
The approved value should come from operations, not from whichever public profile happens to look newest. A restoration rollup may need dispatch to confirm the phone route, HR or licensing to confirm a practitioner or credential, and the regional GM to confirm whether a service is actually available in that market.
This is a smaller version of the multi-location entity cleanup process. The difference is that a ChatGPT correction record begins with a captured answer and ends with a scheduled readback.
Correct the source that owns the fact
Do not copy the same update across every public surface until the operating team has approved the value. Then fix the places that are wrong, starting with the source ChatGPT cited and the location's owned record.
Fix the location page and structured data together
If your own page shows the wrong hours, phone number, address, or service, update the visible copy first. Then update applicable LocalBusiness structured data so it describes the same facts. Google's LocalBusiness documentation supports location-level properties such as name, address, telephone, hours, URL, and business type. Structured data should describe what a customer can verify on the page.
OpenAI says public websites can appear in ChatGPT search and recommends allowing OAI-SearchBot so site content can be included in summaries and snippets. Its crawler documentation separates OAI-SearchBot from GPTBot. You do not need to open training access to make a corrected page eligible for ChatGPT search.
Fix the public profile when the profile is wrong
Google lets verified businesses edit their address, hours, contact information, website, photos, services, and other profile details. Correct a wrong Google Business Profile because customers use Google Search and Maps, not because a profile edit guarantees a ChatGPT update.
The same rule applies to Bing Places, Apple Business Connect, review platforms, trade directories, and local publications. Fix the surface that contains the error. Do not claim that any one listing is ChatGPT's permanent source of truth. OpenAI says ChatGPT search sometimes works with third-party search providers, and the visible source mix can change by query.
Ask third-party publishers for a precise correction
When an old article or directory page is cited, send the page URL, the exact wrong statement, the approved replacement, and a public source that verifies it. A publisher is more likely to act on a bounded factual correction than a request to "improve our AI visibility."
For a roofing company, that might mean correcting a page that says the branch offers solar installation when it only performs roof repair. For a med spa group, it might mean removing a practitioner who left the location. For a plumbing rollup, it might mean replacing a former acquisition phone number that now reaches another company.
If the affected branch closed, moved, or rebranded, use the closed-location cleanup workflow rather than deleting every old reference. Historical pages may need a clear status and route to the operating location.
Next step
Is AI recommending your business?
Find out how visible you are across ChatGPT, Gemini, Perplexity, and AI Overviews.
Use ChatGPT feedback without confusing it with source repair
OpenAI provides in-product feedback and a content-reporting process. Save the bad response and submit feedback when the answer is inaccurate. Use the reporting flow when the issue is a safety, legal, privacy, impersonation, or policy concern that fits OpenAI's documented categories.
Feedback and source correction do different jobs. Feedback tells OpenAI about the response. Updating a cited directory, owned location page, or public profile corrects the evidence customers and search products can reach. Do both when appropriate, but do not treat a thumbs-down as confirmation that a public business fact has changed.
Pro Tip
Preserve the original answer, source URL, and correction evidence. If the error returns, the team should be able to see whether ChatGPT selected an unchanged source, summarized a correct source badly, or resolved the wrong location.
Keep OAI-SearchBot access separate from training access
A corrected page cannot be selected from your site if OAI-SearchBot is blocked from search inclusion. Check robots.txt, CDN or firewall rules, HTTP status, canonical URL, indexability, and whether the correct facts appear in server-rendered text.
OpenAI's crawler documentation says OAI-SearchBot is used for ChatGPT search, GPTBot is used for content that may support model training, and ChatGPT-User can visit pages during user-initiated actions. Those controls are independent.
The practical policy for a local service site is simple: decide search inclusion and training access separately. The AI crawler access guide covers the robots.txt implementation without treating every OpenAI user agent as the same bot.
Run a 30-day correction workflow
One clean readback is better than ten speculative edits. Use a short incident cycle with named owners.
- Days 1 to 3: Reproduce the answer with the market and ChatGPT mode recorded. Capture citations, source panels, and the approved branch value. Classify the customer impact and assign the source owner.
- Days 4 to 10: Correct the owned page, structured data, profile, directory, or article that contains the wrong fact. Submit precise third-party corrections and ChatGPT feedback where appropriate. Verify the public source itself after the change.
- Days 11 to 30: Retest the original prompt in the same market and add two nearby query variants. Record whether the answer, cited source, named branch, phone route, and service claim are correct. Escalate repeated errors with the full evidence trail.
For a PE-backed platform, the central team should own the incident schema and source standards. Regional operators should approve the real branch facts. Marketing or web teams should update owned pages and profiles. The contact center should independently test phone and booking routes.
Close the incident only after a location-level readback
Do not close the ticket because a CMS, directory dashboard, or Google Business Profile editor says "saved." Read the public page, open the cited source, test the phone or booking route, and rerun the prompt in the affected market.
The final record should say what changed and what did not. A corrected source with an unchanged ChatGPT answer is not a failed source edit. It means the answer still needs observation. A corrected ChatGPT answer with an unchanged bad directory is not a complete fix either, because customers can still find the wrong page directly.
The goal is not to make every answer identical. It is to make the real branch, service, hours, and customer route accurate wherever the source is under your control, then preserve enough evidence to diagnose what ChatGPT shows next.
Sources
- OpenAI: ChatGPT Search. Documents targeted search-query rewrites, third-party search providers, citations, source panels, and location-based results.
- OpenAI: Overview of OpenAI Crawlers. Separates OAI-SearchBot, GPTBot, and ChatGPT-User and explains the search crawler's robots.txt role.
- OpenAI: Publishers and Developers FAQ. Explains how public site content can be discovered, cited, and measured in ChatGPT search.
- OpenAI: Reporting Content in ChatGPT and OpenAI Platforms. Documents response feedback and reporting paths for safety, legal, privacy, and policy concerns.
- Google Business Profile: Edit your Business Profile. Documents the business information a verified merchant can correct on Google Search and Maps.
- Google Search Central: LocalBusiness structured data. Defines location-level business facts that structured data can describe on an owned page.
Amadeus Peterson is the CTO & Co-Founder of Cheers, the local search platform for multi-location service businesses.