How to build one business list across several cities, kept apart by city
Put every city in one search, get one business list for multiple cities, and still know which city each row came from. A worked example and the traps.
Part of the guide Location intelligence automation
To build a business list for multiple cities, name all the cities in one Area of interest and run one search across them, rather than one search per city that you then paste together. Every business that comes back carries the name of the city it was found in, so a single list can still be sorted, filtered, counted or sent city by city. You save the copying, and the columns match because they all come from the same search.
This is for sales managers covering a region, franchise teams comparing markets, distributors with depots in several towns, and analysts who are asked the same question about five cities at once. Below: how one search covers several cities, a worked example with real counts for pharmacies in three cities, the mistakes that make a multi-city list lopsided, and an AI employee that keeps the list fresh.
Why one search beats five spreadsheets
When each city is searched on its own, small differences creep in. One person filters out closed places and another does not. One export has a phone column and another calls it telephone. A business near a city edge turns up in both files. By the time the files are merged, nobody is sure the cities were treated the same way.
One search across all the cities avoids that. The same types of place, the same rules and the same fields apply everywhere, and the city becomes just another column. That column is what lets you split the list again whenever you need to.
How several cities sit in one Area of interest
The Area of interest block is where a flow is told where to look. Set it to Cities and pick as many as you need from the list. Each city covers the area the place search gives for it, or about 12 km around its centre when there is none. If you need exact borders, use Draw on a map and draw each one instead.
The data block after it then searches each city separately. Nearby places, which reads xMap's places database, looks from the middle of each city out to its edge (at most 25 km, and up to 8 areas in one run) and keeps only the places inside that city. Every place it passes on has a field called area holding the name of the city it was found in. Map business scan, which reads online maps live, also searches up to 8 parts of the area in a run and drops anything outside it.
A worked example: pharmacies in three cities
Say a medical supplies company wants one list of pharmacies for its account managers in Toronto, London and Sydney. Before building anything, it helps to know how big each city's list will be. xMap's places database, November 2026, gives these counts within 10 km of each centre:
| City | Pharmacies within 10 km | Belong to a chain | Average rating |
|---|---|---|---|
| Toronto | 519 | 119 of the 438 nearest the centre | 4.3 |
| London | 866 | 91 of the 438 nearest the centre | 3.9 |
| Sydney | 346 | 132 of all 346 | 4.1 |
Pharmacies within 10 km of each city centre, xMap's places database, November 2026. For Toronto and London the chain share and rating are worked out from the 438 nearest the centre, not the whole count.
Two things stand out. London has well over twice as many pharmacies as Sydney, so a list that simply keeps the first 300 rows overall would be mostly London. And the chain share differs a lot between cities, so a team that only wants independent pharmacies will lose a different part of each city's list. Both are reasons to keep the city column and to decide limits per city, not for the whole list.
The flow for this team is short. Area of interest holds the three cities. Nearby places looks for pharmacies and passes on the places found. A Filter keeps independents with a phone or website. Sort and limit puts the best rated first. The list goes to a shared sheet, one row per pharmacy, with the area column first so each account manager can filter to their own city.
Mistakes that make a multi-city list lopsided
- One limit for the whole list. Keep the first 100 and the biggest city takes most of them. If each city needs its own top 100, use one flow per city: linked copies make one flow for many cities, each with its own city and the rest shared.
- Expecting every place from one search. One Nearby places search returns the 500 nearest places of a type. London's 866 pharmacies within 10 km will not all fit, and the step says there may be more. Split a big city into districts, each its own area, to reach further.
- Too wide an area. A whole country as one area is searched from its middle, so most of it is missed. Name the cities, or draw the parts you need.
- Merging by name. Chains repeat names across cities. Keep the place id the data gives, and let Remove duplicates work on the same place, not the same name.
- Mixing data that was gathered on different days. A list built from five separate exports taken weeks apart is not one list. One search on one day is.
Let an AI employee keep the list current
A list built once starts to age the day after. An AI employee in xMap Flows can rebuild it on a timetable and send only what changed. One way to set it up:
- Schedule: every Monday at 07:00.
- Area of interest: the cities you cover, picked from the list.
- Nearby places: the types of business you sell to, passing on the places found, each with its area.
- Only new: lets through only businesses this flow has not found before, in any of the cities.
- Sort and limit: best rated first.
- Email to the team, and the Google Sheets app for the full list, with the area column first.
On Monday morning the email lists the new businesses across all your cities, each with its city named, and the sheet gains a row for each. The ready templates New places every morning, only new and Market size of a category across cities start from the same pattern, and My brand against two rivals, city by city shows the city split used for comparison. For the wider picture of how these flows fit together, see location intelligence automation.
Questions
How many cities can one flow search?
Nearby places searches up to 8 areas of an Area of interest in a run, and Map business scan up to 8 parts. For more cities, split them across linked copies of the same flow.
How do I know which city a business came from?
Each place Nearby places finds has an area field with the name of the city or drawn area it was found in. Keep that column when you export or email the list.
Can I get the top 50 in each city rather than overall?
Sort and limit keeps the first ones across the whole list. For a top 50 per city, run one flow per city, which linked copies make easy.
Will a business near two cities appear twice?
Each area keeps only the places inside it. Where areas overlap, a place can be found twice; Remove duplicates keeps one of each by the place itself.
Templates that do this
Read next
More on business and places data · Every article · Templates