What a service page has to say to be useful

A service page’s copy — this kind of website copy is often the hardest copywriting job on a whole site — has one job: answer whether this business can do this specific job, for someone like this visitor, and what it costs to find out. That is a narrower and more useful question than the one most service pages actually answer, which is closer to “what is this service, in general terms” — a description rather than a decision aid.

The question a visitor actually arrives with

Nobody lands on a service page out of curiosity about the category. They arrive with a specific situation — a leaking pipe, a business about to open, a website that needs rebuilding — and the page’s job is to tell them, as quickly as possible, whether this business is a plausible answer to that specific situation. A page that describes the service in the abstract, without addressing the range of real situations that bring people to it, is answering a question nobody asked.

That is why a strong service page usually names the variations a service comes in — the smaller job, the larger job, the awkward edge case — rather than describing one idealised version of the work. A page that only describes the straightforward case reads as though it was written before the business had done the messy version, which most businesses have.

What most service pages say instead

The common failure is a feature list: what is included, technical specifications, a bullet list of inclusions, closing with an invitation to make contact. It is accurate, and it is inert, because it describes the service rather than answering the reader’s actual question.

What the page must answer	What it commonly says instead
Can you do my specific situation, not just the general category	A description of the service in the abstract
How long does it typically take	A generic “contact us for a timeframe”
What does it cost, or what drives the cost	Nothing, or a vague “competitive rates”
What happens if something goes wrong	Silence — this is almost never addressed
Why should I believe this business over another	An unverifiable claim rather than a specific, checkable one

Cost belongs on the page, even without a figure

A service page that avoids the cost question entirely reads as evasive, whether or not that is the intention. Where a specific figure cannot be quoted honestly — because cost genuinely varies by scope — the page should still explain what drives the cost up or down, so a reader can estimate where they sit before contacting anyone. Website design cost sets out this distinction directly: a cost page that explains the cost structure without naming a figure is doing real work, and it is a different thing from a page that avoids the subject altogether. Any figure that does appear on a page should state AUD and whether GST is included, because a number that does not say is not yet a price.

Copywriting features versus the questions they answer

A feature list and an answering page can contain the same underlying facts and read completely differently, because the difference is framing, not information. “Includes a 12-month warranty” is a feature. “If something fails within the first year, it is fixed at no charge” is the same fact, answering the reader’s actual worry — what happens if this goes wrong. Rewriting a feature list as a set of answered questions is usually a smaller edit than it looks, and it is the single highest-leverage change available to an existing service page — whether a copywriter does the rewrite or the business owner does it themselves.

Where this differs from a homepage

A service page can go deeper and narrower than a homepage is able to, because a visitor who reached it has already self-selected into caring about this specific service. Homepage copy covers the broader, faster job the homepage has to do; a service page’s copy can afford the specifics a homepage has no room for, and should use that room rather than repeating the homepage’s summary at greater length.

One page per service, or one page covering several

A related decision is whether each service gets its own page or several related services share one page. The test is whether there is genuinely enough distinct, specific content to justify a separate page — distinct situations, a distinct process, distinct pricing logic — or whether splitting a service out mainly produces two pages saying largely the same thing with a different heading. A business offering several closely related services with genuinely different considerations for each (different timeframes, different licensing, different typical problems) usually benefits from separate pages. A business whose services differ only in name, with identical process and pricing logic behind each, is often better served by one services page covering the group properly than several thin pages that each fail the answering-a-question test.

Service pages and the industries they serve

Where a service is delivered differently for different types of client — a different regulatory backdrop, a different buying trigger, a different proof point — that difference is usually better handled on a dedicated industry page than folded awkwardly into a single generic service page trying to speak to every audience at once. Industries is where this site handles that distinction for its own service pages, separating what is genuinely common to the service from what is specific to who is buying it.

What to do next

Take an existing service page and count how many sentences answer a real question a buyer would have, versus how many describe the service in the abstract. If most of the page is description, rewrite it as answers to the five questions in the table above. Where the honest answer touches what the business can and cannot claim about itself, claims you cannot make sets out the boundary before it becomes a legal problem rather than a content one.