← Class Library
0 / 8 lessons

Fix Wrong Answers and Track Your Progress

15 min

What you'll be able to do

  • Trace a wrong AI claim about your business back to the source feeding it
  • Correct it at the source and confirm the answer actually changed
  • Set up simple tracking and a monthly rhythm that keeps this running

▶ Video coming soon

Walkthrough for this lesson

KEY TAKEAWAYS

  • There is no complaint form that fixes AI answers. You fix the source the engine is reading, then wait for a re-crawl
  • Different engines correct at different speeds. One may update in days while another stays wrong for weeks
  • Analytics tools mostly file AI traffic as Direct or Referral, so you need a custom channel to see it
  • Re-run your baseline monthly with the same questions. The trend is what tells you it's working
  • If two quarters of work move nothing, put the effort back into the channels that do work for you

When the AI says something false about you

You found these in your baseline: the wrong hours, the address you moved out of, a service you dropped, a price that's years old. Your first instinct is to look for a way to report it. There isn't one, not really. AI engines are reading something, somewhere, and repeating it. So the fix is detective work: find what they're reading, correct that, and make sure it gets re-read.

The correction workflow

  • Capture the wrong claim exactly: which engine, the precise wording, and the question that produced it.
  • Find the source. If the engine shows citations, start there. Otherwise, check the usual culprits: an outdated page on your own site, your Google Business Profile, a directory listing, a review site, or an old news article.
  • Correct it at the source. Update your own page, edit your Business Profile, or email the directory asking for a change.
  • Force a re-read. Request re-indexing in Google Search Console and Bing Webmaster Tools for any page you changed.
  • Leave feedback in the product too. The thumbs-down in ChatGPT and the feedback control on AI Overviews are worth thirty seconds, though they're a supplement to fixing the source, not a substitute.
  • Re-test. Ask the same question again in a fresh chat a week or two later, and keep asking until the answer flips.

Be patient across engines. A fix might show up in Perplexity within a couple of weeks while Copilot keeps repeating the old claim until Bing re-crawls the source. That's normal. Log the date you made each correction so you can tell the difference between “it didn't work” and “it hasn't propagated yet.”

Seeing AI traffic in your analytics

By default, most visitors arriving from AI tools get filed as Direct or Referral, so it looks like nothing is happening. In Google Analytics you can fix that: go to Admin, then Data Display, then Channel Groups, copy the default group, and add a new channel called “AI Search” placed above Referral. Set it to match the session source against this pattern:

  • chatgpt\.com|openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|meta\.ai
  • Expect the numbers to look small. Around 1% of sessions is a normal share right now, and those visitors typically convert much better than average, so judge this channel by leads and calls rather than by traffic volume.
  • If you use a CRM or a contact form, add a hidden field that records where the visitor came from. Knowing that three of last month's five best leads came from ChatGPT is worth more than any visibility score.

Your monthly rhythm: about 30 minutes

  • Re-run your baseline questions, word for word, in the same engines (15 min).
  • Update your share of voice and note any new wrong facts (5 min).
  • Fix one thing: a section rewritten answer-first, an FAQ question added, or a correction filed (10 min).

How to know if it's working, and when to stop

Give this two quarters before you judge it. If your share of voice is climbing and AI referrals are converting above your normal rate, keep going and consider investing more in content and third-party presence. If after two quarters the number hasn't moved and AI referrals are still negligible, that's real information too: put your effort back into the channels that are working for you. Being willing to walk away from something that isn't paying off is part of running this well, and it's the same discipline you'd apply to any other marketing channel.

You've built an engine

Look at what you have now: a measured baseline, a site AI crawlers can reach, pages written to be quoted, an FAQ built from real questions, a way to correct what's wrong, and a monthly habit to keep it all current. That's the whole system. The businesses that win here aren't the ones with the biggest budgets, they're the ones that keep showing up month after month with clear, honest, specific answers. That's a game a small business can win.

Put it into practice

Pick the single worst wrong fact from your baseline and run the AI Fact-Correction prompt on it today. Then put a recurring 30-minute block on your calendar for the same day each month.

PROMPTS FOR THIS LESSON

Copy these into your AI tool. They auto-fill with your business profile. Browse the full library.

Local MarketingAs needed

AI Fact-Correction Workflow

Paste a wrong AI answer about your business and get a ranked diagnosis of which source is feeding it, drafted corrections for each, and a re-test plan.

Local MarketingAs needed

AI Fact-Correction Workflow

You are a reputation triage assistant. An AI search engine is saying something incorrect about my business. AI engines repeat what they read from sources on the web, so I need to find the source and correct it there. Help me work backwards. MY BUSINESS: [BUSINESS DESCRIPTION] CITY: [CITY] WEBSITE: [WEBSITE URL] HERE IS THE WRONG ANSWER: - Which engine said it: [ChatGPT / Perplexity / Google AI Overview / Gemini / other] - The question I asked: [PASTE THE EXACT QUESTION] - What it said, word for word: [PASTE THE EXACT ANSWER] - Any sources it cited: [PASTE THE CITED LINKS, or write NONE SHOWN] HERE IS THE TRUTH: [EXPLAIN WHAT IS ACTUALLY CORRECT] SECTION 1: LIKELY SOURCE DIAGNOSIS Rank the most likely sources feeding this wrong claim, most likely first, with your reasoning drawn from the wording and any citations shown. Consider: - An outdated or forgotten page on my own website - My Google Business Profile - A directory or listing site (Yelp, industry directories, chamber listings) - A review site - An old news article, press release, or event listing - A social profile I no longer maintain - The model's own training data, if the claim appears in no live source For each, tell me exactly how to check it in one line. SECTION 2: CORRECTION DRAFTS For each likely source, give me what I need to fix it: - For my own website: the corrected sentence, written answer-first and self-contained so the correct version is the quotable one - For my Google Business Profile: exactly which field to edit and what to put in it - For a directory or third-party listing: a short, polite email requesting the correction, with the specific wrong detail and the correct detail stated plainly - If the source is likely training data with nothing live to fix: say so honestly, and explain that the fix is to publish the correct fact clearly on my own site and strong third-party listings so live retrieval overrides it SECTION 3: FORCE A RE-READ The steps to get the corrected source picked up: requesting re-indexing in Google Search Console and Bing Webmaster Tools, and leaving in-product feedback (the thumbs-down in ChatGPT, the feedback control on an AI Overview). Be clear that in-product feedback supplements fixing the source, it does not replace it. SECTION 4: RE-TEST PLAN - The exact question I should re-ask, word for word - Which engines to re-test and roughly how long each typically takes to update - A reminder to use a fresh chat with no previous context, and to run it more than once - A simple table for me to log the correction date, re-test date, and result Be honest about what I cannot control. There is no complaint form that edits an AI's answer directly, and different engines will correct at different speeds.
After you run this: Log the date you made each correction. Engines re-crawl on their own schedules, so one may update within days while another repeats the old claim for weeks. Re-test with the same question in a fresh chat until the answer flips.

What's next

That's the full workshop. Run your first monthly cycle four weeks from now and watch your share of voice move.