Guide

How to fix negative brand sentiment in AI answers

last reviewed 2026-10-26 12 min read · 2,514 words no sentiment score anywhere in this guide
What one answer can tell you about how you are described one question · one assistant · one run
  • a label

    The answer named you and described you. Positive, negative, neutral or mixed — and only ever about text something actually read.

  • not named

    The answer never mentions you, so no description exists to read a slant off. A real finding, and not the same thing as neutral.

  • not measured

    No answer text to read — the run failed, the engine was not asked, or the text is past its retention window. Unrun, never a zero.

  • classification failed

    The text was there and the thing reading it was not. Its own outcome, carrying the reason, and never quietly counted as neutral.

An assistant does not rate your business. It describes it — in a clause or two, inside an answer to somebody else’s question — and that description is assembled from whatever it has read and whatever it remembers. You cannot edit that. What you can change is the evidence it is working from.

This guide covers how to find out what is being said about you, where a negative characterisation comes from, the four things that genuinely move one, and the three remedies sold for this problem that cannot.

What does “sentiment” mean when an assistant describes your business?

Sentiment here is the slant of the description itself: whether the sentences an assistant writes about you read as favourable, unfavourable, flat, or both at once.

It is a property of one answer, not of your company. Ask for the best options in your category and your name may arrive with a clause attached — though some users report slow support. Ask again with the words reordered and the clause may not appear. The description is written fresh each time, out of training and out of whatever was fetched while answering.

So one answer’s slant is one of four things: positive, negative, neutral, or mixed — praise and criticism in the same breath. A fifth outcome is not a slant at all: the answer may not name you. No description means no sentiment, and counting that as neutral is the first mistake available.

Is this the same as a review score or a star rating?

No, and the difference is what makes it hard to act on.

A star rating is a number computed from inputs you can inspect: reviews, each with an author, a date, and a platform with a written process for disputing one.

An assistant’s description has none of that furniture — no total, no author, no record of which pages contributed, only prose that varies from run to run. So there is nothing to dispute, and no single figure that can be made to go up. A dashboard handing you one has manufactured it.

The honest unit is a count: how many recorded answers described you one way, how many the other, out of how many were actually read.

The hard part: you cannot edit the model

There is no support desk for what an assistant says about your business, and accepting that is cheaper than discovering it later.

Model weights are not editable from outside. You cannot file a correction, you get no case number, and there is no verified-owner route for amending a characterisation the way a directory listing or review platform gives you one.

You cannot change the model. You can change what it reads.

That is the entire available surface, and it is narrower than most advice on this subject admits. An assistant that fetches while answering reads whatever the open web says about you at that moment; a model retrained later reads it again. Every remedy below acts on a page, a thread, a listing or a record. None acts on the model.

How do you find out what is actually being said about you?

Ask the assistants the questions your customers ask, and write down what comes back word for word.

Not what do you think of my company — nobody types that. The questions that matter are buying questions: best tool for this job, is this one any good, alternatives to it, is it worth the money. Ten is enough to start.

Record four things per answer: the exact question, which assistant, the date, and the complete text of the reply — not a summary of it. The phrase matters more than the verdict, because the phrase is what you will later go looking for a source for: reported slow onboarding sends you somewhere specific, negative sends you nowhere.

The manual version of this routine is written out in track brand mentions in AI.

One answer is one observation, not a sentiment

Assistants do not answer the same question the same way twice, so a single reply tells you what happened once.

Sampling, retrieval and the word order of the question all move the output. The same prompt an hour later can name different companies and attach a different clause to yours. A screenshot of something unflattering is not yet a finding.

A pattern is a finding. The same criticism in four of six recorded answers is worth tracing; one in twelve is noise, and chasing it costs more than it returns. Below two measured runs on one question there is nothing that deserves a name — the rule the product further down enforces on itself.

Where does a negative characterisation come from?

