Right of Reply When a Comparison Fact Is Disputed
Method · 8 min read ·
What to do when a vendor says your comparison got a fact wrong: check, correct, note the change, offer a reply and protect fairness to readers.
You publish a comparison. A week later, an email arrives from one of the vendors you described. They say that a row is wrong, a price is outdated or a claim is unfair. Your first reaction may be defensive. Your second should be professional. How you handle the dispute shows readers, vendors and search tools what kind of publisher you are.
This article sets out a calm approach to disputed facts in comparisons: how to check, when to correct, how to give the other side a fair hearing and how to protect your independence.
Why fairness to the subject matters
A comparison affects the products it describes. A wrong claim can lose a vendor customers, and it can mislead readers into a worse choice. That is a harm, even when unintended. Wikipedia notes that comparative advertising, in which a product is compared with a named competitor, is expected to be truthful, supported by facts, based on measurable attributes and not unfairly damaging to the competitor's reputation. Independent comparisons are not advertising, but the same ethical standards are a good guide.
Fairness is also in your own interest. A reputation for accuracy and openness to correction is the most valuable asset a comparison site has. Google's guidance on helpful content places trust at the centre of quality and asks whether a page is clear about who created it, with sound sourcing and accuracy. A publisher that handles disputes well meets that standard.
Build in a right of reply from the start
The best time to handle disputes is before they arise.
- Tell vendors you are comparing them, where it is practical, and invite them to check the facts about their own product.
- Give a deadline that is reasonable and a clear route for responses.
- Be clear about what they may do. They can correct facts. They cannot dictate conclusions.
- Publish a corrections policy on your site: how to report an error and what you will do.
- Show a contact route on every comparison page.
Inviting a vendor to check facts is not the same as letting them approve the page. You keep editorial control.
When a dispute arrives
1. Acknowledge promptly
Reply within a day or two. Thank them for getting in touch, say you will look into it and give a time when you will respond. Keep the tone courteous even if the message is not.
2. Understand exactly what is disputed
Ask for specifics if necessary. Which row, which claim, which version? What do they say is correct? What evidence can they provide? Separate the different kinds of complaint.
- A factual error. A wrong date, price or feature status.
- An outdated fact. True when written, no longer true.
- A matter of definition. You and the vendor mean different things by a term.
- A matter of emphasis. The vendor thinks you gave too much weight to a weakness.
- A matter of opinion. They disagree with your assessment.
The first two are corrections. The third needs clarification. The last two are editorial judgements that you may keep, while considering the point.
3. Check the evidence
Go back to your sources. Look at the documentation, retest if necessary and check the date. If the vendor points to a page, read it. If they claim a change, verify it. Do not rely only on their word, and do not dismiss it either.
Wikipedia distinguishes corrections, which address factual inaccuracies, from clarifications, which resolve potentially misleading statements that are technically accurate but need more context. Decide which applies.
4. Decide
If the fact is wrong, correct it. If it is right but misleading, clarify it. If it is right and fair, keep it and explain. If you are not sure, say what you could not verify and mark the row as unconfirmed until you can.
5. Respond to the vendor
Tell them what you decided and why, briefly and politely. If you made a correction, say what you changed and when. If you did not, give the evidence. If there is a legitimate disagreement, offer to include a short statement from them.
Make the correction visible
Where you have changed a material fact, tell readers.
- Fix the table or text.
- Add a dated note, for example: "Correction, 12 March: an earlier version said Product B had no export. It supports export in two formats. We apologise for the error."
- Update the date at the top of the page.
- Keep a change log on long-lived pages.
- Check other pages where the same error might appear.
- Update any social posts or summaries that repeated it.
A quiet fix of a material error looks like concealment. A visible, dated note looks like integrity.
Offer a reply where it adds value
For disagreements of substance, a short statement from the vendor can help readers. You might include a boxed "Vendor response" beneath a section, clearly labelled and attributed, with a date. Set a length limit, say two or three sentences, and keep the right to edit for clarity and to remove anything abusive or unverifiable. Do not allow replies to become advertising.
If the vendor's reply raises a point that is persuasive, update your assessment and say why.
Protect your independence
Fair treatment is not the same as giving in.
- Do not remove accurate, relevant criticism because a vendor dislikes it.
- Do not accept payment for changes to your assessment. Paid placements, where they exist, are labelled and separate. On this site, votes cannot be bought.
- Do not let a vendor edit your page directly.
- Keep a record of the exchange, including what you changed and why.
- Be wary of legal threats. Take advice if you receive one, and do not respond in haste.
- Disclose relationships. If you have any financial connection to a vendor involved, say so.
Handle bad faith
Occasionally, a vendor will try to bully, flood you with demands or insist on changes that would make the page misleading. Stay calm and professional. Restate your corrections policy. Fix what is wrong, and decline what is not. If the contact becomes abusive, you may end it and keep a record. Readers will judge you by the page and by your conduct.
What if you are the one disputing a comparison?
If you are a vendor who believes a comparison is wrong, you will get a better result by being helpful.
- Be specific. Point to the exact claim.
- Provide evidence. Link to documentation, release notes or policy pages.
- Be polite. The author is often a person with limited time.
- Do not demand deletion. Ask for a correction.
- Offer to provide information for future updates.
- Say what is true as well as what is false. Acknowledge accurate points.
A worked example
A site publishes a comparison of two email tools. A week later, the maker of Tool B writes to say that the page states that B has no automation features. The author acknowledges the message the same day and asks for the specific evidence.
The vendor links to documentation for an automation feature launched two months earlier. The author checks it, tests it on a free account and finds that it exists but supports only simple sequences. She decides this is both a correction and a clarification. She updates the row to "partial: simple sequences, added January", adds a dated note "Correction, 12 March: an earlier version said B had no automation. B added simple automation in January", and updates the page date.
She emails the vendor with the changes and invites a two-sentence statement for a "Vendor response" box. The vendor supplies one, which she edits slightly for length. A reader comments that the correction note increased their trust in the page. A month later, the same vendor sends another correction, politely, and the exchange takes ten minutes.
A checklist
- Corrections policy and contact route published
- Prompt, courteous acknowledgement
- Specifics requested; type of complaint identified
- Evidence checked independently
- Decision: correct, clarify or keep, with reasons
- Vendor informed
- Visible, dated correction
- Vendor response offered where useful
- Independence protected; relationships disclosed
- Record kept
The contact page here shows how this site invites reports from readers, and the categories and search pages help you find products to compare.
A short template for the first reply
When a dispute arrives, a calm first message helps. You might write: "Thank you for getting in touch. I want to make sure our page is accurate. Could you tell me which row or statement you believe is wrong, which version of your product it concerns and where I can see the current facts? I will check them and reply by the end of next week. If we have made an error, we will correct the page and add a dated note." It is polite, specific and sets a timetable. Keep your response times, and keep a copy of the exchange in your corrections log.
Learning from disputes
Each dispute is evidence about your process. If errors come from outdated sources, shorten your review cycle. If they come from labels that vendors use differently, add a glossary. If they come from assumptions about plans, state the plan next to each claim. After a few months, patterns appear, and fixing the cause reduces the number of disputes and makes the page better for everyone who reads it.
Frequently asked questions
Should I tell vendors before I publish? Where practical, yes. It reduces errors and builds goodwill.
What if I cannot verify a vendor's correction? Mark the claim as unconfirmed and say what you were unable to check.
Do I have to publish the vendor's response? No, but offering a short one can make a comparison fairer.
Questions and answers
- What is a right of reply?
- An opportunity for the subject of a published statement to respond to it, ideally before publication and at least afterwards.
- Do I have to change my page if a vendor complains?
- Only if the claim is wrong or misleading. Check the evidence, and correct the page where the vendor is right.
- Can vendors review comparisons before publication?
- They can be invited to check facts about their own product, but you decide the content and the conclusions.
- How should I record corrections?
- With a dated note on the page, and a short change log if the page is long-lived.