The reader who scrolls past your CTA didn’t leave because your offer was bad. They left because something you didn’t address made them uncertain. Objection handling in copy is the discipline of writing those doubts out loud, in the reader’s own words, and answering them plainly.
The universal objections
Almost every buyer hesitation reduces to one of six:
- “Will this actually work for me?” — the specificity objection.
- “Can I trust you?” — the credibility objection.
- “Is this the right time?” — the timing objection.
- “Can I afford it?” — the price objection.
- “What if I mess it up?” — the effort objection.
- “What if I regret it?” — the risk objection.
A page that converts answers all six — not with a FAQ dumped at the bottom, but woven into the natural order of the argument. Each objection has a section, a proof point, or a sentence dedicated to it.
How to find your reader’s real objections
The cheapest research you’ll ever do:
- Read the last thirty support tickets or sales replies you got.
- Note the exact phrases people used when they hesitated or churned.
- Read the last ten five-star reviews of a competitor. Note what they had to convince themselves of first.
- Ask the salesperson: “What’s the last question every buyer asks before signing?”
You now have a list of the exact sentences your reader is thinking. Your copy’s job is to say those sentences before they do.
The name-it-and-answer-it move
The most reliable objection-handling structure is two sentences:
You’re probably wondering whether this works for a team as small as yours. It does — more than half of our customers have under ten employees, and the onboarding takes the same forty minutes either way.
Notice the shape: acknowledge the doubt in the reader’s language, then answer with one specific fact. Not a claim, not a testimonial, not a paragraph — a fact the reader can verify or trust.
Where to place them
Objections are the outline. A useful sales page reads like this:
- Hero: names the outcome (removes objection 1 partially).
- Proof block: logos, numbers, a specific case (removes objection 2).
- How-it-works: three steps (removes objection 5).
- Testimonials picked to counter objection 1 or 3.
- Pricing framed against status quo cost (removes objection 4).
- Guarantee or trial (removes objection 6).
- FAQ: the leftover objections you couldn’t weave in.
- Final CTA.
Use the FAQ correctly
The FAQ is not the “questions you want people to ask” section. It’s the “questions people actually ask that would otherwise send them elsewhere” section. A good FAQ is uncomfortable to write. If yours reads like a brochure, rewrite it.
Good FAQ questions
- “How is this different from [obvious competitor]?”
- “What happens if we cancel after two months?”
- “Why is it more expensive than [cheaper alternative]?”
- “Will this still work if my team hates change?”
The risk-reversal principle
A guarantee, a trial, a money-back window, a pilot — these aren’t bonuses. They’re how you resolve objection six directly. The stronger your risk reversal, the more permission the reader has to take a chance on you. If you can offer one and don’t, you’re leaving conversions on the table for no reason.
Your reader’s objections aren’t obstacles to the sale. They’re the outline of it.