The service page blueprint

A single page listing eleven services ranks for none of them and convinces nobody. One page per service is the least glamorous high-leverage change available.

The logic is simple. A search engine, and now a language model, is trying to find the best page about a specific need. A page covering eleven services is the best page about none of them. It also cannot answer the specific questions a customer has about the one thing they actually need.

The blueprint, in order

1. Headline: the service, in the customer’s words

   Name the service the way a customer says it, plus the location. "Boiler repair in Sheffield", not "Domestic heating solutions".

2. The direct answer, in two sentences

   What it is, who it is for, and roughly what it costs or how pricing works. This block is what gets extracted by AI answers, so it goes at the top rather than the bottom.

3. What is included, as a list

   The actual scope. This is the section that prevents the awkward call later, and lists are extractable in a way paragraphs are not.

4. What it costs, or how you price

   The most searched and least answered question on the internet. A range, a starting price, a call-out fee, or a plain explanation of what drives the price. Saying "it depends, here is what it depends on" is vastly better than silence.

5. Proof, specific to this service

   Photographs of this job, reviews mentioning this job. Generic proof is much weaker here than specific proof.

6. How it works, three or four steps

   Removes the fear of the unknown, which is the real objection for anyone letting a stranger into their home.

7. FAQs, the real ones

   The questions you actually get asked on the phone about this service. Five to eight. This section is disproportionately quoted by AI assistants.

8. One clear next step

   Phone number and a short form. The same on every service page.

The mistakes that undo it

• Duplicating the same page for twenty towns, changing only the place name. Search engines handle this badly and customers see through it instantly. Write genuinely different pages, or write one good page and list the areas you cover.
• Writing for the search engine instead of the caller. Repeating the service name fourteen times reads as spam to both a human and a model.
• Hiding the price. The competitor who publishes a range gets the call.
• No internal links. Each service page should link to the related ones and back to the main services page.
• Thin pages. A service page of eighty words is worse than not having one, because it looks like an abandoned site.

The rollout

• List every service you want enquiries for. Rank by profitability, not by volume.
• Build the top three first, using the blueprint exactly.
• Link them from the main navigation, not just a dropdown.
• Add the same three or four FAQ questions everyone asks, plus the ones specific to each service.
• Add Service schema markup to each page.
• Then do the rest, one a week. All at once produces twenty thin pages.