An updated page and a corrected AI answer are separate states. Keep the approved fact, source changes and subsequent checks in one versioned record.
Published by Gist, which makes Gist GEO.
Sources checked October 19, 2026.
“The Downtown branch
closes at 2 p.m. on
18 December 2026.”
A customer arrives after closing because an AI answer showed last month’s hours. A prospect expects a price that applies only to annual billing. Another asks for a service your nearest branch has never offered.
These errors need a precise correction. Start by confirming the product, location, and date behind the answer. Then update the public records you control, request corrections where appropriate, and check whether subsequent answers reflect the right facts.
Gist’s broader brand-correction playbook covers the wider problem. This checklist focuses on operational facts that change by time, place, or purchase conditions. Its working document is a correction ledger: one record for each fact, with a history of what changed and what you observed afterward.
A correct number with the wrong qualification is still misleading. Choose a fact type to see the scope that must travel with it.
Location name and full address
Local time zone and applicable date
Normal weekly schedule
Date-specific exception or temporary closure
Separate delivery/pickup/service hours
Public location page and booking display
Save the complete answer, exact question, visible citations, engine, surface, and timestamp. Record any location context and the date the customer asked about. Preserve a screenshot or transcript before you make changes.
Copy the incorrect statement exactly into the ledger. Then identify the business entity it describes:
An answer saying “$39 per month” may have omitted annual billing rather than repeated an obsolete price. “Open until 8 p.m.” may describe a different branch. Diagnose the specific mismatch before replacing a number everywhere.
Check each cited page. If a page contains the same incorrect current fact, record a public-source error. If none of the pages you examined supports the claim, record “unsupported by examined sources.” That label preserves uncertainty about where the answer came from. It does not prove a particular training source, cache, or fabrication mechanism.
Ask the person responsible for pricing, branch operations, or service delivery to approve the correction. A draft landing page or a colleague’s recollection is a weak source of truth.
Record the approved wording, who approved it, when it takes effect, and when it stops applying. Choose a public page where a customer can verify the fact. Keep confidential contracts or customer-specific prices out of that public evidence.
The team may need to resolve an internal disagreement first. If the booking page and the branch manager give different hours, there is no reliable correction to distribute yet.
Use the relevant checklist below to write a statement with enough context to stand on its own.
Confirm:
For illustration, “Team costs $39 per month” is incomplete if $39 is a monthly equivalent on an annual subscription. A clearer hypothetical statement is: “The Team plan costs USD 468 per user billed annually, equivalent to USD 39 per month, or USD 49 per user per month billed monthly.” Include any actual minimum seat requirement, tax treatment, and commitment details next to the price.
If your business uses custom quotes, publish the real quoting conditions. Do not invent a universal starting price to make the page easier to summarize.
Update the primary pricing page and check linked plan comparisons, checkout or booking flows, public PDFs, and promotional pages that still present an older price as current. Keep genuinely historical material dated and clearly labeled; a past price may be accurate for the period it describes.
For retailers using Merchant Center, separately check the submitted product data. Google requires the amount and currency to match the landing and checkout pages. Correct the affected variant and market, rather than assuming one feed value covers every offer. Google Merchant Center price requirements
Confirm the location name, full address, local time zone, and date. Then distinguish:
Keep phone support and online ordering availability separate from the hours customers can enter a physical location.
For illustration, a branch might normally close at 6 p.m. but close at 2 p.m. on a particular date. Both facts belong in the record, with the exception attached to that date and branch. Replacing the recurring schedule would create a new error after the exception passes.
In Google Business Profile, use Edit profile, then Hours, to review the normal week. Google documents separate entries for breaks in the day. Edit business hours
Special hours handles date-specific changes and closures of up to six consecutive days. Google says closures lasting seven days or more, or an unknown duration, use Temporarily closed. Special hours require the profile to be set to Open with main hours. More hours covers supported service-specific schedules. Google’s Special hours guidance
Check the matching location page and booking or ordering flow as well. Have the local operator verify the final display, especially when a schedule crosses midnight or the business has locations in different time zones.
Confirm exactly what is available and where. Record any appointment requirement, geographic service area, customer eligibility, or start and end date.
A business-wide list can be misleading when only one branch provides a service. Give customers a branch-level answer they can verify. If a service has ended, remove current availability claims from the booking path and relevant location pages, and label historical announcements appropriately.
Where Google Business Profile offers the services editor for your business category, open Edit services and select the affected service. You can update its description and price or remove it. Google advises against putting prices or phone numbers in custom service names; use the appropriate details instead. Manage Business Profile services
The ledger below is invented, but the distinction is operational: fixing a public source does not tell you what a later answer says.
“The Downtown branch closes at 2 p.m. local time on 18 December 2026; the normal weekly schedule resumes afterward.”
Use the ledger to assign a separate status to each affected source:
Owned website. Update the approved fact where customers actually use it. Check any structured data or other site-generated representation of the same fact for contradictions. Save the before-and-after versions and publication time.
Managed profile. Have an authorized owner or manager update the relevant listing, then verify the public display. For Bing Maps listings, Microsoft directs businesses to Bing Places to claim or update the record, with availability varying by region. That route updates the listing; it does not promise a corrected Copilot answer. Microsoft’s listing guidance
Independent page. If a directory or publisher still describes an old fact as current, use its correction process and provide the approved public evidence. Record the request and any response. A historical article may need contextual clarification rather than removal of an accurate historical statement.
A submitted profile change is still pending work. Google reviews Business Profile edits and distinguishes accepted, pending, and not-approved statuses. Check which status you actually have. Understand Business Profile edits
For changed pages you manage, Google offers a recrawl request through Search Console. Its documentation says crawling can take days to weeks and inclusion is not guaranteed. A recrawl request is not a deadline for any AI answer to refresh. Ask Google to recrawl
Give each fact a stable ID. Create a new version when the approved fact or its scope changes, and append each verification result. Do not overwrite the original wrong answer when a later one looks correct.
Use these fields:
Fact ID and version: A stable reference and revision number.
Entity and scope: Product or branch, market, currency where relevant, and applicable date.
Observed error: Exact statement, saved answer, question, engine, surface, and capture time.
Approved correction: Full wording, effective period, approving owner, and public evidence URL.
Source diagnosis: Incorrect public source, unsupported by examined sources, or still unresolved.
Action history: Each affected URL or profile, assigned owner, submitted date, publication or acceptance status, and before-and-after evidence.
Retest history: Original question, test conditions, answer date, factual outcome, and source links.
Next review: A date or event, such as the day before exceptional opening hours or the next approved price change.
Here is an illustrative ledger record:
Fact H-014, version 2. Downtown branch. Incorrect answer: “Open until 6 p.m. on 18 December.” Approved correction: “The Downtown branch closes at 2 p.m. local time on 18 December 2026; the normal weekly schedule resumes afterward.” Operations owner approved the exception. Location page updated; profile edit pending. Next check: verify the public profile after acceptance, then repeat the saved date-specific question. No claim has yet been made about subsequent AI answers.
When the public facts are clear but an answer still states something wrong, submit concise feedback through the engine’s current channel. Include the exact statement, product or branch, effective date, and a public URL supporting the correction. Keep private customer data out of the report.
For Google AI Overviews, the documented feedback flow uses thumbs down, then Report a problem and the appropriate category. Google says the submission includes the recent query and results. AI Overviews feedback instructions
For ChatGPT, OpenAI currently directs response feedback through the thumbs-down control. Its former model-behavior web form is deprecated. The separate Report route is for potential terms or legal violations, so do not describe every pricing error as a legal complaint. OpenAI’s current feedback directions
Keep the submission record without promising an acceptance, correction date, or universal model update. If the error could materially harm customers or operations, give the business owner the evidence promptly while the correction remains unresolved.
Try the possible retest outcomes. This changes only the illustrative explanation below; it does not update any page, profile or saved record.
Once the corrected source is publicly visible, repeat the original question on the same engine and surface. Record location context and the date being asked about. Run a separate, explicitly scoped question if the original was ambiguous; do not quietly substitute it into the original test series.
Classify each new answer:
An answer that stops mentioning the price has not demonstrated that it knows the new price. An answer with the right amount but the wrong billing commitment still needs correction.
Repeat checks over time and retain each result. Summarize outcomes by engine and question, including missing answers. If the error returns, reopen the record and inspect the newly cited sources. A recurrence alone does not establish why it returned.
Gist GEO’s documented workflow includes repeated query analysis, question- and engine-level reporting, and Opportunities with actionable tasks. Use those observations alongside the ledger to choose where to investigate. Have a person verify the exact price, hours, or service claim against its approved source; a visibility score cannot establish factual accuracy. Book a Gist GEO demo.
Use “sources corrected; answer checks ongoing” when the public records are fixed but you are still verifying responses. Use “error not observed in the latest checks” when that is what the saved answers show, with the dates and test scope attached.
A correction is most useful when another teammate can see the approved fact, confirm where it is published, and understand what still needs checking. The ledger gives them that handoff without promising control over the next answer an AI system produces.
Publisher disclosure: This guide is published by Gist and discusses Gist GEO, our own product. Sources and product descriptions checked October 19, 2026.
“Error not observed in the latest checks” is a bounded statement. Attach the dates and test scope so another teammate can see what remains uncertain.
Choose which optional analytics and advertising Gist can use. You can change your choices in Privacy settings. Privacy policy
