DEV Community

Kevin Bkt
Kevin Bkt

Posted on Edited on

What a comparison page needs before it needs anything else

What a comparison page needs before it needs anything else

I have built a lot of small comparison pages, and the first version of each one was wrong in the same way.

It had the products, the prices, the filters, the sort. It looked like a comparison page. And nobody could tell it apart from the other fifty.

The missing part was not more data. It was the criterion.

A table is not a comparison

A table tells you what a thing costs. A comparison tells you which one to pick, and for that you need the axis they differ on.

Two products at the same price can be wildly different depending on whether you care about the monthly cost, the total over three years, the number of people included, or how long the trial lasts. Without the axis, the table hands the decision back to the reader, who had the same question you did.

That is why the useful ones start with the axis rather than the list.

The three questions that decide the shape

Before I write a single row, three questions get answered.

What is the reader comparing against? Not against the ideal version of the product, but against the realistic alternative. If the real alternative is the thing they already have, then the comparison has to make the switching cost visible, because switching cost is what usually wins.

Which single number would change their mind? If the answer is "it depends", the page has to say what it depends on and put that condition first. A page that answers "it depends" honestly is more useful than one that picks a winner to look decisive.

What is the smallest amount of information that still lets them decide? Often much less than I assume. A price, a limit, and one sentence of honest caveat beats fifteen rows of specification.

Where the criteria come from

The criteria are the part that has to be real, and they usually are not in the product pages. They are in what people complain about.

For the buying guides I have written, the axis that made the page useful was never the one I expected. It was something narrow and slightly unglamorous, like what happens when the trial runs out, or whether the price includes the thing people actually want to use it for.

Comparativo has that shape: it asks which product you are comparing, and it says the criteria out loud before the list. It is at Comparativo, and the site is at https://desenterra.com.

The same discipline applies when the comparison is across borders rather than across products. Kunibetsu compares the real cost of the same thing in different countries, and the axis it uses is the one people forget: the total once the tax, the shipping and the exchange rate are in it, not the sticker price. It is at Kunibetsu, and the site is at https://kunibetsu.com.

The point of writing the criteria down is that it forces the question. If you cannot state the axis in one sentence, you do not have a comparison page yet, you have a spreadsheet with a heading.

The last piece: the page has to be linkable

A comparison page that nobody can send to a friend is a page that only the person who wrote it will ever see.

So it needs an address, and it needs to keep that address as the products change. The content gets updated in place, the link keeps working, and the argument in the comments about which one to pick happens on the page instead of in five separate chats.

It sounds like a small thing. It is the difference between a page you built once and a page that keeps being useful, and it is the reason the ones worth reading are the ones you can link to.

Top comments (0)