ADS & LANDING PAGES

Objection handling section for a landing page

Use when traffic reaches the page but hesitates, and you need the doubts answered in copy.

objection-handling-section.md

Download .md

You are a conversion copywriter building the objection handling section of a landing page.

Product: {{PRODUCT}}
Price and commitment: {{PRICE_AND_COMMITMENT}}
Audience: {{AUDIENCE}}
Objections I hear from sales or support: {{KNOWN_OBJECTIONS}}
What I can honestly offer to reduce risk (guarantee, trial, cancellation, support): {{RISK_REDUCERS}}

Step 1: List 8 objections. Start with the ones I gave you, then add likely ones for this audience and price point. Mark each as Supplied or Inferred.
Step 2: Rank them by how likely they are to stop a purchase, and say why for each rank.
Step 3: For the top 6, write the on-page treatment as a table: Objection (in the visitor's own words), Short answer (max 25 words), Evidence needed, Where it should sit on the page.
Step 4: Write the section as finished copy - a heading plus six question and answer pairs, each answer under 45 words.

Rules:
- Answer the objection directly in the first sentence. Do not open by restating the question.
- Never promise something not in my risk reducers. Flag it as {{POLICY_CHECK}} if you think an offer would help but I have not confirmed it.
- Do not use fake reassurance like "you have nothing to lose".
- 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}}
{{PRICE_AND_COMMITMENT}}
{{AUDIENCE}}
{{KNOWN_OBJECTIONS}}
{{RISK_REDUCERS}}
{{POLICY_CHECK}}

Getting a better result

Pull the objections from sales call notes or support tickets rather than guessing them.
Put the price objection near the pricing block, not buried in an FAQ at the bottom.
If an answer needs evidence you do not have, get the evidence rather than softening the claim.

Questions about this prompt

When is this different from writing an FAQ?

Reach for it when people arrive at the page and stall. An FAQ answers questions about the product; this answers reasons not to buy, ranks them by how likely each is to stop a purchase, and says where on the page each belongs. If traffic is not arriving at all, your problem is upstream of this prompt.

What do I need in front of me?

Price and commitment, the audience, {{KNOWN_OBJECTIONS}} taken from sales call notes or support tickets rather than invented at a desk, and {{RISK_REDUCERS}} you can genuinely honour. That last field matters because anything outside it returns as {{POLICY_CHECK}}, and a guarantee written into a page before anyone confirmed it is a problem you do not want.

What does it produce?

Eight objections marked Supplied or Inferred, ranked with reasoning, then the top six as a placement table and again as finished copy. The Supplied and Inferred labels are the part to check. An inferred objection ranked first is an assumption about your buyers that nobody has verified against a real conversation.

What is the mistake that costs me?

Taking the finished copy and dropping all six answers into an accordion at the foot of the page. The placement column exists because the price objection belongs beside the pricing block, where it is felt. Resist softening any answer whose evidence is missing, too. Go and get the evidence, since vague reassurance reads as an admission.