CryptoWebBuild

The Local Service Website That Books Jobs: 2026 Blueprint for Trades

Page structure, service page templates and area pages that are not thin. How plumbers, heating engineers and roofers turn local searches into calls, with the Just Imagine build as the example.

A local service website books jobs when every service has its own page, every town you actually cover has its own page, and a phone number is visible before the visitor scrolls. Design matters, but structure is what decides whether the site answers the search that brought someone there.

Why most trade websites get visits but no calls

Three failures account for almost all of it, and none of them are about colour or animation.

1. The whole business is on one page

A one-page site answers one question. But "boiler not firing", "landlord gas safety certificate" and "leaking radiator valve" are three different people with three different levels of urgency. When they all land on the same block of text, each of them has to work out whether you do their job. Most do not bother.

2. The only contact path is a form

Someone with no hot water and a house full of people is not filling in a five-field form and waiting for an email. They are calling the first number they see. If your number sits in the footer, they call someone else first.

3. There is no proof above the fold

Registration numbers, insurance, years in the area, and a photograph of an actual person do more work than any headline. A visitor is deciding whether you are safe to let into their home. Answer that before you ask them to scroll.

The page map that covers the searches

That is roughly 15 to 20 pages for a single engineer. It sounds like a lot until you notice you are not writing 20 essays, you are writing six service explanations and eight local variations with real local detail.

What goes on a service page that actually converts

A service page has one job: confirm you do this exact job, in this exact area, at a price the visitor can roughly predict. The order below is the order a nervous customer thinks in.

  • An H1 that names the job and the place. "Boiler repair in Rugby" beats "Our Services". It also matches how people search.
  • Two sentences on what happens next. Who arrives, how quickly, and what it costs to find out what is wrong.
  • A price range, not a mystery. A diagnostic fee, a typical repair range, and a note that the final price is confirmed before work starts.
  • What is included. Parts, testing, certification, cleanup, and whether the work is guaranteed.
  • Proof. Registration number, insurance, a photograph, a recent job in the same town.
  • Five questions answered. The same five that come up on every call. These become your FAQ schema as well.
  • A sticky call bar on mobile. Not a chat widget that covers the number.

Area pages without the thin-content problem

Area pages get a bad reputation because most of them are the same page with a different town name. That version deserves to be ignored. A real area page carries information that is only true for that place.

  • Which services you actually deliver there, not the full menu by default.
  • Realistic response time from your base, including the honest caveat about traffic or distance.
  • Local detail: housing stock, common boiler types, parking and access quirks, local landmarks for orientation.
  • One or two jobs completed nearby, described without inventing customer names.
  • Internal links to the two or three service pages most requested in that town.
  • Structured data with areaServed matching the town, not the whole country.

Mobile is the business, not a breakpoint

Most emergency searches happen on a phone, often one-handed, often late. Four details decide whether that person becomes a call or a bounce.

Tap to call, always visible

A fixed bar at the bottom of the screen with one number and one label. No menu, no accordion, no "contact us" link. Thumb reach matters more than symmetry.

WhatsApp with the message already written

A pre-filled message containing the postcode and the problem turns a chat into a two-tap job. Something like "Hi, boiler issue at CV22, no hot water since this morning" removes the blank-screen hesitation that kills half of WhatsApp enquiries.

A three-field callback form

Name, phone, what needs fixing. Every additional field costs completions. Postcode can come on the call. If you need photos, ask for them in the WhatsApp thread after first contact.

What we shipped for Just Imagine Heating

The Rugby build has six service pages (boiler repair, installation, servicing, landlord CP12, radiators and heating, plumbing and leaks), eight area pages covering Rugby, Coventry, Leicester, Northampton, Leamington Spa, Warwick, Kenilworth and Milton Keynes, plus a proof section, an FAQ page and a quote page.

  • Gas Safe registration above the fold, with the number readers can verify themselves.
  • Three contact paths: call, WhatsApp with a 10 second quote prompt, and a callback form.
  • Static HTML and CSS, so the first screen arrives fast on a phone with two bars of signal.
  • Cookie consent that sets nothing unless accepted.

Related Engineering Guides