Five origins account for most of what people find, and reading the answer carefully usually says which one it is.

  1. An old review page. Complaints from a period since fixed, still near the top of the results for your name. Nothing has to be recent to be repeated.
  2. A forum thread. One long discussion, strongly worded, often years old, and frequently the most detailed thing written about your product anywhere — and detail is what retrieval rewards.
  3. A news item or a public record. A dispute, a filing, an outage. Accurate, permanent, and not something to argue with.
  4. A competitor’s comparison page. Phrased as a fair summary, and often the only page describing you in the exact terms a buyer asked about.
  5. A plain factual error, repeated. A price that changed, a product discontinued, a market you left. The model is not being unfair; it is quoting stale text.

The last is the most common, the least dramatic, and the one fixable this week.

Correcting the source, when there is a source to correct

When a description traces to a specific page, that page is the job, and the highest-leverage work on this list.

Order matters. A page you own is an edit. A page you do not own falls into three cases: a platform with a documented correction route, such as a business profile or directory listing; a publisher who will consider a factual, specific correction; and everybody else, who will not. Work down that order and stop at the third.

What this is not is a takedown campaign. A legitimate criticism is not an error, and an accurate page that happens to be unflattering is not a correction target. Pushing on one is how a small complaint becomes a larger story — which the assistants then read.

Answering the objection on a page of your own

If a criticism keeps recurring, publish the page that answers it directly, in the words the criticism uses.

The mechanism is dull and it is the only one on offer. An assistant that fetches while answering retrieves pages matching the question in front of it, and a page that states an objection and answers it matches that question better than one which never mentions it.

So name the thing: the setup time, the pricing confusion, the limitation that is genuinely real — what is true, what changed, and when. Say the unflattering part out loud. A page that concedes a limitation and explains the trade-off is usable evidence; one that only praises you reads as marketing and weighs nothing against the thread that prompted the question.

Getting other sources to agree with you

One page saying the right thing is weaker than three independent pages saying it, and that asymmetry is the whole of this step.

A description assembled from many documents moves when many documents move. The practical list is short: the factual pages on your own site, your profile on whichever platforms your category uses, any directory that accepts submissions, and whatever independent coverage can honestly be earned.

The flip side is unglamorous. Where one fact is written four ways in four places — a changed tier, a dropped feature, a new location — the inconsistency becomes the description.

Fixing the plain factual errors on pages you control

A large share of unflattering descriptions is not criticism at all. It is stale fact, faithfully repeated.

A discontinued product still listed. A support policy that changed two years ago. A minimum contract you no longer require. An assistant reading your site has no reliable way to know which page is current, and a model that absorbed the old version keeps reproducing it until something newer displaces it.

The audit is mechanical: list the facts a buyer asks about — what it costs to begin, what is included, how long it takes, who it is not for — check each against every page of yours that states it, and delete the contradictions. The cheapest item in the guide, because every page involved belongs to you.

What does not work, and gets sold anyway

Three remedies are sold for this problem and none of them can work.

Asking the model to forget

Changes one conversation, nothing else

Telling an assistant to disregard something edits the session you are sitting in. It reaches neither the model nor anybody else’s session, and a chat transcript is not a correction channel.

Reputation repair sold with a guarantee

A promise about something the seller does not operate

Nobody outside a model’s operator controls what it generates, and the operator does not control any individual answer either. A promise about next month’s answers is made on behalf of a system the seller cannot reach.

Mass-publishing rebuttal pages

Fails twice, in two directions

Twenty thin pages restating one denial is the oldest answer here. Near-duplicates are the shape search systems discount, and a wall of identical rebuttals reads as evidence the complaint is widespread.

What the three share

They act on the model, or on the look of evidence

Each tries to edit the thing you cannot reach, or to manufacture the look of sources rather than change what they say.

What brand sentiment tracking in an LLM can honestly report

A tool can tell you how the answers it collected described you, and over how many runs. Anything beyond that is invented.

