How to create location pages in WordPress: three ways, step by step

Short answer

There are three ways. Build them by hand as child pages of an “Areas we serve” page, for a handful of towns. Build a custom post type with custom fields, for a developer-built site with many branches. Or use a plugin that generates a page for each town from one template, and check each before publishing.

A location page is an ordinary WordPress page about the work you do in one place. Making one takes minutes. Making thirty that are each worth reading is the real job, and the method you choose decides how much of that job is copying and how much is writing.

The steps below use the screens in WordPress 7.1. For why location pages matter and how they sit alongside your Google Business Profile, start with multi-location SEO in WordPress. For how many to build, see how many location pages you need.

Which method should you use?

MethodSetting upEach new pageChanging text every page sharesRight for
By hand, as child pages of an “Areas we serve” pageMinutesCopy the last page, then write this town’s partEdit every page, one at a timeA handful of towns, and no developer
Custom post type with custom fieldsA small development job: the post type, the fields and a templateFill in a form, then write the local partEdit the template onceBranches that each have the same set of facts, on a site a developer looks after
A plugin that generates the pagesInstall and set up; Townsmith’s docs allow about fifteen minutes to the first draftsGenerated with the rest; you write the local partChange the template, then update the pagesSeveral services across many towns

In all three, the slow part is the same: finding something true to say about each place. No method writes it for you, and a page without it is what Google’s spam policies describe as a doorway page, however it was built.

Before you start: which parts of the page repeat?

Split the page into two halves on paper before you open WordPress, because each method handles the halves differently.

  • The shared half. What the service involves, how you price it, your guarantees and how to book. It can be the same on every page, and it is what a template or a parent page should carry.
  • The local half. A job you did in that town, how long it takes you to get there, the parking, the age of the houses, the questions people there ask. Nothing else can supply it. Twenty things to write when every town looks the same has ideas.

If you cannot yet write the local half for a town, leave that town off for now and name it in a list on the parent page instead. Writing a page for a town you have not worked in yet covers the honest way to add it later.

Method 1: how do you create location pages by hand?

This is what WordPress supports without any plugin: a parent page called “Areas we serve”, and one child page for each town beneath it.

  1. Check your permalinks. Under Settings, Permalinks, any option except Plain gives pages readable addresses; Post name is the usual choice. With Plain, every page is /?page_id=123 and the parent never appears in the address. On an established site, leave a working setting alone, because changing it changes the address of every post.
  2. Create the parent page. Go to Pages, Add Page, and title it “Areas we serve”. Open the settings sidebar with the Settings button at the top right of the editor, and on the Page tab set the Slug to areas. Write a short introduction: where you are based and how far you travel. Publish it.
  3. Create the first town page. Pages, Add Page again, with a title a searcher would recognise, such as “Plumber in Lewes”. On the Page tab, click the value beside Parent and choose “Areas we serve”, then set the Slug to lewes. The page’s address becomes /areas/lewes/: WordPress’s own help text in that panel explains that child pages inherit their parent’s URL structure.
  4. Write both halves. The shared half once, and the local half for Lewes. Give your phone number exactly as your Business Profile shows it; NAP on your location pages explains why the match matters.
  5. Save it as a draft, then start the next town. The Pages list has no Duplicate action. Instead, open the Options menu (the three dots at the top right of the editor), choose Copy all blocks, start a new page and paste. Rewrite the local half before anything else, then set the Parent and Slug again, because they are not copied.
  6. List the towns on the parent page. Edit “Areas we serve” and add a Page List block. In the block’s settings, set Parent to “Areas we serve”, which shows only its child pages. Each town page appears in the list once it is published, alphabetically unless you give the pages an order.
  7. Link back up. On each town page, link to the parent page and to the page for the service itself, so a visitor can go up a level. Internal linking for local pages shows the pattern.
  8. Compare before you publish. Paste the new page and the one you copied it from into our free duplicate content checker. If most of the text is shared, the local half is not doing its job yet.

To move pages you already have under the new parent, use Quick Edit in the Pages list, which has a Parent menu. Moving a published page changes its address. WordPress keeps no record of a page’s old address; for a missing one it guesses from the last part of the address, which found the right page for a simple move in our test but is not something to rely on. Add a redirect for each page you move. Location page URL structure covers how.

What it costs in time. Setting up takes minutes, and each page costs its writing time. After that the pages are separate copies: when your call-out charge or guarantee changes, you edit every page, and nothing tells you when two pages have drifted into saying the same thing.

When it is right. A handful of towns, each somewhere you can write about from experience, on a site without a developer. It is also a sensible first step for a business testing whether location pages bring in enquiries at all.

Method 2: how do you build location pages with a custom post type?

A custom post type is a second kind of page, with its own menu item, its own address base such as /locations/lewes/ and its own template. Custom fields are labelled boxes on its edit screen, one for each fact every location has: address, phone, opening hours, the team, the towns covered. The template prints each field in the same place on every page, so the layout is defined once and each new location is a form to fill in.

Developers can register a post type in PHP, but most sites use a plugin. Advanced Custom Fields (ACF), with over two million active installs on WordPress.org, is the best known. It adds the fields, and its WordPress.org listing says it can register the post type from its own screens too, so neither part needs code.

  1. Register the post type. In ACF, open Post Types and click Add New. Name it Locations, singular Location. Turn on Hierarchical if you want regions with towns beneath them, the way Pages work; ACF’s documentation notes it is off by default. Set the permalink rewrite to a custom slug such as locations, which becomes the first part of every location’s address.
  2. Create the fields. Under Field Groups, add a group with a field for each fact: address, phone, opening hours, and one larger field for the local paragraph. Set the group’s location rules so it appears on the Location post type.
  3. Build the template. This is the step that usually needs a developer. A classic theme needs a template file for the post type, named single-location.php for a post type called location, that prints each field. In a block theme, the Site Editor offers a “Single item: Location” template; getting field values into it takes a block or a little code, so check your field plugin’s documentation for block themes.
  4. Add each location from the post type’s new menu item: fill in the fields and write the local paragraph.
  5. Give the set a hub. Turn on the post type’s archive and /locations/ lists every location, using your theme’s archive template.

