What to do when a client says “too expensive” — how to handle a pricing conversation

A conversation about price starts off well when you do not instinctively defend the offer, but instead check what the client is really questioning. In the sale of SEO services, the words “too expensive” rarely mean only a lack of money. Most often, the client does not yet see the link between the scope of work, the risk of doing nothing and the business outcome. If you recognise that gap precisely, it is easier to lead the conversation without unnecessary discounts and without promises that cannot be made honestly.

How to effectively recognise and understand clients’ price objections?

Effectively recognising a price objection means establishing whether the problem is budget, value, scope or the risk of working together. This matters because these situations require different responses. When the client does not understand the value, you need to clarify the business outcome. When they do not trust you, you need to show the assumptions, dependencies and how the work will be verified.

In SEO, a price objection often results from comparing a cheaper offer, an unclear scope, a long time horizon for results or implementation constraints on the client’s side. For the client, these reasons sound similar, but commercially they mean something different. A cheaper offer may cut out analytics, content, links or responsibility for implementation. In turn, pressure for a quick result usually clashes with the real time needed for indexing, publishing and implementing changes.

You also need to distinguish an objection from a low project priority. If the client has the budget but not the resources to implement recommendations, price is often just a convenient shortcut. In that case, defending the hourly rate does nothing, because the problem lies in the organisation’s readiness. The worst reaction is an immediate discount, because it confirms that the price was arbitrary.

Key questions that uncover the reasons behind price objections

Key questions that uncover the reasons behind price objections check what the offer is expensive against and which business goal is meant to justify the spend. Without this, the conversation quickly turns into comparing amounts alone. Good questions organise the discussion around budget, timing, expected return and responsibility for implementation. This makes it clear whether the scope needs narrowing, the timeline changing or the purpose of the project explaining first.

In practice, the following questions work best:

• Compared with which offer or solution is our proposal too expensive?
• What business goal should SEO achieve and by when?
• What budget is realistic for this project or the first stage?
• How will you know that the investment is starting to pay back?
• Who on your side implements the technical and content recommendations?

The answers to these questions change the meaning of the price conversation, because they reveal what actually builds the cost. If the client is comparing a full scope with a simplified offer, you need to show the difference in work and responsibility. If the goal is a fast initial stage, it is more sensible to talk about priorities than to cut everything at once. When the client lacks implementation resources, that must be accounted for honestly before the price is agreed.

What affects the cost of SEO services and how to present it to the client?

The cost of SEO services is affected primarily by the scope of work, the complexity of the site, market competitiveness and the level of responsibility on the provider’s side. These elements determine how much work needs to be done and how difficult the implementation will be. A simple local site is priced differently from a store across several markets. The difference does not come from the rate itself, but from the actual amount of work and risk.

The price is most often increased by large websites, multiple language versions, indexing issues, the need for regular content, link building and extensive analytics. If the project covers several countries, hreflang issues, local intent and separate content come into play. If the site has technical errors or runs on JavaScript, the share of specialist work grows, as does dependence on developers. When the agency takes on greater responsibility for the result, the cost of coordination, prioritisation and reporting also increases.

The best way to show the price to the client is to break it down into logical areas and link each of them to a business outcome. You are not selling a number of hours alone, but the scope of activities needed to improve visibility, non-brand traffic, leads or sales. This way the client can see what they are paying for and what disappears if the budget is reduced. That is much more honest than a general statement that the project is “more demanding”.

In practice, it works well to show the starting point, the backlog of priorities, implementation dependencies and work scenarios instead of guarantees. Such a presentation organises the conversation, because the price stops being abstract. The client can then assess whether they want the full scope, stage one with quick wins, or a limited cooperation model. This usually reduces pressure for a discount, because the conversation shifts from the amount to choosing a variant.

What are the different types of SEO work and how do they affect price?

Different types of SEO work affect the price because they require different time, skills and team involvement from the client side. Not every SEO service means the same set of tasks. Some projects are mainly technical, others are based on content, links or analytics. That is why two “SEO” offers can have a similar name but a completely different workload.

Technical SEO usually raises the cost when issues with crawling, indexing, JavaScript, structured data or hreflang need to be solved. This is an area where diagnosis alone is not enough, because implementation still has to be followed through. If the client has an available development team, the project can be simpler organisationally. If not, the provider has to take on a larger coordination role, and that affects the price.

On-page and content increase the cost as the site grows and more materials are needed. With topic clusters, briefs, page optimisation and internal linking, it is not just writing that matters, but also planning the content architecture. The bigger the content gap, the more work there is at the start. This matters because the client often sees only the cost of articles, not the whole process needed to use them effectively.

Off-page, that is digital PR and link acquisition, also strongly differentiates budgets. This area requires source selection, material preparation and control over publication quality. It is not a technical add-on, but a separate workstream. If the competition has a strong link profile, skipping this stage may limit the effects of other actions.

Analytics affects the price when tracking, KPI and reporting need to be set up around real business decisions. Without that, it is hard to assess honestly whether visibility translates into leads or sales. In more complex projects, measurement of implementations, time to implementation and the health of indexing also come into play. This is not always the most visible part of the service, but it often decides the quality of project management.

