What should a service page contain?

Service pages are typically written as descriptions of a service and read as a sequence of questions a buyer is checking off. The mismatch explains most of their weakness. The reader is not absorbing prose; they are looking for whether this is for them, what it will cost, how long it will take and what happens next, and they abandon at the first question the page declines to answer.

Writing in question order fixes most of it without adding length. What this is, in the words a customer would use rather than the words the industry uses. Who it suits and — usefully — who it does not, which is more persuasive than any claim because it demonstrates that the business turns work away. What it costs, as a range, a starting point or a minimum. How long it takes. What actually happens, step by step, so the buyer can picture the process. What is excluded. And how to begin.

The exclusions section is the counterintuitive one and it consistently outperforms expectations. Stating what is not included, what would cost extra and what you do not do reads as confidence, prevents the disputes that arise later, and removes the reason a careful buyer would hesitate. Businesses avoid it for fear of giving a reason not to proceed, and it more often removes the reason to hesitate.

Process detail does more than most people expect too, for a specific reason: uncertainty about what will happen is a major source of delay in service purchases. A buyer who can see that the first step is a call, the second a visit, the third a written quote, and that nothing is committed until they say so, has had their main anxiety addressed before they contact anybody. That is a conversion mechanism rather than a courtesy.

The two things that add least are the things most service pages contain the most of: general claims about quality and long paragraphs of background about the business. Neither differentiates, because every competitor makes the same claims, and neither answers a question the buyer is holding. Background belongs on a page about the business, where the people who want it will look for it.

One structural point worth observing: one service per page. Combining several into a single page means each is described shallowly, none can rank or be retrieved for its own query, and the buyer has to sort through work they did not ask about. Separate pages, each answering one question set completely and linking to the neighbours, is better for the reader and better for every system that reads pages.