If you already pay for Yoast SEO Premium or Rank Math PRO, their local SEO features include a ready-made Locations post type for branches; see Yoast Local SEO for multiple locations and Rank Math multiple locations before you build your own.

What it costs in time. Setting up is a small development job, and a larger one if the template has to match a designed theme. After that, a new location is a form, and a layout change is one edit to the template. The local paragraph still has to be written for every location.

When it is right. Branches with the same set of facts, where details such as address and opening hours are worth storing once and reusing, in a store locator or in schema. Two cautions. A post type exists only while whatever registers it is active: switch that plugin off and every location address stops loading until it is back, although the content stays in the database. And a template that only prints fields makes the thinnest page there is. If the local paragraph field is empty, every location page is the same page with a different address.

Method 3: how does a location page plugin build them?

Page generators build pages from one template and a list of places. They differ in whether the pages are real WordPress pages or virtual ones served from a table, whether your edits survive an update, and whether anything checks that the pages differ. Programmatic SEO tools compared sets out each tool, and bulk creating pages from a spreadsheet covers the spreadsheet route.

The steps below are for Local Pages Engine, which we make. It builds a page for each service in each town and scores every page against its closest sibling before it goes live.

  1. Install it. Plugins, Add Plugin, search for Townsmith, then install and activate Townsmith Local Pages Engine. Activation opens a setup wizard, and everything it sets can be changed later.
  2. Business profile. Your business name, phone and town. These fill the {{business_name}} and {{phone}} tokens on every page, and the business schema.
  3. Services. Add each service you sell, such as “Boiler repair”. Each can have a page in every town you choose.
  4. Service areas. Paste your towns, one per line. Start with the ones you can write about.
  5. Blueprint. Create the starter blueprint and open it in the block editor. It is an ordinary page with tokens such as {{service}} and {{area}}, variation blocks holding two or more wordings so neighbouring pages are not word for word the same, and a local content slot that generation leaves empty for you. Blueprints and merge tokens lists everything a blueprint can hold.
  6. Generate. Local Pages, Dashboard shows your services against your towns. Tick the combinations you want and press Generate selected. Each becomes a draft page, built in small batches that carry on if you close the tab.
  7. Review the score. Every draft is scored out of 100: up to 45 points for differing from its closest sibling, 35 for local substance and 20 for clearing a thin-content floor. Local Pages, Quality lists every page with its closest sibling and what to fix, and Twin Finder in the editor shows the phrases two pages share. The local slot earns its full 20 points once it holds forty words of your own about the place. The quality score sets out the maths.
  8. Publish what clears the bar. The default bar is 60, and you can move it. Below it, the free plugin warns you before publishing and lists what to fix. Nothing publishes on its own.

The address pattern is chosen once, under Local Pages, Settings: flat, nested under a service hub, area first, or your own pattern under one parent page such as “Areas we serve”. Location page URL structure explains which to pick.

What it costs in time. Townsmith’s getting-started guide allows about fifteen minutes from install to the first scored drafts, most of it spent on the blueprint. The local writing then takes as long as it would by hand. The saving is in upkeep: edit the blueprint and the Sync screen shows what would change on each page before you apply it, and a block you have edited by hand is never overwritten.

When it is right. Several services across several towns, where hand-made pages would run into dozens and drift out of step. It is the wrong tool for a single branch page, for pages that are not about places, and for a site where a developer has already built a locations post type that feeds a store locator.

What does each method tend to miss?

  • By hand: contact details that go stale on some pages and not others, and pages that slide towards copies of each other because each was copied from the last.
  • Custom post type: pages with every field filled in and the local paragraph left empty.
  • Plugin: pages published before anyone wrote the local part, which is the fastest way to build a set of doorway pages.

The local landing page checklist has the full set of checks to run before any page goes live, whichever way it was made.

Where Townsmith fits

Local Pages Engine is method 3, with the checks from the other two built in. Its pages are ordinary WordPress pages rather than a custom post type, so they stay if you switch the plugin off, and its custom URL pattern can put them under your own “Areas we serve” page, as in method 1. The free plugin has no cap on services, towns or pages.

Pro adds what branch networks reach for in method 2: a phone number, address and opening hours for each location, a map on each page, CSV import of services and towns, and a publish gate that holds back pages below the bar. If you have one branch and three towns, method 1 is enough and you do not need either. See features and pricing.

Common questions

Should location pages be child pages or top-level pages?

Either can rank. Child pages give tidy addresses such as /areas/lewes/ and an automatic list on the parent; top-level pages such as /plumber-lewes/ suit a few pages. Pick one and keep it, because moving pages later means redirects.

Can I copy one location page to make the next?

Yes, if you rewrite the local half before you publish. Copying is how near-duplicate sets get made, so compare each new page with the one you copied, and treat a page that still shares most of its text as unfinished.

Do I need a Google Business Profile for each location page?

No. A profile is for each real, staffed location; a page can cover a town you travel to. Business Profile or location pages explains which does which job.

What happens to the pages if I remove the plugin that made them?

It depends on the method. Pages made by hand, or by a generator that saves real pages, stay. A custom post type’s pages stop loading until whatever registered the post type is active again. Virtual pages served by a plugin disappear with it.

Steps checked in WordPress 7.1.4 on 5 November 2026. Written by Stephen Evans, who makes Local Pages Engine.