What to do when a competitor makes a false claim about your product

What should you do when a competitor’s comparison page gets your product wrong?

Save the sentence and the page as they appeared when you found them. Check the statement against current documentation for the same product, plan, region, and date. Then give your sales team a short, sourced response and ask the publisher to correct the specific error.

You may have found the page in search, heard about it from a buyer, or seen it cited in an AI answer. Record which happened. A page can be inaccurate without ever reaching a buyer, and a lost deal needs evidence beyond the page’s existence.

Is the claim false, outdated, or a matter of opinion?

Take a statement such as “Product A does not support SSO.” The answer depends on which plans and identity providers the page compares. Current documentation showing SSO on an enterprise plan would contradict a blanket claim, but not a claim limited to the free plan.

Save the exact words, the surrounding paragraph, the page URL, and the date you checked it. Find the product document or approved fact that settles the same scope. If your own documentation is unclear, ask the product owner before calling the competitor wrong.

“Harder to use” is a judgment. “Does not offer SSO” is a checkable product claim. Respond to the judgment with evidence about the buyer’s use case; reserve a factual correction request for a supported contradiction.

What should your sales team say while the page is still live?

Give reps the shortest answer that resolves the buying concern. For the SSO example: “SSO is available on our Enterprise plan; here are the supported providers and setup requirements.” Link to the current documentation. Include the limitation if it matters.

Ask reps to record when a buyer raises the disputed point. That tells you whether the claim is entering evaluations. Do not tell buyers that the competitor is lying unless you have evidence of intent; the documented problem is the inaccurate statement.

How do you ask for a correction?

Contact the publisher with the URL, the exact sentence, the current evidence, and replacement wording that keeps the plan or date condition. Preserve the request and any reply. If the page changes, save the revised wording as well.

If an independent review site repeats the same error, contact that editor separately. A correction on one page does not update every other page carrying the claim. For a sustained dispute, involve the people at your company who own product facts and external communications.

The competitor claim monitoring guide covers ongoing page checks. The comparison-page guide covers an accurate response on a page your company controls.

What if an AI answer repeats it?

Save the full buyer question, answer, date, and any citation attached to the disputed sentence. Open the cited page and check whether its text supports the answer. Similar wording alone does not prove that the AI used the competitor page. A source list that merely includes the domain does not prove it either.

The AI citation guide shows how to inspect that connection and measure later answers. Keep the page correction, the AI answer, and any buyer objection as separate observations.

KnitKnot can keep a captured answer, its material claim, reliable source evidence, and your approved company fact together. Start with one claim that a buyer has raised or an AI answer has repeated, then check whether the evidence supports a response.