How to find businesses near multiple locations in one run
Upload your stores, sites or clients as a list, then search around every row at once: the places found near each, or a count for each location, in one table.
Part of the guide Location intelligence automation
The quickest way to find businesses near multiple locations is to stop searching one address at a time. Put your locations in a table, one row each with a latitude and longitude or an address, and let a single search run around every row. Each business that comes back says which of your locations it was found near and how far away it is, so forty branches take the same effort as one.
Teams ask this when they already have a list: a chain's branches, a distributor's depots, a bank's ATMs, the sites a property fund owns, the offices of key clients. The question is the same each time, "what is around each of these?", and the answer is either a list of the places found or a number for each location. This article shows both, the settings that matter, and where the limits are.
Start from a clean list of your locations
Upload the list on the My data page as a CSV. A row needs a name and a position. Columns called latitude and longitude (or lat and lng) are read on their own; when you only have addresses, the import places each row from its address and city columns. Check a few rows on the map afterwards: a branch dropped in the wrong town will search the wrong town.
- Give each row a short, unique name ("Depot North", "Branch 14"). It is what every result will be labelled with.
- Keep one row per location. If two branches share a building, keep one row, or both will report the same neighbours.
- Add any column you will want later, such as region or manager. It travels with the results.
Two answers to the same question
Nearby places, set to look around each incoming place, can pass on one of two things. Choose before you run, because they lead to different reports.
| The places found | Each incoming place, with counts | |
|---|---|---|
| What goes on | One item per business found | One item per location of yours |
| Labelled with | near (your location) and distance_m | nearby_count, nearby_nearest, nearby_nearest_m |
| Also gives | Name, type, rating, phone, website, chain or not | Average rating, how many are chains, a count per type |
| Good for | Lead lists, partner lists, visit plans | Ranking locations, spotting the crowded and the empty |
| Cost | Searches plus each place passed on | Searches only |
The two ways Nearby places can answer around each of your locations.
If you are not sure, start with counts. It is the cheaper run and it tells you which locations are worth a full list.
Setting the distance and the types
The distance is the circle around each row, from 100 metres (the same street or building) up to 25 km. Pick it from how people reach the place: a few hundred metres for walk-in shops in a dense centre, a few kilometres for a depot that serves its district. One block takes up to 12 types; each type is one search around each location, so three types around 20 branches is 60 searches.
When the circles overlap
Branches close together share neighbours. A cafe 300 metres from two of your shops will be found twice, once near each. That is right for counts, since both shops really do have it nearby, but wrong for a lead list, where it should appear once. Add Remove duplicates after the search, set to the same place, and keep the copy with the nearest location so the rep who owns that shop gets it.
A made-up example
Say a physiotherapy group runs nine clinics around Melbourne and wants to offer staff wellness sessions to gyms and offices nearby. Its table holds the nine clinics with their addresses. The flow reads the table with My data, searches within 1 km of each clinic for gyms, fitness studios and coworking spaces, removes duplicates, and asks xMap LLM to score each place as a partner.
The output is one list, with a column saying which clinic each place is nearest to. The clinic managers filter it to their own name. A second run of the same flow, set to counts instead, gives each clinic a single row: how many gyms are within 1 km and how far the nearest is. Two clinics with almost none nearby are the ones to market differently.
Limits to know
- Up to 100 of your locations and 200 searches in one run. A list of 300 branches is better split into regions, one run each.
- Each search returns up to the 500 nearest places of a type. In a dense centre with a wide circle, the step says there may be more; narrow the distance.
- The places come from xMap's places database, refreshed every month. Places that opened this week may not be there yet.
- Rows without a position pass through without a search. The step tells you how many.
Keeping it running
A one-off list is useful once. The same flow on a Schedule, with Only new after the search, tells each location's manager only about businesses that appeared near them since the last run. That turns a static table into a standing watch around every site you have, which is what most teams wanted in the first place. It is one of the simplest patterns in location intelligence automation.
Questions
Can I search around addresses instead of coordinates?
Yes. Upload the addresses with their city; the import gives each row a position from its address. Rows it cannot place are left without one and are not searched.
Can each location have a different distance?
One block uses one distance. For two sizes, such as small shops and large stores, split the table with a Filter and use two Nearby places blocks.
How do I know which location a business belongs to?
Each business found carries near, the name of your location it was found around, and distance_m, how far it is in metres.
Will the same business be counted for two locations?
In counts, yes, if it is within the distance of both. In a list, add Remove duplicates to keep it once, with the nearest location.
Templates that do this
Read next
More on business and places data · Every article · Templates