How to make a store locator
How to make a store locator?
A store locator should answer three things quickly: where the stores are, what's closest, and how to get there. Here's a simple way to build one.
Search, a location list, rich records, and directions work together in the published view.
Define the locator job and required data
A useful store locator lets someone find a relevant branch, understand what it offers, and open directions without decoding the map.
Start with the Store Locator template
The Store Locator template starts with search, list view, directions, clustering, and a Locations group configured. Treat those defaults as a starting point, not as proof that the imported data is ready.
Example: four retail branches
A small first import might use the columns title, address, phone, website, tags, amenities, cta_label, and cta_url. One row can represent each branch.
Test and troubleshoot the locator before publishing
Test the customer tasks, not only whether markers appear.
Common mistakes, limits, and trade-offs
A locator is a maintained business dataset. A polished layout cannot compensate for vague addresses, inaccurate pins, stale hours, or categories customers do not understand.
How it works
Frequently asked questions
Which spreadsheet fields can I import for a store locator?
Should every locator have a list view?
How do directions choose the destination?
Can I measure store visits or purchases?
When should I use Google Sheets instead of CSV?
What should I test before embedding?
Want the quick version?
Start with a template and publish your first map today.