Service area page template: a town page for a business that travels there

Short answer

A town page for a business with no premises there should say where you are really based, how soon you can get there, and something true about working in that town: jobs done there, its housing, its local rules. This template lays that out in WordPress blocks, with no invented local address and a placeholder for every local fact.

Of all location pages, this is the one most likely to turn into a doorway. A firm writes one good town page, copies it for twenty more towns, and ends up with twenty pages that differ by a single word. This template is built the other way round: most of its sections can only be filled from that town, and the parts that repeat are short.

Use it for a town you travel to from somewhere else. If customers come to you at an address in the town, use the branch page template instead. For one service in one town, such as “boiler repair in Lewes”, there is a service-in-town template. All six are in the location page templates gallery.

What goes on a service area town page?

  1. A heading with your trade and the town. “Electrician in Lewes”, matching how people search.
  2. An honest opening. What you do for people there, the town you work from and how far away it is, and how often you are in this town. Saying where you are based is what a reader expects, and it matches a Business Profile that shows a service area rather than a shopfront.
  3. A call button with your one real number. The same number as on every other page and on your Business Profile.
  4. Our work in the town. Two jobs you did there, different in kind, with the street or part of town, what you found and what you did. This is the section nobody else can copy, so it carries the page.
  5. What the town’s homes or businesses tend to need. One true thing about the place that changes your work: the age of the housing, hard water, a conservation area, narrow streets, a council rule. Leave the section out rather than fill it with history from Wikipedia.
  6. What you do there. Your services, each linked to its service-in-town page where one exists, or to the service page where it does not.
  7. Getting to you. How soon you can usually come, which days you are in the town, and whether travel costs extra. If it does not, say so; it is a common worry for anyone outside your home town.
  8. Reviews from that town. Real reviews from customers there, with where they were left. Leave the section out until you have one.
  9. Questions from the town. Start with the travel charge, then add a question only someone there would ask.
  10. Nearby towns and a contact line. Links to the neighbouring town pages and your areas page, then your business name, base town and phone number, written exactly as everywhere else.

Copy the town page template

Press Copy, open a new page, switch to the code editor (Options menu at the top right, or Ctrl+Shift+Alt+M), paste, and switch back. The placeholder inside the work section, “a job you did in [Town] and what was particular about it”, is the one to spend your time on. If your theme shows the page title as the main heading, as most do, move the first heading’s text into the title and delete that block, so the page has one H1.

<!-- wp:heading {"level":1} -->
<h1 class="wp-block-heading">[Trade or main service] in [Town]</h1>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>[What you do for people in [Town], in one sentence.] We are based in [base town], [minutes by road] from [Town], and we [how often you are in [Town]: every week, most days].</p>
<!-- /wp:paragraph -->

<!-- wp:buttons -->
<div class="wp-block-buttons"><!-- wp:button -->
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="tel:[phone, digits only]">Call [phone]</a></div>
<!-- /wp:button --></div>
<!-- /wp:buttons -->

<!-- wp:heading -->
<h2 class="wp-block-heading">Our work in [Town]</h2>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>[a job you did in [Town] and what was particular about it: the street or part of town, what you found, what you did]</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>[a second job in [Town], different in kind from the first]</p>
<!-- /wp:paragraph -->

<!-- wp:heading -->
<h2 class="wp-block-heading">What [Town] [homes or businesses] tend to need</h2>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>[Something true of [Town] that changes the work: the age of the houses, hard water, a conservation area, narrow streets, the local council’s rules. Leave it out if you cannot say anything true.]</p>
<!-- /wp:paragraph -->

<!-- wp:heading -->
<h2 class="wp-block-heading">What we do in [Town]</h2>
<!-- /wp:heading -->

<!-- wp:list -->
<ul class="wp-block-list"><!-- wp:list-item -->
<li><a href="[link to the service page or the service-in-town page]">[Service 1]</a>: [one line on it]</li>
<!-- /wp:list-item -->

<!-- wp:list-item -->
<li><a href="[link]">[Service 2]</a>: [one line on it]</li>
<!-- /wp:list-item --></ul>
<!-- /wp:list -->

<!-- wp:heading -->
<h2 class="wp-block-heading">Getting to you</h2>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>[How soon you can usually get to [Town], which days you are there, and whether travel costs extra. If there is no charge, say so.]</p>
<!-- /wp:paragraph -->

<!-- wp:heading -->
<h2 class="wp-block-heading">What customers in [Town] say</h2>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>[One or two real reviews from customers in [Town], with their first name and where you found the review. If you have none from [Town] yet, leave this section out.]</p>
<!-- /wp:paragraph -->

<!-- wp:heading -->
<h2 class="wp-block-heading">Questions from [Town]</h2>
<!-- /wp:heading -->

