FAQ

AI is saying wrong things about our company. What do we do?

Do not start with complaints to the AI companies — the wrong fact almost always comes from a wrong or conflicting source the engine is reading. The fix order: find which page the wrong version lives on (often your own outdated page, a platform listing or Wikipedia); make one canonical, machine-readable version of the truth easy to find (llms.txt plus JSON-LD on the official site); correct the third-party sources in citation order; then verify by re-sampling the same questions over the following weeks. Vendor feedback channels exist but are slow — treat them as escalation, not the fix.

Figure 01 · The misinformation chain: from polluting source to wrong answer — and the four-step fix

  • The chain · 1

    Polluting source

    A third-party directory, an old press release, an encyclopedia entry, or your own outdated page supplies the wrong fact.

  • The chain · 2

    Engine cites it

    The AI cites that source when answering, and the wrong fact enters the answer.

  • The chain · 3

    Wrong answer

    Customers read the wrong price, address, registration status or case attribution.

  1. 01

    Step 1: Document and classify

    Archive the screenshot, prompt, full response, engine and date; classify into one of four kinds.

  2. 02

    Step 2: Trace the source

    Follow the citations to the polluting page; check your own site's outdated wording first.

  3. 03

    Step 3: Fix sources, publish one canonical version

    Correct every source page; publish one machine-verifiable fact version via llms.txt + JSON-LD.

  4. 04

    Step 4: Re-test to confirm

    Re-sample the same fixed question set after 2–4 weeks; track the error rate separately.

Fix sources, not answers: with the source unclean, the next sampling round gets it wrong again. Errors travel from a polluting source through engine citation into the answer; the fix runs the four-step loop, with vendor feedback channels only as a backstop. Measured data: Negency Flagship Report 2026 (Issue 1) — 17 of 30 sites had no JSON-LD at all.

First, classify: four kinds of error, four different fixes

