history<\/a> before it addresses the customer’s need, loses the visitors who could not, in those few seconds, confirm they were in the right place.<\/p>\nThe opening also establishes whose page this is. A customer who reads an opening that speaks directly to their need feels understood, and reads on; a customer who reads an opening recounting the business’s years in the trade feels, correctly, that the page is not yet about them. The opening is the page’s first and clearest chance to show the customer that they, and not the business, are its subject — and a page that gets it right has earned the few more seconds it needs to make its fuller case.<\/p>\n
The body: the concrete answer<\/h3>\n
The body of the page is the answer itself \u2014 the substantive account of the service. It is the longest part, and its single governing quality is concreteness.<\/p>\n
The body should say, specifically, what the service is, who it is for, and what the customer actually receives. It should describe the service as it really is, in particular and tangible terms, rather than in the vague and flattering language that service pages so often default to. A later section treats the writing of this description directly, because it is where most service pages fail.<\/p>\n
The body should also be organised, not poured out in one undifferentiated mass. A customer reading it has a sequence of questions, and the body is easier to use when its parts are marked by headings that name what each part addresses — so that a customer who already knows they want the service, and only needs the price or the process, can find that part without reading the whole. The body is a reference as much as a pitch, and it should be built so the customer can navigate it.<\/p>\n
The proof: evidence the customer can trust<\/h3>\n
The proof section addresses the doubt that the body alone cannot settle. The body says what the business offers; the proof gives the customer a reason to believe it. Because a service is something the customer cannot inspect in advance, this section does real work.<\/p>\n
Proof takes several forms, and a page should use whichever it genuinely has: the testimony of past customers, examples of work done, relevant credentials, a record the customer can check. What unites good proof is that it is specific and verifiable rather than asserted \u2014 a concrete review or a real example carries weight that the business’s own claims about itself cannot.<\/p>\n
Proof is most persuasive when it is placed where the relevant doubt arises, rather than gathered into a single block at the foot of the page. A claim made in the body and immediately followed by the evidence for it is more convincing than the same claim and the same evidence separated by several screens. The proof section is a useful idea for organising the page, but the proof itself works hardest when it sits next to the thing it is proving.<\/p>\n
The close: the way to act<\/h3>\n
The close is where the page converts. A customer who has read the page and is persuaded must, at that moment, be given a clear and easy way to act \u2014 and a page that has done everything else well and then leaves the persuaded customer with no obvious next step has wasted its own success.<\/p>\n
The close should make the next step single, obvious, and easy. A later section treats the call to action directly; the structural point here is only that the page must end by converting the persuasion it has built into an action the customer can take without effort.<\/p>\n
It is worth noting that a long service page may need more than one close. A customer persuaded early should not have to scroll to the foot of the page to find the way to act, and a customer who reads to the end should find it there too — so the way to act may reasonably appear more than once on a long page, always as the same single, clear action. The close is less a fixed location than a standing offer the page keeps making.<\/p>\n
Writing the service description itself<\/h2>\n
The body of the service page is where most service pages fail, and they fail in a predictable way: the description is vague. It is worth being precise about the failure and its remedy, because the remedy is the single most valuable thing in this article.<\/p>\n
The failure looks like this. A service page describes the service in language that is positive but empty \u2014 it speaks of quality, of dedication, of a customer-focused approach, of solutions tailored to the client. The words are pleasant and they are also interchangeable; the same sentences would fit any competitor’s page, and so they tell the customer nothing that helps a decision.<\/p>\n
The remedy is concreteness. A concrete description says the specific, particular things that are true of this service: what is actually done, how it is actually done, what the customer actually receives, what happens at each stage, what is and is not included. A customer reading a concrete description can picture the service and judge whether it fits their need; a customer reading a vague one is left to guess.<\/p>\n
There is a test for this, and it is worth applying to every sentence on the page. If a sentence could appear, unchanged, on a competitor’s page, it is not yet doing its job \u2014 it is describing services in general rather than this service in particular. The sentences that survive the test are the ones that say something only this business could truthfully say, and those are the sentences that help a customer decide.<\/p>\n
Honesty belongs here as well as concreteness. The description should be accurate about what the service is and is not \u2014 because, in the framing this series draws from Akerlof, a page that oversells creates an expectation the delivery cannot meet, and the gap between the two is felt by the customer as a breach (Akerlof, 1970). A concrete and honest description is also, conveniently, the most persuasive kind: specific truth is more convincing than general praise.<\/p>\n
The on-page SEO of a service page<\/h2>\n
The service page must rank, and the on-page SEO that lets it rank is the subject of the pillar article earlier in this series; this section applies that material briefly to the service page in particular rather than repeating it.<\/p>\n
The page’s title and main heading should name the service in the customer’s words, so that a customer scanning a list of search results recognises it as the answer to their question. The page should be built around the language customers actually use for the service, identified by the keyword research the pillar article described. And the page should be built to transactional intent \u2014 to a customer ready to act \u2014 which means the path to acting is prominent rather than buried.<\/p>\n
The reassuring point, made at length in the pillar article, is that none of this conflicts with writing the page to convert. A concrete, honest, well-structured service description written for the customer is, by that fact, the kind of page a search engine is built to rank. The on-page SEO of a service page is not a separate layer added on top of the persuasion; it is, in the main, the same work seen from the search engine’s side.<\/p>\n
Writing to convert: what makes a customer act<\/h2>\n
Conversion is the second job, and it is worth setting out what actually moves a customer from reading the page to acting on it. Conversion is not a trick; it is the removal of the reasons a persuadable customer does not act.<\/p>\n
The first thing that makes a customer act is clarity. A customer who understands exactly what is offered, what it costs, and what happens next can decide; a customer left uncertain on any of those points tends not to, because uncertainty is itself a reason to delay. Much of conversion is simply the page being clear where a vague page is unclear.<\/p>\n
The second is trust, which the proof section builds \u2014 a customer acts when they believe the business can deliver what the page describes. The third is the absence of friction: the page must not make acting harder than it needs to be, by hiding the way to act, by demanding more of the customer than the moment requires, or by introducing a doubt at the last step.<\/p>\n
It should be noted that conversion is mostly subtraction, not addition. A page does not convert better by adding persuasive pressure; it converts better by removing the uncertainties, the doubts, and the obstacles that were holding a willing customer back. The next two sections treat the two largest of those: the customer’s doubts, and the friction at the point of action.<\/p>\n
Addressing the customer’s doubts and objections<\/h2>\n
Every customer reading a service page is also, silently, raising objections to it. They are wondering whether the service really fits their situation, whether the price is justified, whether the business is as good as it claims, whether something will go wrong. A page that ignores these doubts leaves them intact, and an intact doubt is a customer who does not act.<\/p>\n
The technique that addresses this is straightforward to state and widely neglected: the page should name the customer’s likely doubts and answer them, on the page, before the customer has to ask. A business knows what its customers worry about \u2014 it has heard the questions and the hesitations many times \u2014 and the page should take those known worries and meet them directly.<\/p>\n
This feels, to many business owners, counterintuitive. Naming a doubt seems like raising a problem the customer might not have thought of. In practice the customer has almost always thought of it already, and a page that names the doubt and answers it honestly does two things at once: it removes the specific objection, and it shows the customer a business confident enough to address the hard questions rather than avoid them.<\/p>\n
An honestly answered objection is therefore not a weakness admitted but trust earned. The page that says plainly who its service is not suitable for, or what its price reflects, or how it handles the thing that sometimes goes wrong, is more convincing than the page that pretends no doubt could arise. Addressing objections is one of the most powerful conversion techniques available, and it costs nothing but the willingness to be candid.<\/p>\n
Pricing on a service page: to show it or not<\/h2>\n
One question divides small businesses more than almost any other about their service pages: whether to put prices on the page at all. The question is genuine, and it deserves a reasoned answer rather than a rule.<\/p>\n
The case for showing prices rests on the customer’s experience. Price is one of the things a customer most needs to know in order to decide, and a page that withholds it has left a central question unanswered — which, as the section on conversion argued, is itself a reason a customer does not act. A customer who cannot find a price often assumes the worst, or simply moves to a competitor whose page told them.<\/p>\n
The case against showing prices is real for some businesses. Where a service is genuinely bespoke, and its cost depends heavily on a customer’s particular situation, a single printed price may be misleading or impossible — and a business in that position has a legitimate reason to handle price through an enquiry rather than on the page.<\/p>\n
The honest middle ground serves most businesses well. A page need not always show an exact price, but it should almost always tell the customer something about price — a starting figure, a typical range, the factors that determine the cost, an example. The instinct to say nothing about price is usually the business’s discomfort rather than the customer’s interest; the customer wants a sense of the cost, and a page that gives them none has, on a question that matters, left them guessing.<\/p>\n
Whatever a business decides, the decision should be made for the customer’s sake and not the business’s. A business that hides its price because it fears the customer will balk has misread the situation: the customer will learn the price eventually, and learning it late, after investing time in an enquiry, tends to produce more resentment than learning it early. Transparency about price, in whatever form the business can honestly offer it, is part of the honesty the whole page depends on.<\/p>\n
The call to action<\/h2>\n
The call to action is the close of the page \u2014 the specific instruction that tells the persuaded customer how to act. It is a small element, and a remarkable number of service pages get it wrong.<\/p>\n
A good call to action has three qualities. It is single: the page asks the customer to do one clear thing, rather than offering several competing actions among which the customer must choose. It is obvious: it is visible and prominent, placed where a customer who has finished reading naturally looks. And it is easy: the action it asks for is proportionate to the moment, not a larger commitment than a customer at this stage is ready to make.<\/p>\n
The most common failure is the buried call to action \u2014 a page that persuades the customer and then makes them hunt for the way to respond. A customer who has been persuaded and cannot immediately see how to act will, often, simply leave; the persuasion does not survive the search for a contact form. The way to act should be present where the persuasion lands.<\/p>\n
The second most common failure is the crowded close: a page that ends by offering the customer four different things to do, and so, in effect, asks them to make a second decision after the first. A single clear action converts better than a choice of actions, because it removes a final small uncertainty at the exact moment the page most needs the customer to move.<\/p>\n
Common service page mistakes<\/h2>\n
A few mistakes recur across service pages often enough to be worth naming as a group, since each undermines one of the page’s two jobs.<\/p>\n
The first is the vague description \u2014 the body written in interchangeable praise rather than concrete particulars, treated at length above. The second is the absence of proof: a page that asserts the business’s quality and gives the customer no verifiable reason to believe it. The third is writing about the business rather than the customer \u2014 a page that recounts the business’s history and values where it should be answering the customer’s question.<\/p>\n
The fourth is the buried or crowded call to action, which loses customers the page has already persuaded. The fifth is ignoring search intent \u2014 building the page without regard to the question it is meant to receive, so that it ranks for the wrong search or no search. The sixth, treated in the next section, is the single page that tries to cover several distinct services at once.<\/p>\n
One page per service<\/h2>\n
A structural decision shapes whether a business’s service pages can work at all: whether each distinct service has its own page, or whether one page tries to cover several. The answer, with few exceptions, is one page per service.<\/p>\n
The reason follows from the principle that a page is an answer to a question. Distinct services answer distinct questions \u2014 a customer searching for one of them is not searching for the others \u2014 and a single page covering several services is therefore not a clear answer to any of them. It is a compromise that serves each of its searches partially and none of them well.<\/p>\n
A single combined page also ranks poorly, for the same reason. A search engine assessing the page cannot see it as a focused answer to any one query, because it is not; a dedicated page for each service is a clearer, stronger answer to that service’s search than a shared page can be. This is the on-page version of an argument a companion series on this blog made about directory listings, that one focused, complete instance does more than a scattered, partial one.<\/p>\n
The practical instruction is to give each genuinely distinct service its own page, written to that service’s question and that service’s customer. A business with several services and one page describing all of them has, in effect, one weak page where it could have several strong ones \u2014 and should treat building the separate pages as a priority, since the service pages are, as this article began by arguing, the pages that do the heaviest commercial work.<\/p>\n
How a service page connects to the rest of the site<\/h2>\n
A service page is not an island, and how it connects to the rest of the site affects both of its jobs. The connections are made by internal links, and they run in two directions.<\/p>\n
Links into the service page matter for ranking and for the customer’s path. Other relevant pages on the site — the homepage, related articles, a page about a related service — should link to the service page where it is genuinely relevant, because those links help a search engine understand the page’s importance and help a customer who is elsewhere on the site find their way to it. A service page that nothing else links to is harder for both to reach.<\/p>\n
Links out of the service page matter for the customer who is not quite ready to act. A customer reading the page may have a related question, or may want to see an example, or may be comparing this service with another the business offers — and a well-placed link lets them follow that need without leaving the site. The links out should be genuine and few, chosen to help rather than to distract from the page’s own job of converting.<\/p>\n
The practical instruction is to treat each service page as a node in the site, not a leaf. It should be reachable from the pages a customer might come from, and it should offer a sensible next step to the customer who needs one — while keeping its own call to action, as the section on the close argued, the single clearest thing on the page.<\/p>\n
A service page checklist<\/h2>\n
The table below draws the article together as a checklist. Each row is something a working service page should do, with the job it mainly serves \u2014 ranking, converting, or both.<\/p>\n