Key points
- Give each service, and each distinct buyer intent, its own page with a matching URL, title and H1.
- Above the fold, a service page must say who you are, what you do, where you do it, why you can be trusted, and how to get in touch.
- Answer the questions buyers actually ask: what it involves, how long it takes, what it costs, what happens next.
- Link hub to spoke and spoke to spoke, mark pages up with Service, FAQPage and BreadcrumbList schema, and measure each page in Search Console.
- Do not mass-produce near-identical town pages. Google treats them as thin content, and they lose enquiries anyway.
One page per service and intent
A local service business usually has a handful of things people actually search for. A structural engineer is searched for as "crack inspection", "steel beam calculations", "chimney breast removal" and "structural engineer for extension", not as "structural engineering services". Each of those searches is a different intent, with a different question behind it and often a different budget. One page per intent lets the page speak directly to that question, rank for that phrase, and be quoted by an AI answer engine for that exact topic.
The test is simple: if two pages would answer the same question for the same person, merge them; if one page is answering three different questions, split it. Most businesses land on four to eight service pages plus a few informational articles.
URL and title patterns
Keep URLs short, lower case, hyphenated, and readable on their own. A pattern that works for a single-area business is /service-place, for example /crack-inspection-london. A business with several genuinely separate areas or many services may prefer /services/service/ with location handled in the copy and the title. Pick one pattern and apply it everywhere; avoid dates, IDs and parameters.
Titles should lead with the service and place, then the business: "Crack inspection in London | Panoptic Design". Keep the H1 consistent with the title but written for a human ("Crack inspection in London by a chartered structural engineer"). The meta description is your advert in the results: who, what, where and the next step, in under 160 characters.
Above the fold: who, what, where, proof, and the enquiry path
Before anyone scrolls, a service page should answer five things. Who are you (a named business, a named person where possible, a qualification). What exactly do you do on this page. Where you do it (the service area, stated plainly). Why you can be trusted (accreditation, years, a review, a recognisable client). And how to get in touch, in the way the buyer prefers: phone, WhatsApp, a short form, or a booking link. On mobile, the contact path should be visible without scrolling and reachable with a thumb.
Resist the temptation to open with a slogan. "Chartered structural engineer for crack inspections across South West London" does more than any headline about excellence.
Answer the buyer's real questions
The body of the page is where most service sites fall down. They describe the business when they should answer the buyer. A good service page works through the questions in roughly the order a buyer asks them:
- What does it involve? The actual steps, in plain words.
- When do I need it, and when don't I? Being honest about when a service is unnecessary is one of the strongest trust signals you can publish.
- How long does it take? Site visit, report, follow-up.
- What does it cost? A starting price, a typical range, or a clear statement that it is a fixed quote after a call. "Contact us for pricing" answers nothing.
- What happens next? What the buyer receives, and what they do with it.
Put the most common questions in a short FAQ at the end, with genuine answers. These are the passages answer engines lift. We go into why in What is GEO?
Internal linking: hub and spoke
Treat the home page (or a services overview) as the hub and each service page as a spoke. The hub links to every spoke with descriptive anchor text ("crack inspection in London", not "learn more"). Each spoke links back to the hub, to its two or three most related spokes, and to any supporting article or tool that helps with the decision. Breadcrumbs on every page reinforce the structure for people and for crawlers. No important page should be more than two clicks from the home page.
Structured data
Three schema.org types do most of the work on a local service site. Service on each service page (name, description, provider, areaServed), pointing to a site-wide Organization or LocalBusiness node. FAQPage only where the page has a visible FAQ, with the questions and answers matching the text exactly. BreadcrumbList everywhere. Keep the markup truthful and in sync with the page; structured data is a confirmation of what is visible, not a place to add claims.
What not to do
Do not generate forty near-identical pages that swap "Wimbledon" for "Putney" for "Richmond". Google's guidance on doorway and thin content has been clear for years, and in practice those pages rarely rank and never convert, because a buyer in Putney can see that the page knows nothing about Putney. If you genuinely serve several areas, say so on the service page, name the areas, and consider one well-written area page only where you have something real to say: projects completed there, local planning knowledge, a local phone number.
Also avoid burying each service under a generic "Services" page with one paragraph each, hiding the phone number behind a contact page, and publishing pages that need JavaScript to render their main content.
Measuring in Search Console
Google Search Console is free, and it answers the question "which pages are earning their place?". In the Performance report, filter by page and look at impressions, clicks, average position and the queries that triggered each. A page with rising impressions and a poor click-through rate has a title or description problem. A page with impressions on the right queries but position 15 needs stronger content or links. A page with no impressions after a few months is the wrong intent, or duplicated elsewhere. Compare pages monthly rather than staring at totals, and record enquiries by source page so you can see which pages produce work, not only traffic. We cover the tracking side in Why websites lose enquiries after launch.
Example · Panoptic Design
For Panoptic Design, a chartered structural engineer working across London, we rebuilt the site with six search-led service pages: crack inspection, RSJ and steel beam calculations, chimney breast removal, extensions, rear extensions and side-return extensions, plus three informational articles and a "Do I need a structural engineer?" checker that pre-qualifies enquiries. Each page states who, what and where above the fold, answers the buyer's questions in plain English, carries Service, FAQ and breadcrumb markup, and offers WhatsApp, form and phone enquiry paths. The crack-inspection page is the site's best organic performer, and every enquiry is logged with its source page.
A short checklist
- List every service people search for. One page each.
- Give each page a clean URL, a service-and-place title, and a matching H1.
- Put who, what, where, proof and the enquiry path above the fold, on mobile first.
- Answer what it involves, when it is needed, how long, how much, what next.
- Link hub to spoke, spoke to spoke, with descriptive anchor text and breadcrumbs.
- Add Service, FAQPage (where real) and BreadcrumbList markup.
- Verify the site in Search Console and review pages monthly.
- Log enquiries by source page.
Want service pages built this way? Automika builds websites and search and GEO infrastructure for UK service businesses, and custom tools such as checkers and calculators when they help qualify the enquiry. Tell us what you need and we'll tell you honestly whether we're the right build partner.
