WP Store Locator vs Agile Store Locator
On this page
- Which should you choose? The quick verdict
- How do they compare at a glance?
- Do they work without a Google Maps key?
- Which gives each location a better page?
- How do you get your branches in?
- What can visitors search by?
- What do they cost?
- How well are they maintained?
- What about cookie consent?
- Where Townsmith fits
- Common questions
Short answer
Choose WP Store Locator for the larger free version: radius search, category filters and a WordPress post for each location, on OpenStreetMap with no key. Choose Agile Store Locator if you want schema on each store page or will buy its Pro licence anyway, which adds radius search and CSV import. Importing a spreadsheet costs money in both.
These are the two free store locators that give each branch a page of its own, and both run on OpenStreetMap without a Google key. They differ in what the free version includes, where your locations are kept, and how you pay for the rest: WP Store Locator sells add-ons you buy once, Agile Store Locator a yearly or lifetime licence.
How we checked, and a disclosure. On 5 November 2026 we installed both free versions on a clean WordPress 7.1.4 site and read their code, and took paid features, prices and WordPress.org figures from the vendors’ own pages that day. Townsmith does not make a store locator, but its Pro add-on lists the nearest branches on location pages, which we cover at the end. For the other free locators, see store locator plugins for WordPress.
Which should you choose? The quick verdict
- Choose WP Store Locator if you want radius search, category filters and location pages without paying anything, you want each location stored as a WordPress post, or you would rather pay once for add-ons than every year.
- Choose Agile Store Locator if you will pay for Pro anyway and want CSV import, radius search and extra layouts on one licence, or you want schema markup on each store page without adding it yourself.
- Choose neither on its own if your customers do not visit you. A locator finds premises; a business that travels to the towns it serves needs service area pages instead.
How do they compare at a glance?
| WP Store Locator 3.1.1 | Agile Store Locator 1.8.10 | |
|---|---|---|
| Maps without a Google key | OpenStreetMap, the default | MapLibre with OpenStreetMap |
| Other map services | Google Maps, Mapbox, Stadia Maps | Google Maps, Geoapify, Mapbox, MapTiler |
| Address suggestions as you type, with no API key | No | No |
| A page for each location | Yes, with one setting; off in our test until we turned it on | Yes, once you create a detail page and point the store links at it |
| Where locations are kept | WordPress posts | The plugin’s own database tables |
| Schema on location pages (free) | None in its code | On by default |
| Radius search | Free | Pro |
| CSV import | CSV Manager add-on, $39 once for 1 site | Pro, from $49 a year |
| Paid price (as listed) | Add-ons bought once; all three for $49, $99 or $199 | $49, $89 or $129 a year; lifetime $129, $229 or $329 |
| Last updated on WordPress.org | 3 November 2026 | 4 November 2026 |
| Active installs | 40,000+ | 10,000+ |
| Rating | 96/100 from 312 reviews | 98/100 from 59 reviews |
| Support threads resolved, last two months | 12 of 18 | 1 of 1 |
Do they work without a Google Maps key?
Both do, and that is the main reason to pick either over Google-only locators. WP Store Locator has run on OpenStreetMap by default since version 3.0, released on 21 September 2026. Its readme says address searches on OpenStreetMap are geocoded on your server and cached. On those free maps there are no address suggestions as a visitor types, and the directions link opens openstreetmap.org unless you add a free Openrouteservice key to draw the route on your own map. Switching to Google Maps, Mapbox or Stadia Maps later is one setting, and your locations do not need to be entered again.
Agile Store Locator uses MapLibre with OpenStreetMap tiles when you choose Free Maps, and looks addresses up through Nominatim, which finds what the visitor submits but offers no suggestions while they type. Address search can come from Google Places, Geoapify or Mapbox independently of the map you show, so you can keep free map tiles and pay only for the search box.
If you do choose Google, both need your own API key, and Google’s getting-started guide tells you to make sure billing is enabled for the Cloud project the key belongs to.
Which gives each location a better page?
This is the difference that matters for search, because someone searching for your service in a town is shown pages about that town, not a search box. Both plugins can give each location an address of its own, but they build the page differently.
WP Store Locator: each location is a post
Every location is a WordPress post of the plugin’s own type. Turn on Create landing pages? and each one becomes a public page at an address such as /stores/downtown/; the vendor’s local pages documentation calls it the setting most worth turning on. In our test it was off after activation, and the setup wizard in 3.1.1 asks about it in its last step. The page carries the address, contact details, opening hours with an open-now badge, categories, any custom fields, optional social links and the post’s own content, so you can write a proper description of each branch in the editor. We searched the 3.1.1 code and found no schema markup; the vendor lists rich snippets only for a Pro version it has announced but not released.
Agile Store Locator: one page that shows each store
Agile keeps stores in its own database tables rather than as posts. To give them pages, you create one WordPress page containing its [ASL_STORE] shortcode and set the store links to use page slugs, as its store details guide describes; that page then shows whichever store the address names, at URLs like the vendor’s demo, /store-details/perth-mazda-centre-perth/. Each page is assembled from the store’s fields: map, address, hours, contact details, logo and gallery. In the 1.8.10 code, schema markup for the store is written on each of these pages and switched on by default. If you also run a local SEO plugin that describes each branch, check the page with Google’s Rich Results Test so the business is not described twice.
In practice, WP Store Locator’s pages are the more flexible, because each location’s description is ordinary post content written in the WordPress editor. Agile’s are built from set fields, such as the description and gallery, but carry schema without any work. Either way, a page that holds only an address and opening hours is thin: add the team, parking, the services offered at that branch and recent work nearby. Multi-location SEO in WordPress covers what each branch page needs, and NAP on your location pages covers matching each one to its Business Profile.
How do you get your branches in?
One at a time, in both free versions. For a dozen branches that is manageable by hand, and Agile’s free version can duplicate a store in one click, which helps when locations share most details.
For more than that, both charge. WP Store Locator’s CSV Manager add-on is $39 once for one site; it imports and exports CSV files, syncs from Google Sheets or a CSV at a URL, and looks up coordinates for rows that have none. Agile puts CSV import and export, scheduled synchronisation and import automation in Pro, from $49 a year. Agile’s free version has no CSV export either, which matters if you ever leave.
What can visitors search by?
- WP Store Locator, free: address, postcode, city, state, country or store name; radius, maximum results and category filters; the visitor’s own location; search restricted or biased to up to 15 countries; and an option to show the nearest location even when none is in range. Version 3.1.1 can draw the search radius as a circle on the map.
- Agile Store Locator, free: address, postcode, category, the visitor’s own location and nearest store.
- Agile Store Locator, Pro: radius search, a distance slider, country-restricted search, searching within the visible map, a search widget for other pages, and eight locator templates where the free version has one.
Radius search is what lets a visitor ask for branches within ten miles of their postcode. WP Store Locator gives you that free; with Agile it is a reason to buy Pro.
What do they cost?
Both show prices with a dollar sign and no currency code, and both offer a 30-day refund.
- WP Store Locator is free, with three optional add-ons, each bought once: CSV Manager and Statistics from $39, and a Search Widget from $19. The add-on bundle of all three is $49 for one site, $99 for five or $199 for twenty, with lifetime updates and 12 months of support.
- Agile Store Locator Pro is $49 a year for one site, $89 for three or $129 for five, or $129, $229 or $329 once for a lifetime licence, on its pricing page. Every plan has every Pro feature; they differ only in the number of sites.
For one site that needs CSV import, that is $39 once against $49 a year, or $129 for Agile’s lifetime licence. Agile’s money buys more, though: radius search, analytics and the extra templates come with it, where WP Store Locator charges separately for statistics and has radius search free.
How well are they maintained?
Both were updated within days of our check, and both say they are tested up to WordPress 7.1.4. WP Store Locator has been on WordPress.org since 2013 and is the more widely used, with over 40,000 active installs. Its 3.0 release in September 2026 rebuilt much of the plugin, and five updates followed within five weeks; anyone upgrading from 2.x should know that older CSV Manager, Statistics and Search Widget add-ons are switched off until they are updated to 2.0. On WordPress.org, 12 of its 18 support threads from the last two months were marked resolved.
Agile Store Locator has been listed since 2016, has over 10,000 active installs, and has shipped eleven releases in its 1.8 series. It had one support thread in the last two months, resolved. Its rating is slightly higher, from far fewer reviews.
What about cookie consent?
Both load map tiles from outside your site, which a UK or EU site may need to hold back until the visitor agrees. WP Store Locator has a built-in placeholder that keeps the map back until consent, with your own wording, and works with Borlabs Cookie and Complianz; Stadia Maps can be set to use only EU servers. Agile says it offers Google Maps consent options and works with popular consent tools, but does not say whether its Nominatim lookups run from the visitor’s browser or your server.
Where Townsmith fits
Townsmith makes Local Pages Engine, which is not a store locator and has no search box. It builds a page for each service in each town a business serves, from one blueprint, and scores every page against its closest sibling so near-copies are caught before they go live. Its Pro add-on lists the branches nearest each town on that town’s page, with the distance, address, phone number and directions, and pins them on a map drawn with OpenStreetMap and no API key. See location pages with maps.
So the two jobs sit side by side. A locator answers “where is my nearest branch?” for someone already on your site; town pages answer a search for your service in a place, including places with no branch. A network that wants visitors to type a postcode should run WP Store Locator or Agile alongside it. Local Pages Engine for multi-location businesses shows how the pieces fit.
Common questions
Do I need Pro for radius search?
Not in WP Store Locator, where radius, maximum results and category filters are free. In Agile Store Locator, radius search and the distance slider are Pro features.
Can I move my locations from one to the other?
Through CSV, which is paid in both: WP Store Locator’s CSV Manager exports, and Agile Pro imports and exports. Match the columns before you import. The location addresses differ by default, /stores/ in one and the detail page’s slug in the other, so plan redirects from the old addresses before you switch.
What happens to my locations if I deactivate the plugin?
The data stays in your database, but the locator and the location pages need the plugin to be active, in both cases. WP Store Locator’s locations stay as posts; Agile’s stay in its own tables, and its free version has no CSV export.
Do they work with Elementor or Divi?
Both are placed with a shortcode, so they work in any builder that accepts one. Agile’s readme names Elementor, the block editor, Divi and WPBakery. WP Store Locator also has its own blocks for the block editor.
Plugins installed and prices read on 5 November 2026. Written by Stephen Evans, who makes Local Pages Engine.