Service-area pages for trades: when should you create them?

Choose the smallest format that answers the question

A coverage section answers “do you work here?” A service page answers “do you do this kind of job?” A project story shows what you did on a particular piece of work. A service-area page can combine useful local service information when there is enough to say. Those formats are related, but they should not all repeat the same paragraphs under different headings.

Start by asking what the customer needs to decide. If you offer the same service and process across a compact group of nearby towns, one well-written service page with a clear coverage list may be enough. If the only new fact is a single completed project, write that project up accurately. Do not create a permanent town page just to give one photograph a home.

• Coverage section: the service is consistent and customers mainly need to confirm the area.
• Project story: a particular completed job supplies the useful detail.
• Service-area page: you have distinct, durable information for customers in that area.
• No new page yet: you cannot serve the area reliably or have nothing useful to add.

Use an evidence test before commissioning another page

Remove the town name from your proposed text and read it again. If the page could describe every other place you cover, ask what the new URL adds. A separate page should earn its place through relevant services, real project context, practical coverage information or other facts that change the reader’s understanding. It does not earn that place through a longer list of nearby postcodes.

There is no magic minimum word count or number of photographs that makes a location page useful. A concise page with specific information can serve a customer better than a long generic essay. Google’s spam policies warn against doorway pages created for similar queries that provide little useful destination content. Do not respond by adding random local history; a paragraph about a town landmark does not explain your trade service.

• Can we explain which work we actually undertake in this area?
• Is there relevant evidence we have permission to publish?
• Are any coverage or process details meaningfully different here?
• Does the page answer a customer question beyond the place name?
• Will somebody maintain these claims as the business changes?

The policy boundary is set out in Google’s guidance on doorway abuse.

A worked structure for a small roofing business

Consider an illustrative roofing firm based in one town and working across several nearby areas. It offers repairs, flat roofing and roofline work, with a handful of permissioned project photographs. Its first useful structure might be a homepage, clear service information, a coverage section, project stories and contact details. It does not automatically need every combination of service and town.

Suppose the firm has completed a flat-roof project in one nearby town. A project story can explain the customer’s problem, the company’s contribution and what the photographs show, then link to the flat-roof service. Later, if the business has enough area-specific information and ongoing work to justify a town page, it can add one and connect those project stories. The sequence follows useful evidence rather than a target page count.

For the broader content brief, use our roofing website checklist.

See how services and evidence can be organised on a website for a roofing firm.

Write a practical brief for a justified area page

Begin with the service and place in ordinary language, then explain the specific information the reader came for. Keep the same business identity and contact details used elsewhere. If you show a project, make the location as precise as is appropriate and permitted; a general area is often sufficient. Do not publish private customer details just to make a local claim look more convincing.

Describe limitations honestly. You may consider larger planned projects across a wider area than small repairs, or need to discuss access before arranging a visit. Only include distinctions that are true for your business. A useful page helps the customer decide whether to enquire; it should not make every possible enquiry appear suitable.

• Opening: what you offer in the area and who it is suitable for.
• Service detail: the relevant scope and what is discussed separately.
• Evidence: an accurate project summary or other substantiated information.
• Coverage: the practical boundary and how uncertain locations are checked.
• Process: what happens after an enquiry and when availability is confirmed.
• Links: relevant service information, useful projects and one clear contact route.

Prepare the supporting evidence with our project story template.

Review existing town pages before adding more

If you already have several similar pages, list their purpose, main query, internal links and actual performance where available. Look for pages that offer the same service, answer the same questions and differ mainly by place name. Do not assume that a page with few clicks is useless: it may be new, unindexed or relevant to a small but valuable audience. Establish the facts before making a change.

Where two pages genuinely duplicate the same intent and content, improving one destination may be more useful than expanding both. Keep important information, plan any necessary redirects and update internal links with someone who understands the site. Do not simply delete URLs that customers or other websites may still use. A canonical tag is not a substitute for deciding what each page is supposed to do.

Keep website coverage separate from Business Profile settings

A website page is not a new physical branch. Publishing a town page does not establish eligibility for another Google Business Profile, and selecting an area in a profile is not the same as building useful information on your website. Keep both representations consistent with the business you actually run. This is particularly important for a sole trader working from home and travelling to customers.

Use the website to explain scope, evidence and the customer journey. Use the profile’s service-area settings to describe genuine coverage under Google’s rules. Do not promise that either action will produce a particular local ranking. Where a marketing supplier suggests a page for every town, ask what useful information each page will contain and how the content will be kept accurate.

For account setup, address visibility and coverage controls, follow our service-area Business Profile guide.

For Google’s own distinction between service-area and hybrid businesses, read the official service-area guidance.

Check the page as a customer before publishing

Open the draft on a phone and follow the route from a service page to the new area page and then to the enquiry step. The business name should remain consistent, coverage should be easy to understand and the next action should work. Check that project captions say what the images actually show. A visitor should not have to decide between several pages claiming to be the main contact point.

Give the page a unique, descriptive title and one main heading, and ask your website provider to check its canonical address, indexability and sitemap inclusion. Confirm that it has a relevant incoming link rather than existing only in a sitemap. After launch, review the questions and suitable enquiries it helps generate alongside verified search data. Useful local information is the aim; a larger page count is not the result you are buying.

For the wider priorities, return to our local SEO basics guide.

If you need a clearer structure for construction services and coverage, see our approach to builder websites.