Should you respond to a competitor's page about you?

Someone forwards you a link. It's a competitor's site, and the URL ends in /vs/your-product. There's a table. You lose most of the rows.

The instinct is to fix it — a blog post, a tweet, a rebuttal page, an email to their team. Almost every one of those instincts is wrong on the first day. Here are the six questions worth answering before you spend anything on it.

Is the page about you, or about the category?

Most "vs" pages are template output. A competitor writing thirty of them is running an SEO play against a keyword pattern, not against you specifically. The tell is structural: same headline shape, same table columns, same closing CTA, only the product name swapped. If you can find /vs/ pages for four other companies with identical section headings, you're looking at a content program, not an attack.

That changes what a response is for. You're not defending your reputation against a considered argument — you're competing for a search result. Those are different jobs with different budgets. A hand-written page that names you, cites specific screenshots of your product, and reads like someone actually used it is the rarer case. That one deserves attention.

Does anyone actually see it?

Check before you care. Search the exact query the page targets — "your product vs their product," "your product alternative" — and see where it ranks. Check whether it's linked from their nav, their footer, their pricing page, or nowhere at all. A page that exists only in a sitemap has a readership of roughly you.

Volume matters more than tone here. A gently unfair page ranking first for your own brand-plus-alternative query costs you real pipeline. A brutally unfair page on page four of results costs you nothing but your afternoon. Teams routinely invert this and spend their energy on the loudest page rather than the most-seen one. The related failure — treating speed as the goal — is covered in reacting first is overrated.

Is it wrong, or is it stale?

Sort every claim into three buckets, and be honest about which is which.

True. Sometimes they do have SSO on the lower tier and you don't. Note it, route it to product, move on. There is no messaging fix for a missing feature.

Stale. They tested you in March, you shipped in June, the table never updated. This is the most common bucket and the cheapest to address, because you're not arguing — you're supplying a fact. Stale claims also decay in your favor over time, which is a genuine argument for patience.

False. They're claiming something that was never true, or comparing your entry tier to their top tier without labeling it. This is the only bucket where a direct response is clearly justified, and even then, see the next question.

What does responding publicly actually cost?

A public rebuttal does three things at once, and only one of them is good.

It corrects the record for people who read your post. It also introduces your competitor's name to your audience — some of whom hadn't heard it — and it signals that the page got to you. Then it hands them a reason to update the page, link to your rebuttal, and keep the fight in a venue where they chose the terms.

The asymmetry is worth sitting with: their page is discovered by people already searching for a comparison, which means high intent and low reach. Your rebuttal is distributed to your own audience, which means low intent and high reach. You are usually amplifying more than you're correcting. The exception is a factually false claim on a well-ranked page — there, the correction has to exist somewhere public and linkable, even if you never promote it.

What should you change instead of arguing?

The best response to a competitor's comparison page is almost always your own comparison page, written straight. Not a rebuttal — an honest page that covers the same decision, names the cases where they're the better pick, and ranks for the same query.

That sounds like a concession. It converts better than a defense, because the reader arriving at that query has already decided to compare, and the page that admits a real limitation earns the credibility to be believed on everything else. It also outlives the specific dispute. We wrote about reading these pages from the other direction in what a competitor's comparison pages reveal — the same reading applies to your own.

Second-best: get the accurate version into your sales team's hands the same week. If reps are hearing the claim on calls, the page has already done its damage and a battle card beats a blog post.

How do you know when it changes?

Comparison pages are not written once. They get rows added after a competitor's release, prices corrected quietly, your name dropped entirely when you stop being a threat, or added when you start being one. The edit history is the signal — more than the page itself. A rival who updates your row within two weeks of your launch is watching you closely, and that tells you something about their operation.

This is the part nobody sustains manually. You check the page the week it appears, then never again, and six months later it says something new that no one caught. Seeto watches public surfaces like comparison pages on a schedule and surfaces the differences as discrete change events — the row that appeared, the claim that changed, the price that moved. It won't tell you whether to respond; that judgment is the whole point of the questions above. It just makes sure the page doesn't drift while you're not looking.

---

The uncomfortable answer to most of these situations: do nothing publicly, fix the one true claim, publish your own honest comparison, and put the page on a watch list. It feels passive. It's the version that's still working in a year.