nexa
ExploreServicesAboutTeamFAQBlogContact
GitHubStart a project
Blog · Product

Writing comparison pages people actually finish

Notes from building The Home Versus: shorter verdicts up top, fewer spec tables, and a layout that respects people who only want the answer.

Tina

Team Lead · Mobile & Web

August 27, 20262 min read

On this page

  1. The reader we design for
  2. Anatomy of the verdict box
  3. Same information, different order
  4. Why tables went to the bottom
  5. Do and don't
  6. What we learned

Most comparison articles are written for search engines first and readers second. You scroll past an intro, a table of contents and three paragraphs about why the category matters before you learn which product to buy. On The Home Versus we flipped the order. This is a case study of that decision.

1stThe verdict is the first thing on every page
1Sentence per difference that actually matters
LastWhere the full spec table lives, collapsed

The reader we design for

Someone landing on a comparison page has usually narrowed it down to two products already. They are not looking to learn about the category. They want a tie-breaker, and they want to know why so they can trust it. That makes the page closer to asking a friend who owns both which one they would buy again.

Anatomy of the verdict box

Every page opens with the same three-part block. If a reader leaves after it, the page did its job.

  1. Pick A if…Who the first product suits, in one line
  2. Pick B if…Who the second product suits, in one line
  3. The deciding trade-offThe single sentence that breaks the tie
The verdict box. Writing it well is the hardest part of every article.

A real example, written the way it appears on the page:

PICK A IF

You mostly clean hard floors

and want something light enough to carry up the stairs one-handed.

PICK B IF

You have rugs, pets or a bigger home

and can live with the extra weight for stronger pickup on carpet.

If we cannot write this block clearly, it usually means we do not understand the products well enough yet. Everything after it would have been padding.

Same information, different order

Typical comparison page

  1. Intro about the category
  2. Table of contents
  3. Generic buying guide
  4. Long spec table
  5. Verdict, finally

The Home Versus

  1. Verdict box
  2. One sentence per difference that matters
  3. Photos in real rooms
  4. Store links
  5. Full spec table, collapsed
The answer moves from the bottom of the page to the top.

Why tables went to the bottom

Spec tables look thorough but rarely help. Two vacuums with different suction numbers tell you very little about which one handles pet hair on a rug. A long table also hides the two rows that matter among twenty that do not.

A table answers what is different. A sentence answers whether it matters to you.

Do and don't

Do

  • Lead with the decision
  • Show products in real rooms
  • Put store links next to the verdict
  • Show a clear "updated" date

Don't

  • Open with why the category matters
  • Repeat the same buying guide on every page
  • Add a section just to fit a keyword
  • Hide the answer under a hero image

What we learned

None of this is clever. Most of the work was removing things, and the hardest part was trusting that a shorter, clearer page was good enough without one more section just in case.

Mentioned in this post

The Home Versus

Case study

Work with us

Need an app like The Home Versus built?

Our services

Keep reading

All posts
  • AI can design an app now. Are designers redundant?
    Read post

    Design

    AI can design an app now. Are designers redundant?

    AI makes the first draft of a screen cheap. That shifts design work to what matters most: understanding users and choosing what is right for them.

    Tina· Oct 10, 20266 min read
  • AI in software development: turn change into an advantage
    Read post

    Engineering

    AI in software development: turn change into an advantage

    AI does not replace technical thinking. With the right process, it frees teams to focus on the decisions that make products better.

    Ethan· Oct 9, 20264 min read
  • Adding AI to an app without a surprise bill
    Read post

    Engineering

    Adding AI to an app without a surprise bill

    Most of the cost of an AI feature is decided before the first request. Model routing, caching, context size and hard limits, in order of impact.

    Ethan· Oct 7, 20267 min read
nexa
ExploreServicesAboutTeamFAQBlogContact

© 2026 Nexa Tech. All rights reserved.

Web · Mobile · Open source