AI search and AIO increase the scope because they require rebuilding content for answers, entities, source quality, FAQs, semantics and freshness. That is extra work, not an automatic bonus to classic SEO. This needs to be made clear to the client, especially when they expect quick visibility in AI answers. An honest conversation here means showing the additional scope without promising an outcome that cannot be guaranteed.

How to emphasise the business value of SEO in a conversation with a client?

You emphasise the business value of SEO when you connect the scope of work with a specific outcome for the client’s business. Visibility improvement alone is rarely enough as an argument. The client needs to hear what that visibility can change operationally and commercially. In practice, this most often means more non-brand traffic, more leads or sales, better indexing and less dependence on ads.

The best approach is to talk about the effect, not the specialist’s activities. If a technical audit is meant to reduce losses caused by indexing errors, say so directly. If content is meant to capture traffic from informational and transactional queries, show where the gap is today. A client accepts the price more easily when they understand the cost of doing nothing, not just the cost of the service.

In this part of the conversation, do not promise positions or quick growth. Instead, show the starting point, assumptions and the conditions on which the result depends. It is worth pointing out what needs to happen on the client side, especially with implementations, content publication and analytics. That builds credibility, because the price stops looking like an arbitrary figure.

The value also needs to be based on KPI that the client considers important from a business perspective. For one project it will be non-brand traffic and the number of leads, for another sales, implemented recommendations or time to implement changes. In sites with technical issues, indexing health and crawl budget can be important. This means the conversation does not end with the general statement that SEO “works in the long term”.

Evidence is more important than the salesperson’s confidence. Show the priority backlog, milestones, reporting method and scenarios rather than guarantees. The client should know how progress will be assessed, even if the final result depends on many factors. This is especially important in AI search and AIO, where the scope of work is growing, but presence in AI answers cannot be honestly guaranteed.

Alternative strategies instead of lowering the price

Instead of lowering the price, propose collaboration options tailored to the client’s budget, deadline and resources. This shift moves the conversation from conflict to decision-making. The client does not have to accept or reject one version of the proposal. They can choose the model that is organisationally realistic for them.

Usually two or three options are enough. One can cover the full scope, another the first stage with quick wins, and a third a limited model with greater involvement from the client’s team. Sometimes a longer schedule is a better solution than a lower monthly price. In SEO projects, that is often safer than aggressively cutting the scope at the start.

A good option must clearly show what stays and what drops out of the offer. If you reduce the budget, indicate whether some content, analytics, link building, the frequency of work or the level of responsibility for the outcome disappears. This way the client sees the consequences of their decision. Such transparency protects both sides from later disappointment.

A discount only makes sense when the working conditions change. You can lower the price for a smaller scope, a longer contract, less frequent reporting or implementations on the client’s side. It is not worth cutting the amount without changing anything, because you undermine your own valuation. This is one of the most common mistakes in price discussions.

Also avoid defending the hourly rate itself. The client usually does not buy hours, but a solution to a problem and a way to achieve the result. When the conversation turns to hours alone, it is easy to lose out to a cheaper but weaker proposal. It is better to compare scope, implementation dependencies and a realistic work plan.

If, despite the options, the client still only says “too expensive”, go back to qualification. Check whether the project is a real priority for them, who will implement the recommendations and within what timeframe the investment is supposed to pay off. Sometimes the problem is not the price, but a lack of readiness to work together. In that situation, it is better to name it than to try to save the sale with a proposal that cannot be delivered.

The most common mistakes in price conversations and how to avoid them

The most common mistakes are giving a quick discount, defending the price instead of the value, using language that is too technical, making promises without backing them up and failing to qualify the client. Each of them weakens your position in the conversation and obscures the meaning of the proposal. The client then starts comparing only amounts, because they were not given clear decision criteria. If the price is to be defended, the client must first understand the scope, the conditions for success and the consequences of reducing the budget.

In practice, it is best to stick to a few simple rules:

• Do not give a discount automatically. First establish whether the problem is budget, priority, scope or lack of trust.
• Do not defend the rate itself. Show what is included in the work, what requires implementations and what business problem it solves.
• Do not use specialist language without explaining it. The client should understand the effects, not the terminology itself.
• Do not promise positions or presence in AI answers. Instead, show scenarios, dependencies and how progress will be measured.
• Do not leave room for assumptions on the client’s side. State clearly who implements the recommendations and what will happen if implementations are delayed.

A separate mistake is having a conversation with a client who is not organisationally ready to work together. If there is no budget, no implementation resources or no realistic payback timeframe, the price objection will keep coming back. In that case, it is better to narrow the scope, break the plan into stages or honestly walk away from the project. This protects margin and reduces the risk of conflict after the collaboration starts.

Avoiding these mistakes is not about more persuasive selling, but about better decision management. A price conversation should end with a choice of conditions, not a tug-of-war. When the client sees options, limitations and metrics, they find it easier to make an informed decision. That way, the price stops being abstract and becomes a consequence of the agreed scope.