ECOMMERCE

Head to head comparison page

Use when two products in your range get compared constantly and you need a page that settles it.

comparison-page-two-products.md

Download .md

Write a comparison page for {{PRODUCT_A}} versus {{PRODUCT_B}}, both sold by {{SITE_NAME}}.

Specs and prices:
{{SPECS_FOR_BOTH}}

Known differences customers ask about: {{COMMON_QUESTIONS}}

Output in this order:
1. VERDICT BOX - 50 words. Name which product suits which buyer. Do not hedge.
2. SPEC TABLE - rows for every attribute where the two differ. Columns: Attribute | {{PRODUCT_A}} | {{PRODUCT_B}} | Which is better and why in under 12 words. Omit attributes where they are identical, and list those separately as "Same on both".
3. FIVE DIFFERENCES THAT MATTER - each with a heading, 60 to 80 words, written in terms of what the buyer will notice in use.
4. WHO SHOULD BUY WHICH - two short blocks, three bullets each.
5. FAQ - 4 questions, answers under 45 words.

Rules:
- No spec value may appear that is not in the input. If a comparison needs a figure you do not have, write "not published" in the cell.
- Do not declare an overall winner. Decide per buyer type.
- No em dashes. No marketing adjectives without a spec behind them.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{PRODUCT_A}}
{{PRODUCT_B}}
{{SITE_NAME}}
{{SPECS_FOR_BOTH}}
{{COMMON_QUESTIONS}}

Getting a better result

Pull the common questions from on-site search and live chat logs rather than guessing them.
If one product is being discontinued, say so in the verdict box - it is the single most useful line on the page.
Keep the "Same on both" list. It stops the table implying differences that do not exist.

Questions about this prompt

When is this better than letting the spec table do the work?

When two products in your own range are compared constantly and buyers stall between them, which a raw spec table does not resolve. If the comparison people actually make is against a competitor product you do not sell, this is the wrong shape, because it assumes you hold verified specs for both sides.

What do I need for both products?

Specs and prices for both products and the questions customers really ask. Pull those from on-site search and live chat logs rather than guessing, as the tips say, because invented questions give you a page that answers things nobody wondered about while missing the one difference that is stalling the decision.

What does the page come back as?

A verdict box, a spec table of differences with a separate Same on both list, five differences written in terms of use, two buyer blocks and an FAQ. The Same on both list is the quiet win. Without it, a table listing only differences implies that everything else differs too.

What is the tempting change that backfires?

Overriding the rule against declaring an overall winner. One verdict reads decisively and sends half your buyers to the wrong product, which arrives back as returns. The other slip is filling a not published cell with a figure from an old supplier sheet rather than leaving the gap visible on the page.