What does it cost to help customers find your business in search?

The cost of helping customers find a small business in search depends on the work required, the competitive situation and who will implement the recommendations. A monthly fee, an audit and a technical repair are different purchases. Comparing them by price alone can hide the work your business still has to fund.

This guide does not present a market-average price. It shows how to compare real proposals for improving how customers find you, identify missing responsibilities and connect the budget to decisions you can review.

Establish what you are buying

Ask whether the proposal is for diagnosis, implementation, ongoing improvement or a combination. An audit may identify problems without fixing them. A content plan may exclude writing. A monthly service may depend on your developer completing technical work separately.

Describe the business problem before choosing the commercial model. A site that cannot be indexed needs a different first step from a site that ranks for irrelevant searches. A business expanding a service may need better information architecture and content rather than a generic package of monthly tasks.

Google’s guidance on choosing help with search visibility supports asking how recommendations will be implemented and measured. It also warns against guarantees of first place. Use those questions to clarify the proposal rather than judging it by the length of its task list.

Compare scope line by line

Work area	What a useful proposal explains	A cost that may sit elsewhere
Diagnosis	Pages reviewed, evidence collected and priorities	Specialist development investigation
Technical fixes	Exact changes and verification method	Developer implementation time
Service content	Which pages, who writes and who approves facts	Photography or subject expertise
Local visibility	Eligible profile and business-information work	Operational updates by the business
Reporting	Measures, review questions and next decisions	Analytics or enquiry-system setup

Ask the provider to separate setup work from recurring work. A one-time migration repair should not be obscured inside an indefinite monthly promise. Conversely, publishing useful new material requires ongoing business input and should not be described as a one-off switch.

Compare retainers, projects and audits

A project fee can suit a bounded requirement such as a technical audit with implementation support or a defined set of service-page improvements. The acceptance criteria should say what will be delivered and how completion will be checked.

A retainer can suit work that needs repeated review and adjustment. Ask what decisions will be made each month, what implementation capacity is included and how priorities change when the evidence changes. “Ongoing optimisation” is too vague to evaluate by itself.

An audit can be useful before a larger commitment, provided it produces an actionable plan. Ask for example deliverables showing affected URLs, evidence, priority, owner and verification. A long automated report without interpretation can leave the business paying again to understand the problem.

Calculate the complete commitment

Use a consistent period and include the work required from other suppliers. An invented example: Proposal A charges £450 a month but excludes an estimated £300 a month of agreed developer work. Proposal B charges £650 and includes that implementation scope. Their comparable monthly commitments would be £750 and £650, subject to the actual terms.

These figures are illustrative arithmetic, not UK price benchmarks or Business Web Development packages. They do not establish value without comparing the quality and relevance of the work. Check VAT treatment, minimum terms, cancellation arrangements and ownership of produced content and accounts.

Also budget for your own contribution. A provider may need the owner to explain specialist services, approve factual claims and review enquiry quality. If that input never arrives, a content plan can stall even when the supplier is available.

Ask how progress will be judged

Connect activities to a chain of evidence. A technical change should have a verification result. A revised service page should have a clear customer purpose. Reporting should examine relevant search visibility and, where measurement allows, suitable enquiries.

Avoid making a single ranking the entire objective. Search results vary, and a visible position for an unsuitable phrase may have little commercial value. Our Search Console measurement guide explains how to review queries and pages with more context.

Ask for a baseline before substantial changes begin. Record existing restrictions, tracking gaps and seasonal factors. A supplier should be able to distinguish what the evidence shows from what remains uncertain.

Recognise weak or risky proposals

Be cautious when a proposal promises guaranteed rankings, treats a fixed number of links as the main product or recommends large volumes of near-identical pages. Google’s spam policies address manipulative link practices and doorway pages. Ask what real value the proposed work creates for a visitor.

Do not assume a high fee establishes quality or that a low fee proves poor work. Ask for the reasoning, responsibilities and evidence. A small, focused repair may be more valuable than a broad package that avoids the main problem.

Choose the next bounded step

If the problem is unclear, start with a defined diagnosis. If the problem is established, ask for an implementation scope and review point. Expand ongoing work when there is a useful backlog and a way to judge progress.

Use our search visibility review framework to clarify the first step, or explore search visibility work around the services and customers that matter to your business.