# What a Store Locator Must Do in Three Taps

> The three taps from "where is my nearest" to a route, what every result must carry, why the list matters more than the map, and what to leave out.

Source: https://storelocatorsoftware.co/what-a-store-locator-must-do/  
Site: StoreLocatorSoftware  
Updated: 12 November 2026

---

Short answerA store locator has one job: get somebody from "where is my nearest" to an address, opening hours and a route, in about three taps. Everything else is decoration. That means results without a form where possible, a list as well as a map, each result carrying the address, hours and distance, and a link through to a page with the detail. If a visitor has to type a postcode before they see anything, you have added a step to the one thing people came for.

What a store locator must do gets decided by its layout, and locators are usually designed as a map with a search box, which is the arrangement that suits the developer rather than the person standing in a car park.

## The three taps

-
### Find the locator
From the main navigation, named something obvious: Shops, Branches, Find us.

-
### See the nearest
Ideally without typing. Offer location access, and show a list of all locations if it is declined.

-
### Get what they need
Address, hours today, phone, directions. Either on the result or one tap further.

Find the locator, see the nearest, get what they need.

## What every result must carry

- **The name of the branch**, in the form customers use.

- **The full address**, as text.

- **Open or closed now**, and today's hours.

- **Distance**, where you know where they are.

- **A phone number** that can be tapped.

- **Directions**, opening the phone's map app.

- **A link** to that location's own page.

That is a lot for a map pin, which is the reason the list matters as much as the map.

## Why the list matters more than the map

A map is a picture that needs panning, zooming and interpretation. A list can be read. It works without JavaScript rendering correctly, it works for screen readers, it works on a slow connection, and it can be crawled, which is the part that decides whether the locations are findable in search at all.

Build the list first and put the map beside it. If something has to be cut on a small screen, the map is the thing to drop.

Seven things, which is why a list beats a map pin.

## Searching without a form

Situation | What should happen |

Location permission granted | Nearest branches, sorted by distance, immediately. |

Permission declined or unavailable | The full list, grouped sensibly by region or town. |

Fewer than about ten locations | Show them all. No search box needed at all. |

Hundreds of locations | Search, plus a browsable list by region. |

Someone types a town | Match on town, postcode, and the branch names people actually use. |

## The things people search for that break locators

Partial postcodes. Town names with different spellings. The name of a shopping centre. The branch's old name. The name of a nearby landmark. A locator that only matches on exact postcodes will fail all six, and the visitor will conclude you have no branch near them.

Test yours with the five things your staff get asked on the phone, which is a far better test set than anything in a specification.

## Search that forgives

Match on everything a person might type: town, postcode, partial postcode, county, the branch name, the shopping centre, and common misspellings of all of them. Then, when there is no match, say what you do have rather than returning nothing. "No branch in Hexham. The nearest are Corbridge, 8 miles, and Prudhoe, 12 miles" keeps the visitor; an empty result loses them.

## What to leave out

A filter panel with eight options nobody uses. A carousel of offers above the results. A newsletter prompt that covers the map. A radius slider, which is a developer's idea of the question rather than a customer's. And a form asking for an email address before showing branches, which is a way of losing most of your visitors.

## Who the locator is actually for

Three kinds of visitor, with different needs. Somebody who already knows the branch and wants the phone number or the hours. Somebody who knows the town and wants to know if you are there. And somebody who is standing nearby and wants the closest one open now. A good locator serves all three from the same page, which is the argument for showing everything rather than hiding it behind a search.

## A worked example

A regional bakery with nine shops replaced a map-and-search-box locator with a page listing all nine, grouped by town, each with address, today's hours, a phone link and a directions link, and a small map underneath.

No search box, because nine locations do not need one. Visits to the page went up because it started appearing in search for the town names it listed, and the phone calls about opening hours fell noticeably.

## Open now, and the trouble it causes

Showing whether a branch is open right now is the most useful thing a locator can do and the easiest to get wrong. It depends on three things being correct: the hours, the time zone, and the exceptions. Bank holidays and seasonal hours are where it fails, and a locator confidently saying "Open now" about a closed shop is worse than one that simply lists the hours.

If you cannot keep exceptions current, show the week’s hours rather than a live status. Honest and static beats confident and wrong, because customers trust the status far more than they trust a table.

## Temporarily closed branches

They should still appear, marked clearly, with a nearby alternative offered. Removing a branch from the locator while it is shut for a refit sends loyal customers to a competitor and generates phone calls asking whether it has closed for good. One line stating the reopening date answers both.

## Accessibility, which is the same work

Real text rather than text in images. Links that say where they go. Tap targets big enough for a thumb. A page that works when the map fails to load. Every one of those also makes the locator faster and more crawlable, which is why the accessible version and the effective version are usually the same build.

## Where it belongs in the site

In the main navigation, not buried under About. Linked from the footer of every page. And linked from each location page back to the locator, so somebody who landed on the wrong branch can find the right one without going back to search.

### A locator built for finding, not for showing a map
Location pages, lists and maps generated from one record, so every branch is findable and current.

[Store locator](/tools/store-locator/) [Location pages](/tools/ai-location-pages/)

## Frequently asked questions

**Q: What should a store locator do?**
Get somebody from "where is my nearest" to an address, hours and a route in about three taps, without making them fill in a form first.

**Q: Should a locator have a search box?**
Only if you have enough locations to need one. Under about ten, show them all. Hundreds need search plus a browsable list by region.

**Q: Is the map or the list more important?**
The list. It can be read, crawled, used by screen readers and loaded on a slow connection. Build it first and put the map beside it.

**Q: What breaks most locators?**
Partial postcodes, alternative town spellings, shopping centre names, old branch names and nearby landmarks. Test with the questions staff get on the phone.

**Q: Where should the locator live?**
In the main navigation, in the footer of every page, and linked from each location page so somebody on the wrong branch can find the right one.

## Sources
The Google documentation behind the guidance on this page. Google changes these pages without notice, so check the date on any figure before you rely on it.

- [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide)
- [Tips to improve your local ranking on Google](https://support.google.com/business/answer/7091)
