CONTENT WRITING

Objection-led product page copy

Use when a product or service page reads like a feature list and is not converting.

objection-led-product-page-copy.md

Download .md

You are rewriting a product page around the reasons people do not buy, not around the feature list.

Product: {{PRODUCT}}
Who buys it and what they are comparing it against: {{BUYER_AND_ALTERNATIVES}}
Real objections from sales calls, reviews or churn notes:
{{OBJECTIONS}}
Current page copy: {{CURRENT_COPY}}
Proof I can actually use - customers, numbers, guarantees, integrations: {{PROOF}}

Output:
1. Objection map table: Objection | How the current page handles it (well, weakly, not at all) | Proof available | Where on the page it should be answered.
2. Rewritten page copy in blocks, each labeled with its position (hero, subhead, proof block, comparison, pricing context, FAQ, final call to action).
3. Anything the page cannot honestly claim yet, listed as a product or marketing gap.

Rules:
- Every claim must trace to something in the proof block. Anything else gets written as [PROOF NEEDED: what].
- Do not use superlatives without evidence.
- Do not describe features without saying what they let the buyer do.
- No fake urgency, no invented testimonials, no fabricated customer names or figures.
- No em dashes. British spelling.

Fill in before running

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

{{PRODUCT}}
{{BUYER_AND_ALTERNATIVES}}
{{OBJECTIONS}}
{{CURRENT_COPY}}
{{PROOF}}

Getting a better result

Objections from churn notes are more useful than objections from the sales team memory.
The gap list in section 3 often belongs in the product roadmap, not the copy deck.
Order the objections by how often they appear before pasting them in.

Questions about this prompt

When should I restructure the page rather than polish the copy?

When it reads as a feature list and is not converting. A polish makes the same list read better. This rebuilds the page around the reasons people do not buy, so it needs real objections; without them you get the feature list reordered and the conversion problem intact.

Where should the objections come from?

The product, who buys it and what they compare it against, objections from sales calls, reviews or churn notes, the current copy, and the proof you can actually use. Churn notes beat the sales team memory of objections. Order them by how often they come up before you paste them in.

What does the rewrite come with?

An objection map showing how the current page handles each one and where it should be answered, the rewritten copy in labelled blocks from hero through to the final call to action, and a list of what the page cannot honestly claim yet. That third list often belongs on the product roadmap.

What stops the new page being honest?

Publishing over a PROOF NEEDED marker. Every claim is meant to trace back to the proof block, and each marker is a place the page writes a cheque the product cannot cash. Whether the hero should lead with the objection or the outcome is contested, so test the block order rather than debating it.