<!-- wp:details -->
<details class="wp-block-details"><summary>Do you charge extra to come to [Town]?</summary><!-- wp:paragraph -->
<p>[The true answer, with the amount or the rule]</p>
<!-- /wp:paragraph --></details>
<!-- /wp:details -->

<!-- wp:details -->
<details class="wp-block-details"><summary>[A question only someone in [Town] would ask]</summary><!-- wp:paragraph -->
<p>[Answer]</p>
<!-- /wp:paragraph --></details>
<!-- /wp:details -->

<!-- wp:heading -->
<h2 class="wp-block-heading">Nearby towns we cover</h2>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p><a href="[link]">[Neighbouring town 1]</a>, <a href="[link]">[Neighbouring town 2]</a> and <a href="[link to your areas page]">every area we cover</a>.</p>
<!-- /wp:paragraph -->

<!-- wp:paragraph -->
<p>[Business name], [base town]. Call [phone]. [Your email address]</p>
<!-- /wp:paragraph -->

Every block is a WordPress core block, so it takes your theme’s styles. The two questions sit in details blocks, which open and close without any script.

What must be different on every town page?

  • Must be true of this town: the two jobs, the fact about the place, the days you are there and how soon you can come, the reviews, the town’s own question and the neighbouring towns.
  • Can stay the same: the headings’ pattern, the services list (apart from its links), the call button and the contact line. Those should match on every page.
  • Does not count as different: the town’s name, the drive time on its own, or a population figure. Two pages that differ only in those still read as one page twice.

If you have not worked in a town yet, you have less to say there, and writing a page for a town you have not worked in covers what is honest to put on it. For more material, location page content ideas lists twenty kinds of local detail. Before publishing, paste two finished town pages into the duplicate content checker with the town names set to be ignored; it shows how much of the text the pages share once the names are taken out.

A CSV for planning the towns

Fill one row per town before you write a page. A town whose row stays mostly empty is not ready for a page yet; list it on your areas page instead.

area,type,parent,descriptor,lat,lng,minutes_from_base,days_in_town,local_job_1,local_job_2,local_fact,review,neighbours
East Sussex,county,,,,,,,,,,,
Lewes,town,East Sussex,[fifty words or more on working in Lewes],,,[minutes],[days],[a job you did in Lewes],[a different kind of job in Lewes],[something true of Lewes that changes the work],[a review from a Lewes customer and where it was left],[two neighbouring towns]
Uckfield,town,East Sussex,[fifty words or more on working in Uckfield],,,[minutes],[days],[a job you did in Uckfield],[a different kind of job in Uckfield],[something true of Uckfield that changes the work],[a review from an Uckfield customer and where it was left],[two neighbouring towns]

The first six columns are the ones Local Pages Engine Pro’s area import reads, and it ignores the rest, so the same file can load your towns. The descriptor becomes each town’s description, which the quality score credits once it reaches fifty words. The county row comes first so the towns can name it as their parent. Leave lat and lng empty if you plan to look the towns up on OpenStreetMap from Pro’s settings.

What schema should a town page carry?

Describe the business once, as a LocalBusiness with its real details, and on each town page add a Service whose areaServed names that town and whose provider points to the business. Never give a town page a LocalBusiness with an address in a town where you have no premises. Google’s guidelines for Business Profiles ask a service-area business to hide its address and keep one profile for its base, and your markup should tell the same story.

LocalBusiness schema covers the details, and the local business schema generator writes the business half for a firm that goes to its customers, leaving the street address out and listing the areas served.

Where Townsmith fits

Local Pages Engine builds pages like this from one blueprint. Tokens such as {{area}} and {{phone}} fill in the names and details, variation blocks rotate the shared wording so neighbouring pages are not word-for-word copies, and every page gets an empty local slot for the section only that town can fill, the work section here. The quality score gives full credit for that slot only once it holds forty words about the place, and compares each page with its closest sibling, five words at a time, before it goes live.

It builds a page for each service in each town. If you want one page per town covering every service, the area-first URL pattern gives each town a landing page with its service pages beneath it. The free plugin does all of this with no cap on towns; Pro adds an import that loads the CSV above, a map on each page shading how far you travel, and a publish gate that holds back pages below the bar. See service area pages and the quality score.

Common questions

Should each town page have its own phone number?

Not if every call goes to the same base. One business with one number everywhere is consistent; a different number for every town you visit is the kind of mismatch NAP on your location pages warns about. Give a town its own number only if a real office there answers it.

Should I put my street address on a town page?

Name your base town on every page. Show the street address only if customers can visit it; if they never do, leave it out of the page as you leave it off your Business Profile.

How many town pages should I build?

One for each town where you can fill the work section with real jobs. For most trades that is a handful to start with. How many location pages to build works through the test.

Is a town page the same as a service area page?

Yes, in most people’s usage: a page about a town you cover but are not based in. Service-area pages, done properly covers the strategy behind them.

Checked on 5 November 2026. Written by Stephen Evans, who makes Local Pages Engine.