Here is how that works in this product, so the limits are visible rather than implied. When a scan runs, every stored answer naming the brand is read by a classifier, and the label it returns — positive, neutral, negative or mixed — is written onto that answer then and there, stamped with the classifier’s name and version. Later views read the stored label, and a cell labelled by two different classifiers says so.

Three outcomes are not labels, and keeping them apart is the point. An answer that never names the brand is absence: no description exists, so no sentiment exists, and it is not neutral. An answer with no text to read — a failed run, an engine not asked, text past its retention window — is not measured. A run where the text was there and the classifier was not is a failure, carrying its reason, and the loudest thing in its cell. None of the three is folded into neutral, and none is a zero.

There is no score in it. The output is a set of counts — this many runs positive, this many negative — printed beside the number of runs actually measured. No mean, no net figure.

And it refuses to publish a distribution from fewer than two measured runs. Each plan asks a question once per scan, so one scan cannot reach that floor alone; the screen pools the labels its recent scans already stored, matched on the exact question and engine, and every cell states how many scans it drew from. Nothing is padded. Sentiment reporting is on the paid plans.

A routine you can keep

Quarterly beats monthly here, because what is measured moves at the speed of published pages rather than of days.

  1. Re-ask the same questions, word for word. A reworded question is a different question, and its answers do not belong in the old column.
  2. Count, do not judge. How many answers carried the criticism, out of how many came back. Write both numbers; the second is the one people drop.
  3. Trace anything new to a source. If none is found, log the exact phrase and wait for the next round.
  4. Check whether last quarter’s fix is visible. Two rounds with no movement in the wording means the evidence you changed was not the evidence being used.

A pair of counts per quarter is a record. Three records is a trend, and a trend is the only thing that tells you whether any of this worked.

FAQs

Can I ask ChatGPT to stop saying something negative about my business?

Not in a way that lasts. Anything you type into a chat changes that one conversation — it does not reach the model and it does not reach anybody else’s session. The only durable lever is the evidence an assistant reads while answering: the pages, listings, threads and records that describe you.

How long does it take for a correction to show up in AI answers?

It depends which route the assistant took. One that fetches pages while answering can reflect a corrected page once it has been crawled again, usually weeks rather than days. A description coming out of model memory changes only with a later training run, which nobody outside the vendor can schedule.

Is negative AI sentiment the same thing as a bad review?

No. A review has an author, a date and a platform with a dispute process. An assistant’s description has none of those: prose generated at the moment of asking, varying between runs, with no record of which sources contributed. There is nothing to dispute, which is why the work goes on the sources instead.

How many runs do I need before a sentiment reading means anything?

More than one, and two measured runs on the same question is the honest floor. One answer is one observation, because assistants vary from run to run. A tool reporting a sentiment figure off a single check is reporting a number it cannot support.

What should I do first if an assistant is describing my business badly?

Record it properly before changing anything. Capture the exact question, which assistant, the date and the full wording, then repeat it enough times to see whether the criticism is consistent. Then read the phrasing for a source: a specific phrase is traceable, a general impression is not.

Can a tool track brand sentiment across AI search engines?

It can report what the answers it collected said, on the questions it asked, on the engines it asked them on — a real measurement with a real denominator. What no tool can do is sample everything an assistant tells everybody, because nobody outside the vendor sees that. Treat any figure offered as your sentiment across AI search as the sample it is.

Where the measurement section is checkable

The sentiment screen described above is at app.answermend.com/sentiment, behind a sign-in, and the docs explain how to read a cell. The four labels, the three outcomes that are not labels, the two-run floor and the pooling across recent scans are all on it.

Read the description before you argue with it.

Up to five questions written from your own homepage, asked on ChatGPT and Gemini, with the full wording of each answer kept — one pass per question, labelled as one run rather than an average.

Check my site no card · sentiment labels are a paid-plan feature