If you run a service business, you'll likely have a few service pages on your website. Service pages are the dedicated pages that detail your business's services (for example, an accountant might have separate service pages for Tax returns, payroll or year-end accounts).
Open one of your service pages and ask yourself a question: is this written for you, or for your buyer?
Most of the time, you already know the answer.
The page lists your services. Describes your process. Mentions how long you've been trading. It's accurate, it's professional, and it's probably not getting you enquiries.
That's the problem. The service page — the one that should be doing the heaviest lifting on your site — reads like something written for an internal review. You need to speak to the founder who's fed up with their current supplier and is Googling alternatives at 9pm.
The mistake that kills most service pages
The headline is the name of the service. "IT Support." "Commercial Cleaning." "Employment Law."
Then a paragraph about the company. How long they've been going, how dedicated the team is, something vague about quality.
Then a list of features.
Then maybe a contact form.
At no point does any of it speak to what the buyer is actually thinking. And your buyer isn't reading your page thinking "tell me about your company." They're thinking: can these people fix my problem, and will dealing with them be a nightmare?
Your page needs to answer that.
Lead with the outcome, not the service
The single most effective change you can make is to lead with what the client gets, not a description of what you do.
Two opening lines for an IT support company:
Version A: "We provide IT support for businesses across the UK."
Version B: "Your team should spend their day on work that matters — not waiting on hold for IT help."
Same service. Version A talks about the company. Version B talks to the buyer.
This isn't wordplay. It's the difference between a page someone skims and a page someone reads. Professional services businesses that align their messaging with what buyers actually want tend to convert around 4.6% of visitors — roughly double the B2B average. The ones that lead with features don't.
Before you write a line, ask: what does my client's working day look like after they hire me? Start there.
Write for the person making the decision
Service pages make sense to the person who built the business. The terminology is familiar. The structure follows how they think about the work.
The MD from a completely different industry reading it has a different set of questions entirely:
- Does this actually solve the thing that's been bothering me?
- Have they worked with businesses like mine?
- How can I trust these guys will deliver?
- Is this going to be a hassle?
- Can I justify the spend?
Plain language answers those questions. Industry jargon doesn't. Internal terminology doesn't. The safest test: read a sentence out loud and ask whether you'd say it in a client meeting, or when you explain to your Grandma what it is that you do. If you wouldn't say it, don't write it.
The words that convert are usually the words your clients use to describe their problem — not the words you use to describe your solution. If you've never asked a client what they were struggling with before they hired you, their answer belongs on your service page.
A structure that actually works
No single template fits every service, industry or market, but this order works for most UK service businesses:
- Headline — the outcome they want
Specific beats generic. "IT support that keeps your team working" beats "we provide IT services." - Sub-headline — who it's for
Qualify your buyer in one sentence. "For manufacturers with 50+ staff who've outgrown their current IT provider" is worth ten times more than "for businesses of all sizes." - The problem
Name the frustration before you pitch the solution. If your clients usually come to you after being let down by a generalist, say that. Buyers need to feel recognised before they trust you. - What you do
Now you explain the service — but through the client's experience, not your internal process. "You'll have a dedicated account manager, a four-hour response guarantee, and a monthly review call" lands better than "we provide proactive monitoring, incident management, and strategic IT planning." - Proof
A specific result from a real client. "Highly recommended" is white noise. "We cut downtime by 60% in the first three months at our logistics firm" is a reason to get in touch. - One next step
One CTA. Tell them exactly what happens when they click it: "Get a quote" or "Fix your IT problems today". Don't have four buttons all saying different things sprawled across the page.
The “so what" test
Read every claim on your page and ask: so what?
"Established in 2003." So what does 23 years in business mean for the person hiring you today? Better expertise? Stronger supplier relationships? If you can't answer that, cut it.
"We use the latest technology." So what does that translate to for the client? Faster turnaround? Fewer errors? Say that instead.
"We're passionate about what we do." Every competitor's website says the same thing. It registers as nothing.
The claims that survive this test are the ones worth keeping. The ones that don't — and there are usually a lot of them — are just taking up space that could be making an argument.
One page, one decision
A common mistake is cramming every variation of a service onto one page. Basic package, premium package, bespoke option, retainer — all of it, on one page, for everyone.
The result is a page that's confusing for everyone and convincing for no one.
If you serve meaningfully different audiences, they need separate pages. A page for SME IT support and a page for enterprise IT support will both convert better than one page trying to do both jobs at once. Pages with fewer than 10 elements convert at roughly twice the rate of pages with 40 or more. Clarity is the mechanism. Comprehensiveness works against you.
The version of the page that actually gets enquiries
The best service pages read like a conversation with a good salesperson. Someone who gets your problem, knows their stuff, and doesn't waste your time making their pitch about themselves.
They don't describe the company. They show the company understands you.
That's the whole shift. Not the design. Not the layout. Not a new font. The words, written for the person reading them.
If your service page reads the way it did when the site launched, there's a reasonable chance it was written for you. The question worth asking is whether it's working for anyone else.
.svg)
.svg)