Making Your Own Comparison Page Credible

Readers know that a comparison written by one of the products is not neutral. They arrive sceptical. That is not a reason to avoid writing one. Many readers search for exactly the comparison you can provide, and you often know your own product better than anyone. The task is to earn trust despite the conflict of interest, and that is entirely possible.

This article lists what makes a vendor's comparison page credible: disclosure, method, evidence, balance, accuracy and openness to correction.

Accept the starting point

Do not pretend to be neutral. A page that presents itself as an independent review while hiding that its author makes one of the products is deceptive, and it will be found out. Say plainly that you are the maker, and let the page earn trust through what it does.

Google's guidance on helpful content asks about the person or organisation behind a page and encourages clarity about who created it and why. Honest disclosure is the first step in answering that.

Disclose at the top

Put the disclosure where readers will see it before they read anything else.

"We make Product A. This comparison was written by our team. We have tried to be accurate and fair, and we have described how we compared and when. If we have made a mistake, please tell us."

Do not bury it in a footer. Do not use vague phrases like "partners". Name the relationship. If any link in the page is paid or affiliate, say so.

Know the rules

Comparing with a named competitor is legal in many places but subject to conditions. Wikipedia describes the general expectation that comparisons should be truthful, supported by facts, based on measurable attributes and not unfairly damaging to a competitor's reputation or confusing. GOV.UK's guidance on advertising regulations describes UK rules that prohibit false or deceptive messages, omitting important information, using a competitor's logo or trademark and comparing your product with a competitor's non-equivalent product, with significant penalties for breach. Different rules apply to consumer and business marketing. This article is not legal advice. Take advice before publishing, particularly if the page will be promoted.

The practical summary: be truthful, be able to prove what you say, compare like with like, do not misuse the other party's marks and do not run it down.

State your method

A short method note turns a claim into a procedure.

• What you compared: which products, which plans and which versions.
• When: the date of the test and the date of the page.
• How: what you tested, with what data, on what platform.
• What you used: public documentation, trial accounts, your own measurements.
• What you did not test: be open about gaps.
• How attributes were chosen: ideally before you looked at the results.

Our articles on choosing attributes and on writing an honest versus page describe these steps in more detail.

Compare like with like

Match plans, versions and use cases. Compare your standard paid plan with their equivalent plan, not their free tier. Compare the current versions. State the equivalence you used. If perfect equivalence is not possible, say so and explain.

Support every claim

For each claim, show how a sceptic could check it.

• Link to the documentation of both products.
• Quote policies with dates.
• Include screenshots, dated, showing the feature or limit.
• Describe tests well enough to be repeated, and publish results.
• Cite sources for numbers, and date them.
• Avoid vague claims such as "much faster" or "far easier". Replace them with measurements or specifics.

If you cannot support something, soften it or delete it.

Be generous about the other product

This is the hardest and most effective part. A comparison in which your product wins every row looks like an advertisement, and readers will treat it as one.

• Acknowledge where the other product is better, with specifics, and say who benefits from those strengths.
• Describe its features accurately, including depth and limits, not just the label.
• Use neutral language. "Offers" and "lacks", not "boasts" and "fails".
• Give them equal space and equal detail.
• Avoid loaded visuals, such as a red cross on their logo.
• Do not misuse their marks or imply endorsement.

Generosity shows confidence. Readers who need what the other product does best will respect you for saying so, and some will remember you when their needs change.

Include a clear "who should choose which"

Close the comparison with an honest decision guide. "Choose A if... Choose B if..." based on the attributes. This is the part readers use. It turns the page from a pitch into a service.

Show costs fairly

Pricing is often the part readers care about most, and the most error-prone.

• Describe the pricing models, not only the headline price.
• Link to each vendor's pricing page for current figures, rather than copying amounts that will go out of date.
• Include limits and add-ons that affect cost.
• Give an example scenario, dated, with stated assumptions.
• Mention total cost of ownership, not only the licence fee.

A wrong or stale price damages credibility quickly.

Invite correction and reply

Make it easy for readers, and for the other vendor, to point out mistakes.

• A visible contact route and a short corrections policy.
• A promise to check and respond.
• A dated change log for material corrections.
• An offer of a short right of reply for the other vendor on points of substance.

If the other vendor tells you something is wrong, check, and correct promptly if they are right. Our article on right of reply describes the process.

Keep it current

A stale comparison is a liability. Assign an owner, put quarterly reviews in the calendar and watch both products' release notes. Update facts, the date and the version. If the other product is discontinued or merged, say so clearly.

Avoid the traps

1. Hidden relationship.
2. Rigged attributes that favour your strengths.
3. Unlike plans compared.
4. Features compared by label only.
5. Out-of-date claims.
6. Disparaging tone.
7. No way to challenge.
8. Keyword-stuffed, thin duplicates of the same page for many competitors.

A worked example

The maker of a small email tool publishes a page comparing it with a larger one. At the top, a banner reads: "We make Product A. We wrote this comparison. We tested both products in March using the standard paid plans. If you spot an error, tell us." A method box states the plans and versions, the ten attributes chosen before testing and the data used.

The table compares the ten attributes with notes and links. In three rows, Product B wins clearly: automation depth, number of integrations and reporting. The page says so, and says who benefits. In two rows, Product A wins: setup time, measured in a described test, and pricing model for small lists. In the other five, the products are similar.

A "choose which" section gives plain guidance. Pricing links go to each vendor's page, with a dated worked example. A change log notes that in April, the author corrected a statement about Product B's export after the vendor pointed it out. Readers leave comments thanking the team for honesty, and a few start trials. The page is reviewed in July and again in October.

A checklist before publishing

• Relationship disclosed at the top
• Rules and risks checked, advice taken if needed
• Method, dates and versions stated
• Like-for-like comparison
• Every claim supported
• The other product's strengths acknowledged
• A who-should-choose section
• Prices linked, not copied
• Correction route and change log
• Review scheduled

The categories and search pages here help readers find products to compare, the leaderboards page shows how ranking signals are labelled and kept separate and the blog has more on method.

Signals of credibility that readers notice

Readers rarely read every line. They scan for signs that the author is trustworthy. A visible disclosure, a dated method box, at least one honest concession to the other product, links to primary sources and a named person responsible for the page all register quickly. Equally, they notice what is missing: a vague author, a table where one column is entirely green, a price quoted without a date, an absence of any limitation for the author's own product. Build the page so that the first signals are the good ones, and the rest of the page can then do its work.

After publication

Once the page is live, treat it as a service. Watch for reader comments, check your analytics for how people use it and read what other sites say. Reply to questions with facts. If a reader finds an error, thank them and fix it. Over time, a page that is open, careful and updated becomes a reference that people link to, and links earned that way are worth far more than any placement you could buy.

Frequently asked questions

Will honesty about the other product cost me customers? It may send a few elsewhere. It will win the trust of many more.

Should I name competitors in headings? Yes, where readers search for the comparison, and where you use the names factually.

Can I use affiliate links in a comparison? Disclose them clearly, mark them appropriately and do not let them influence the analysis.