AI states facts from its source mix: your website, third-party platforms, Wikipedia, the press, review sites. Before doing anything, classify the error: factual errors (founding year, address, pricing), positioning errors (wrong service boundaries), misattribution (a competitor's case credited to you), or stale information (old products, old wording). The class decides the fix — factual errors mean fixing the source page, stale information means retiring the old version first, misattribution means supplying one canonical version. This page merges the response into a single four-step framework: document and classify → trace the source → fix sources and publish one canonical version → re-test to confirm.

Step 1: Document and classify

Archive the wrong answer: a screenshot, the exact prompt, the full response, the engine and the date, kept together as one record. The archive serves two purposes: it gives the re-test a like-for-like comparison, and it is the evidence you attach when filing a correction with a third-party platform or media outlet. Once archived, classify the error into one of the four kinds above and rank it by damage (see "What to fix first" below).

Step 2: Trace the source

Follow the answer's citations and the engine's knowledge sources to the polluting page — usually a third-party directory, an old press release, an encyclopedia entry, or your own outdated page feeding it wrong facts. Test the wrong claim against your site first: many errors actually originate in your own website's outdated pages, and fixing your own pages is fastest. If your site is right, work through the third-party pages in order of how much engines cite them.

For example: AI states your old office address, and tracing finds a directory profile that has not been updated for years — while your own site footer still links a PDF company profile carrying the old address. Both sources need fixing; fix one, and the next sampling round gets it wrong again.

Step 3: Fix sources, and publish one canonical version

Correct every source page: fix the third-party pages where you have edit rights (platform profiles, partner pages) one by one; for independent media, request corrections from the outlet; retire or update your own old pages the same day. At the same time, publish one authoritative fact source on your own site: key facts (services, dates, locations, credentials) stated consistently and made machine-readable (llms.txt + JSON-LD), so engines have an authoritative source to land on. For how to write an llms.txt, see What is llms.txt? Does a corporate website need one?

Asking the engine to "fix the answer" barely works — with the source unclean, the next sampling round gets it wrong again. Vendor feedback channels are an escalation route, not the main fix: submit through each vendor's official feedback channel (for example, thumbs down under a ChatGPT response with a description of the error, or the report control under a Perplexity answer) — and accept that feedback carries no promise to change any specific answer. What actually changes answers is the re-crawl after the sources are fixed.

Step 4: Re-test to confirm

Re-sample the same fixed question set that produced the error after 2–4 weeks and track the error rate separately. Fact correction follows the engines' re-crawl cycles — weeks, not days — and only sampling shows whether it is fixed. Factual accuracy is a standing metric we track for every GEO client. For the resampling method, see How do you measure a brand's visibility in AI answers?

What to fix first, by damage

Pricing and service-boundary errors (they lose deals directly) > contact and legal-entity errors (customers cannot find you) > positioning and case errors (they cost trust) > wording blemishes (schedule them). If the error lives on a platform with an edit path (encyclopedias, directories, maps), file the correction the same day; if it is your own old page, retire or update it the same day; if it lives in sourceless model memory, only sustained correct wording plus third-party corroboration overwrites it — which is why fact governance belongs before the incident, not after.

The standing work: govern facts before anything goes wrong

In our measurement of 30 global-facing websites of Chinese exporting companies (Negency Flagship Report 2026, Issue 1, sampled on a single day, 30 October 2026), 17 had no JSON-LD at all and 13 had a missing or non-unique H1 — most companies do not even have one machine-readable canonical version on their own site, so when AI gets something wrong there is nothing authoritative to fall back on. The standing work of fact governance is: keep one machine-readable fact file on the site (llms.txt + JSON-LD), keep key facts identical everywhere, and resample a fixed question set regularly to track factual accuracy. Fixing it after the incident costs far more effort than maintaining it.

See where your brand stands in AI search

Start with the free AI visibility audit: your scores for crawler reachability, machine readability and entity structure in minutes. For the full competitor comparison and fix list, see the AI search visibility diagnostic package.

Related questions

How is GEO different from SEO?

SEO optimises a page's rank in a list of links, aiming for clicks. GEO (Generative Engine Optimization) optimises how discoverable, understandable, trustworthy and citable a company is inside AI-generated answers — the goal is to be in the answer itself. They share technical foundations (crawlability, structured data, content quality), but GEO additionally requires governed entity facts, a machine-readable surface (llms.txt, Markdown mirrors) and a third-party mention ecosystem. A site that ranks well is not automatically visible to AI: engines cite the companies whose facts they can fetch, parse and verify. The concrete differences sit in four dimensions — goal, object, content structure and evaluation — compared item by item in the body below.

How can Chinese companies going global build AI search visibility?

For Chinese companies going global, the visibility gap is rarely content volume — it is the machine-readable surface. Our audit of 30 Chinese outbound companies found machine-readability the weakest category (69.2/100 average): 17 had no JSON-LD on the homepage, 15 had a missing or thin sitemap, 13 had a missing or duplicated H1. The path has four steps: audit bot reachability and machine-readability first; govern entity facts so Chinese and English statements agree; publish question-shaped content built on real overseas buyer questions; then earn third-party mentions (media, communities, partners) and verify with periodic resampling against a fixed question set.

What should a corporate website change for the AI search era?

Five changes. (1) Bot reachability: robots.txt explicitly allows AI crawlers and live fetches are not stopped by firewalls or challenge pages. (2) A machine-readable surface: an llms.txt fact file (optional aid), a complete sitemap, Markdown versions of core pages (optional). (3) Entity structure: JSON-LD naming entity types such as Organization, clean title/H1 discipline, hreflang pairing on bilingual sites. (4) Question-shaped content: pages organised around buyer questions, short answers first, FAQ schema attached. (5) Measurability: analytics that separate human and bot traffic and attribute AI-referred inquiries. Negency's own site was rebuilt to exactly this standard, and the public audit tool scores against it.

What is llms.txt, and should every company website have one?

llms.txt is a plain-text brief at the site root written for AI systems: who the company is, what it does, where the core pages live, and the canonical facts and definitions. It does not by itself raise citation rates — in Ahrefs' May 2026 study of 137,210 domains, 97% of published llms.txt files received zero requests that month, so its direct effect is near zero — but it is the cheapest fact-governance move available: one file anchors a single version of the truth that crawlers can rely on. Verdict: worth adding, useless alone; it works as part of entity-fact governance, structured data and question-shaped content. Negency's llms.txt is a full fact bible: company definition, offering boundaries, sourced cases and citation rules.

What should an enterprise prepare before deploying AI agents?

Four preparations, and we advise against starting without any of them. (1) Scenario selection: pilot on a workflow that is frequent, comparatively rule-clear and verifiable — not the most glamorous one. (2) Knowledge and data foundations: govern the knowledge base first (deduplication, versioning, permissions); a dirty knowledge base only scales errors. (3) Governance design: permission boundaries, human approval points and audit logs decided before launch, not after. (4) A measurement baseline: record the manual process's time and error rates before the pilot, or value can never be proven afterwards. Negency's method is a small controlled pilot, verified before scaling, with governance as a design input rather than a patch.