Yoast Local SEO with multiple locations: setup, and what it does not build
On this page
Short answer
Yoast Local SEO now comes with Yoast SEO Premium. Switch on multiple locations and it adds a Locations post type at /locations/, one entry per branch with its address, hours, map and schema, plus a store locator and a KML file. Maps need a Google Maps key with billing. It builds no pages for towns without premises.
Yoast Local SEO handles the part of a multi-branch site that works the same way for every branch: the fields, the schema, the map and the search box. Setting it up is mostly form-filling. What it does not do is write each branch page, check that the pages differ from one another, or give you anything for the towns you travel to without a branch, which for many local businesses is most of the area they cover.
How we checked, and a disclosure. The steps below come from Yoast’s own help centre and product pages, read on 5 November 2026, rather than from older versions of the plugin. Townsmith makes Local Pages Engine, which runs alongside Yoast and is covered near the end. If you are still choosing a plugin, start with Yoast Local SEO vs Rank Math or our comparison of local SEO plugins.
What do you need before you start?
- Yoast SEO Premium, AI+ or WooCommerce SEO. Local SEO is no longer sold on its own; Yoast SEO Premium now includes it, with the News SEO and Video SEO plugins, at $118.80 a year excluding VAT. Yoast says one subscription covers one site or domain.
- A Google account with billing turned on, if you want maps, the store locator or coordinates worked out for you. Yoast’s Google Maps key guide says a key cannot be generated without it.
- Each branch’s details exactly as its Business Profile shows them. Name, address, phone and hours should match character for character; NAP on your location pages covers why.
How do you set up multiple locations in Yoast Local SEO?
The order below follows Yoast’s configuration guide for Local SEO.
- Open the settings. Go to Yoast SEO, then Local SEO. There are five tabs: Business info, Opening hours, Maps settings, API key and Advanced settings.
- Turn on multiple locations. On Business info, switch “My business has multiple locations” to Yes and save. Yoast creates a Locations post type, called
wpseo_locationsunder the hood. - Set the primary location and shared details. If every branch is part of the same business, say so, then choose the primary location, usually head office, so the site-wide LocalBusiness schema describes the right place. Shared business info, such as the email address, website and business type, is then inherited by every location unless you override it on one.
- Set opening hours. Either enter shared hours that every location inherits, or turn inheritance off and give each location its own.
- Add the Google Maps key. Paste it on the API key tab. The Maps settings stay locked until you do.
- Check the addresses before you publish. Advanced settings holds the permalinks, by default
/locations/%postname%/for locations and/locations-category/%category-slug%/for location categories. Change them now if you want something else, such as/branches/, because changing them later means redirects. The same tab renames the menu labels and can include locations in your site search. - Add each branch. Under Locations, choose Add New Location. Fill in the Yoast Local SEO box below the editor (business info, opening hours and map settings), then write the page itself.
- Submit the sitemap index. Yoast adds its geo sitemap to
sitemap_index.xmlautomatically, so submitting the index in Search Console covers it.
What does each location page contain?
Yoast’s guide describes each Locations entry as the landing page for that location. The Yoast Local SEO box holds its facts: address, phone, coordinates, business type, the area it serves and its hours. Those feed the schema for that location and the four Yoast blocks, Map, Address, Opening Hours and Store locator, which also exist as shortcodes such as [wpseo_address] and [wpseo_map] for the classic editor.
Everything else on the page is what you write in the editor. A location entry with the blocks and nothing more is an address card with a URL: accurate, but it says nothing about that branch that the next one does not also say.
Three practical points from Yoast’s help on the Locations post type:
- Templates. In a default theme, the
/locations/archive usesarchive.phpand each location usessingle.php. Yoast suggests addingarchive-wpseo_locations.phpandsingle-wpseo_locations.phpto your theme if those look wrong, for instance to show a map of every branch on the archive. - An archive full of blog posts. If
/locations/lists your recent posts instead of your branches, your theme’sarchive.phpis asking for posts directly. Fix the theme, or add the specific template above. - Drafts and maps. A location that is a draft, pending review or private does not appear on maps for visitors, so publish a branch before you expect to see it on one.
One clash to avoid: once Yoast’s post type owns /locations/, don’t also create an ordinary WordPress page called Locations and hang other pages under it. Two different things would claim the same addresses. Give other location-style pages their own base, such as /areas/, or change Yoast’s. Location page URL structure covers the choices.
The store locator, the KML file and the Google Maps key
The store locator is a block called “Yoast SEO: Local Store locator”, the shortcode [wpseo_storelocator] in the classic editor, or a sidebar widget that only appears when multiple locations is switched on. The widget’s default search radius is 10 km. Maps settings control the number of results, the primary country and the label on the route link.
Yoast’s key guide lists four Google APIs and what each one does in the plugin:
| Google API | What Yoast Local SEO uses it for | Needed when |
|---|---|---|
| Maps JavaScript API | Showing a Google map on your site | You show any map |
| Geocoding API | Turning addresses into coordinates, including those the store locator uses | You show a map, use the store locator or let Yoast calculate coordinates |
| Directions API | The route planner | You offer directions |
| Time Zone API | The widget that says whether a branch is open now | You use that widget |
One out-of-date line in Yoast’s guide: it still mentions a recurring $200 monthly credit. On 1 March 2025 Google replaced that credit with a free monthly allowance for each service, so check Google’s pricing for the APIs you switch on, set usage limits, and restrict the key to your domain.
The KML file is the least important part. Yoast says the plugin generates a geo sitemap and adds a KML file to your XML sitemap. Google’s sitemap documentation lists extensions for images, video, news and localised versions of pages, and nothing for locations. The file does no harm, but your LocalBusiness schema and each branch’s Business Profile are what describe the branches to Google.
What does Yoast Local SEO not do?
Yoast is clear about its own scope. Asked on its Local SEO page whether it supports businesses without a physical storefront, Yoast answers that it is “built for businesses with a physical presence”. That leaves several jobs outside it:
- Town pages for areas you travel to. The Area served field is free text that goes into the schema’s
areaServed. It does not create a page for any of those towns, so a plumber covering thirty towns from one yard gets one location and no town pages. - The words on each branch page. The blocks render facts. The paragraphs about that branch, its team, its parking and the jobs it does are yours to write.
- Checking pages against each other. Nothing warns you that two location pages differ only by the town name.
- Holding back a thin page. A location you publish goes live, however little it says.
None of that is a fault in Yoast; it is a schema and on-page plugin doing that job. The risk is in what people do next. With the fields filled in, the quick way to finish is to write one branch page and copy it for the others, changing the town. Google’s spam policies call pages created to rank for similar searches, which lead visitors to something less useful than the real destination, doorway abuse, and correct schema does not change how the copied text reads. Duplicate content across location pages explains how to tell when a set has crossed that line.
What should a service-area business do instead?
- One base, many towns: leave multiple locations off. Describe the business once, with its real address and the areas it covers in Area served.
- Don’t make a location for each town. Every Locations entry is a business at an address. An entry for a town where you have no premises claims a branch that does not exist, which is the inconsistency Business Profile and location pages for a service area warns against.
- Build town pages separately, as ordinary pages, and only for towns where you have something true and specific to say. Service area pages and how many location pages to build cover both.
- Branches and travel areas together: use Yoast’s Locations for the branches customers visit, and town pages for the rest, each pointing to its nearest branch.
Where Townsmith fits
Local Pages Engine builds the pages Yoast Local SEO leaves out: a real WordPress page for each service in each town, from one blueprint, each with an empty slot for something true of that town. It scores every page against its closest sibling, so a set that differs only by the town name shows up before it goes live. The free plugin does that with no cap on towns.
It is built to sit beside Yoast, and we checked the plugin’s code for how. It looks for Yoast each time a page is shown, and while Yoast is active it writes no meta description, breadcrumb markup or business schema of its own; titles are always left to Yoast. It adds only each page’s Service markup, linked to the organisation Yoast already describes, plus FAQ markup for the page’s own questions unless a Yoast FAQ block already covers them. Its quality score reads the meta description you wrote in Yoast’s own field.
Pro adds a phone number, address and opening hours for each branch, used in the page text, and the box where you enter them reminds you that Yoast writes the business schema, so each branch belongs in Yoast’s Locations as well. Pro can also keep pages below your quality bar out of search, adding noindex through Yoast’s own robots output and leaving them out of Yoast’s sitemap. Its maps use OpenStreetMap and need no Google key. See location pages with maps and pricing.
If every page you need is a branch that customers visit, and you already pay for Yoast SEO Premium, Yoast Local SEO on its own may be all you need. Townsmith earns its place when the towns you cover outnumber the branches.
Common questions
Is Yoast Local SEO free?
No. It comes with Yoast SEO Premium, Yoast SEO AI+ and Yoast WooCommerce SEO, and is not sold separately. The free Yoast SEO can describe your organisation but has no locations, store locator or opening hours.
Can I change the /locations/ part of the address?
Yes, under Local SEO, Advanced settings, which sets the permalink for locations and for location categories. Decide before you publish, because changing it later means redirecting every branch page.
Does it work without a Google Maps API key?
The details, schema, address and opening hours do, with coordinates typed in by hand. Maps, the store locator, the route planner, the open-now widget and automatic coordinates need a key, and the key needs a Google account with billing.
Can Yoast Local SEO handle a business that travels to customers?
It can describe the area you serve in your schema, but Yoast says it is built for businesses with a physical presence, and it does not create pages for the towns you cover. Those are ordinary pages you build yourself or with a tool made for them.
Will Local Pages Engine conflict with Yoast Local SEO?
No. While Yoast is active, Local Pages Engine leaves titles, meta descriptions, breadcrumb markup and the business schema to Yoast and adds only each page’s Service and FAQ markup, so there is never a second LocalBusiness on the page.
Checked on 5 November 2026. Written by Stephen Evans, who makes Local Pages Engine.