A fair comparison page names the competitor, compares specific attributes a buyer can check, attaches a public source and a date to every claim about the other product, and says plainly where the competitor is the better choice. Buyers know a vendor wrote it; fairness is what keeps them reading anyway. Have counsel read it before launch and again whenever either product changes.
Buyers who reach a shortlist search for one product against another by name, and they put the same question to assistants. If the vendor publishes nothing, the comparison still exists. It just gets written by a review site, an affiliate, or the competitor, and none of them will describe your product the way your team would.
This is content planning for SaaS marketing teams, not legal advice. Comparative claims carry legal exposure, and your counsel decides what your pages may say.
What federal law says about naming a competitor
The Federal Trade Commission's 1979 policy statement, still posted in its legal library, defines comparative advertising as advertising that "compares alternative brands on objectively measurable attributes or price" and identifies the rival brand. It asks for "clarity, and, if necessary, disclosure to avoid deception of the consumer," and it accepts disparaging advertising as long as it is "truthful and not deceptive." The FTC's small business guidance adds a point that applies directly to comparison tables: advertisers cannot "use fine print to contradict other statements in an ad." A checkmark in a grid with a footnote that takes it back is that problem in table form.
The competitor has its own remedy, too. The federal Lanham Act, at 15 U.S.C. 1125(a), covers commercial advertising that "misrepresents the nature, characteristics, qualities, or geographic origin" of a party's own or "another person's goods, services, or commercial activities," and makes the advertiser liable in a civil action brought by any person who believes they are or are likely to be damaged by it. A rival whose product you describe is the most motivated reader your comparison page will ever have.
Put a source line under every claim
Each statement about the other product needs evidence a reader could find, dated so a reviewer knows when it was true. Statements about your own product need the same discipline. The table below is a working standard to bring to counsel, not a legal test.
| Claim type | Evidence to keep | When to recheck |
|---|---|---|
| Competitor's list price | A dated capture of their public pricing page | Before each review cycle and when they announce plan changes |
| Competitor lacks a feature | Their own current documentation, captured with a date | Every release cycle you track for them |
| Your feature or limit | Your documentation or release notes | When your product ships a change |
| Speed or performance | A documented test with its method and conditions, or leave it out | When either product changes infrastructure |
| "Customers prefer us" | A survey with its method, or leave it out | When the underlying data ages |
Be careful with gaps in a competitor's documentation. Teams often read a missing help article as a missing capability, and the competitor's customers may know otherwise. Silence in their docs is not proof the feature is absent. Where the record is unclear, say "not documented publicly as of" a date, or drop the row.
Say where the other product wins
A comparison that awards every row to the author reads as an ad, and buyers discount it accordingly. A section headed "When the other product may fit better" gives the rest of the page credibility, and it also filters out buyers who would churn. The honest version of that section comes from your own lost deals. Ask the sales team, "Of the deals we lost to this competitor last year, which ones were the right outcome for the buyer?" The answers usually point to a team size, an integration, or a workflow where the other product is simply the better fit.
Keep the tone factual on both sides. Describe what each product does, for whom, and under what conditions, and let the reader draw the conclusion. Pages about switching belong on their own URL; see how to explain migrating from a competitor. For how third-party ratings fit alongside your comparisons, see how to handle review site profiles.
Thirty "alternative to" pages are a different problem
Here is a fictional example. An invoicing platform for small agencies, based in Oregon, published 30 pages titled "Best alternative to" each competitor, identical except for the competitor's name and a swapped screenshot. Among the doorway abuse examples in Google's spam policies is this one: "Creating substantially similar pages that are closer to search results than a clearly defined, browseable hierarchy." The fictional company keeps six comparisons against the products its buyers actually shortlist, writes each from that competitor's real differences, and folds the rest into one plain directory page.
The six surviving pages are built from material the company already holds. Its win and loss notes record why buyers chose each rival, and its support team knows which workflows trip up customers who switched in. Nobody drafting these pages should have to reconstruct those differences from memory when the sales notes already document them. What the writer adds is structure: one page, one rival, one dated source per claim, and a review owner named in the content plan.
Comparison pages also age faster than almost anything else on a software site, because two release schedules feed them instead of one. Put a "last reviewed" date near the top, keep the dated captures behind each row in a shared folder, and name one owner who checks the page whenever the competitor announces a release or a plan change. When a row can no longer be confirmed, remove it instead of leaving it to drift. A short, current comparison is worth more to a buyer than a long one that was accurate last spring.
How the four steps apply to comparison pages
At Hudson South, Authority Asset comes first: your documentation, win and loss notes, and the evidence behind each claim about your own product. Hudson Twenty-One maps how your team communicates across 21 dimensions, including the tone it takes when a buyer asks about a rival directly. Market Intelligence researches which head-to-head questions buyers in your category ask and what the competitors publish about themselves. AEO Creation turns those inputs into answer-first comparison pages. Hudson South works with one business per line of work in each market. For evidence a buyer can actually inspect, read our article on website proof, and for the rest of the product site, the software and SaaS overview.
Check your comparisons against what rivals publish
Name the competitor that shows up in the most deals. In a free 30-minute call, we walk through how your pages and theirs answer the head-to-head questions buyers ask.
Get your free competitor analysisSources
- Statement of Policy Regarding Comparative Advertising. Federal Trade Commission. Read 2026-10-16.
- Advertising FAQ's: A Guide for Small Business. Federal Trade Commission. Read 2026-10-16.
- 15 U.S.C. 1125, False designations of origin, false descriptions, and dilution forbidden. Office of the Law Revision Counsel, U.S. House of Representatives. Read 2026-10-16.
- Spam policies for Google web search. Google Search Central. Read 2026-10-16.