ECOMMERCE

Rewrite the above the fold product block

Use when a product page has traffic but low add to basket rate and the top of the page is doing nothing.

pdp-above-fold-rewrite.md

Download .md

Rewrite the above the fold block on this product page.

Product: {{PRODUCT_NAME}}
Current title, price, and copy: {{CURRENT_ABOVE_FOLD}}
Full specs: {{SPECS}}
Top three reasons customers say they bought it: {{PURCHASE_REASONS}}
Top three reasons customers hesitate: {{HESITATIONS}}
Price and any comparison anchor: {{PRICE_CONTEXT}}

Produce three complete alternatives, each with:
- Product title as shown on page, under 65 characters.
- One line under the title, under 15 words, stating what it is and who it is for.
- Three benefit bullets, each ending in a spec in brackets.
- One line that answers the biggest hesitation directly.
- Button label.
- The single assumption this version is betting on.

Then rank the three by how directly they address the recorded hesitations, and state what you would measure to tell them apart.

Rules:
- Every bracketed spec must come from the specs input.
- Do not use a superlative unless the spec supports it.
- Do not remove information the current version carries without saying what you removed and why.
- No em dashes.

Fill in before running

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

{{PRODUCT_NAME}}
{{CURRENT_ABOVE_FOLD}}
{{SPECS}}
{{PURCHASE_REASONS}}
{{HESITATIONS}}
{{PRICE_CONTEXT}}

Getting a better result

Hesitation data is what makes this work. Without it you get three rewrites of the same idea.
The "assumption this version is betting on" line tells you what the test is actually about.
Keep the bracketed specs in the live version. They are the part that survives comparison shopping.

Questions about this prompt

When is this better than rewriting the whole product page?

When a page has traffic and a poor add to basket rate. A full rewrite is the reflex and takes weeks. This changes only the block where the decision is made or lost, and it returns three complete versions to test rather than one opinion, which is a much cheaper way to be wrong.

Which input separates three real options from three rewrites?

The current block, the full specs, price context and, above all, the top three reasons customers say they bought and the top three reasons they hesitate. Without hesitation data you get three rewrites of the same idea, as the tips warn. Pull it from chat transcripts, reviews and return reasons.

What do the three versions include?

Three complete blocks, each with a title, a positioning line, three bullets ending in a bracketed spec, a hesitation answer, a button label and the assumption it bets on. Then a ranking against your recorded hesitations. The assumption line is what tells you what each test is actually measuring.

What gets edited out that should have stayed?

Stripping the bracketed specs because they interrupt the sentence. They are the part that survives a shopper comparing you with two other tabs open. Second, do not accept a version that drops information the current block carried unless the output has said what it removed and why it was safe to go.