Skip to content
Searchpedia SEO field notes Callum Bennett Callum

Start here

SEO Objections

Stop arguing with objections and start listening for the real risk behind them — that is the only way to close deals and keep clients.

Beginner3 min readUpdated 2026-07-27Notes by Callum Bennett

Start here

  • Listen for the real risk behind the objection before you respond.
  • Build an objection inventory from past sales calls and lost deals.
  • Use specific case studies with numbers to counter 'SEO takes too long'.
  • Never guarantee rankings; guarantee process and milestones instead.
  • Align SEO scope with business metrics like CLV and CAC to justify costs.

Plain-English take

When a prospect says "SEO is too expensive," they are almost never objecting to the number on the invoice. They are objecting to the risk of not seeing a return. I worked with a SaaS company that spent £8k/month on PPC with a cost per lead of £120. Their SEO proposal was £4k/month. The objection was price. I reframed it: if SEO reduces their blended cost per lead by 30% over six months, that saves £2,400/month — more than half the SEO fee. That changed the conversation. Another common objection: "SEO takes too long." A founder once told me six months was too long. I showed them a 30-day technical audit that fixed 404s, improved page speed, and uncovered quick wins on low-competition terms. They saw a 15% traffic increase in week six. That is what [SEO](/seo/) actually looks like: small wins early, big wins later. The counter-argument is that AI overviews have killed organic traffic. That is a trust objection. I point to competitors who still get 40% of their traffic from organic search. The data kills the myth. The decision rule is simple: when you hear an objection, stop selling and start exploring. Ask "What specifically worries you about that?" The answer reveals the real risk. You cannot reframe a concern you have not heard. Most objections are symptoms of fear — fear of wasting money, fear of looking bad to the boss, fear of another failed initiative. Your job is not to argue; it is to diagnose and prescribe. Understanding [what SEO is](/what-is-seo/) helps clients see it as an investment, not a cost.

When it actually matters

Objections matter in sales conversations, onboarding, reporting, and contract renewals. But they matter most when the stakeholder has been burned before. I had a client who said "SEO is a black box" because their previous agency reported only rankings and traffic, not leads. The decision rule: before you propose, ask what they want to see in reports. I now include a scope document in every [SEO service](/seo-service/) agreement that lists targeted keywords and milestones. That alone reduced my churn by 20%. Another edge case: a CMO objected to SEO because "our competitors are spending twice as much." I showed them a [SEO strategy](/seo-strategy/) focused on long-tail terms with lower competition. In three months they ranked for 47 new terms with zero ad spend. That was a specific example that reframed the conversation from budget to opportunity cost. When reporting, if a stakeholder says "we aren't ranking for anything," that is a scope objection. They expected all terms, not the targeted ones. I now align reporting with the scope. The real cost of mishandling an objection is not the lost deal; it is the churn that comes from a mismatch between expectation and delivery. That is why I treat objections as data, not resistance. They tell me where my proposal was unclear or where the client's priorities differ from mine. Professional [SEO consulting](/seo-consulting/) means addressing those gaps before the contract is signed.

What I got wrong

I used to think objections were rational arguments. They are emotional. I would answer "SEO can take six months" with a list of statistics. That made me sound defensive. Now I say "I understand the pressure. Let me show you what happens in the first month." The most embarrassing mistake was guaranteeing rankings. I did it twice early in my career. Both clients fired me within a quarter. You cannot guarantee what you do not control. The only guarantee is process, and even then, you have to scope for algorithm changes. I should have invested in [SEO training](/seo-training/) for my sales team earlier. That would have stopped us from overpromising. Another thing I got wrong: discounting too fast. When someone pushed back on price, I would drop the fee instead of clarifying scope and value. That made me look desperate. Now I offer a stripped-down [SEO plan](/seo-plan/) with fewer deliverables. If they want the full package, they pay the price. The counter-argument I wrestle with is "your competitor quoted half the price." I now respond with a scope comparison. Usually the competitor's proposal excludes technical audits, link building, or reporting. I have lost two deals because I refused to match a lower price. Both clients came back within a year after the cheap agency delivered nothing. The lesson: trust the value, not the price. And always listen before you respond.

Next step

Quick answers

How do you respond when a client says SEO is too expensive?

I ask what their monthly ad spend is and what their target CPA is. Then I show how SEO can lower blended acquisition costs over time. If their ad spend is £10k and SEO is £3k, the ROI conversation shifts to total cost per lead.

What if a prospect says they tried SEO before and it didn't work?

Ask what the previous agency did and what metrics they reported. Often the issue was no clear scope or they targeted impossible terms. I show a different approach: specific milestones, transparent reporting, and a focus on terms we can influence.

Should I promise a number one ranking to win a client?

No. Google explicitly warns against guarantees. If a client insists, I explain why no agency can control algorithms and offer a performance-based model tied to organic traffic or lead growth, not rankings.

Sources

Primary documentation is linked directly. Anything commercial is marked nofollow.

Notes from Callum Bennett.