The Problem With Getting Geodata In and Out of Geokeo
You have an Excel workbook full of addresses — delivery stops, customer locations, field visit logs, prospecting targets. You need latitude and longitude next to each one, or you need a column of GPS coordinates turned back into street addresses, and you need it done in a way that doesn't mean an afternoon of API calls and copy-pasted JSON.
Geokeo is good at converting between addresses and coordinates at scale. But routing that conversion through your workbook is more work than it sounds. The usual flow is: export the column to CSV, hit the API separately, paste the results back in, and pray the row order hasn't shifted.
Below are the four common ways teams handle this. Only the last one scales.
Method 1: CSV Export and Re-Import
The default with Excel. You export the address column to CSV, run it through Geokeo's interface or a script, get the coordinates back in a new file, and VLOOKUP or paste-special them back into the workbook. Then you check whether the row counts match.
For fifty rows, this is manageable. For two hundred — well within Geokeo's 2,500 daily request limit — it becomes a multi-step reconciliation exercise where half your time is spent verifying that row 87 in the output file maps back to the right row in the workbook.
The part that compounds fastest is the address format mismatch. The Geokeo response format rarely lines up cleanly with however Excel imported your CSV, and you end up doing string cleanup before you can even start the geocode.
Method 2: Power Automate
Power Automate has HTTP connectors that can call the Geokeo API. You can build a flow triggered by a new Excel row, call the geocoding endpoint, and write the coordinates back.
Before you go deeper — do you know what a custom connector is in Power Automate? How to configure an HTTP action with query parameters? How to parse a JSON body and pull out nested properties? If those aren't familiar, this is probably not where you want to spend your afternoon. Skip to Method 4.
For those still here: the flow is buildable. You authenticate, configure the HTTP call to the Geokeo endpoint with the address as a query parameter, parse results[0].geometry.location.lat and lng from the response, and write them back to the Excel table.
It processes one row per flow run.
Two hundred addresses means two hundred separate HTTP calls, two hundred flow runs, and a run history that becomes hard to audit when row 118 returns a 429 rate-limit error and the rest write coordinates that are now out of sync with the source rows.
You probably just need the lat/lon columns filled in. You probably have no idea how to parse a nested JSON path out of a Power Automate HTTP response — and you shouldn't have to. So you ask the IT person who built your last flow, and now the geocoding project is waiting on their calendar.
Method 3: The Previous Generation — Connector Add-Ons
Until recently, the standard approach for repeatable geocoding in Excel was a category of add-ins that let you configure a column mapping, point it at a geocoding API, and run it on demand. You tagged your address column, set the output columns, saved the config, and ran it.
That was a real step up from the CSV export cycle. Configs were reusable. Results landed in the right columns without a VLOOKUP.
But the tool had no awareness of your sheet's structure beyond what you'd configured. If you added a tab, renamed a column, or changed the address format from single-line to multi-field, the config broke. And it had no logic for the edge cases: which result to use when Geokeo returns multiple candidates, how to mark rows that failed, how to skip rows already geocoded.
The tool got the data through. Everything that required judgment was still manual.
The Easy Way: Using SheetXAI in Excel
There is a different way entirely. SheetXAI is an AI agent that lives inside your Excel workbook. It reads the workbook, understands what you are looking at, and through its built-in Geokeo integration it can run geocoding and reverse geocoding from the sidebar — no config templates, no flow building, no CSV roundtrip.
Example 1: Geocode 200 delivery addresses into lat/lon columns
For each address in column A of the "Deliveries" sheet, use Geokeo to look up the latitude and longitude. Write the results into columns B and C. If Geokeo returns multiple candidates, use the top-ranked result.
SheetXAI runs the geocoding pass, writes the coordinates row by row, and flags any addresses where Geokeo returned a low-confidence match so you can review before piping the data downstream.
Example 2: Geocode only the rows that don't have coordinates yet
In the "Deliveries" sheet, geocode any row in column A where columns B and C are empty. Skip rows that already have coordinates. Write results to B and C.
The pattern: instead of managing which rows need processing yourself, you describe the condition and SheetXAI handles the filtering inline.
Try It
Get the 7-day free trial of SheetXAI and open any Excel workbook with addresses or GPS coordinates, then ask it to geocode or reverse geocode the column. The Geokeo integration is included in every SheetXAI plan.
More Geokeo + Excel guides
Geocode a Column of Addresses Into Lat/Lon Coordinates in a Google Sheet
Turn a column of raw addresses into latitude and longitude coordinates without leaving your sheet.
Reverse Geocode GPS Coordinates Into Street Addresses in a Google Sheet
Convert a column of lat/lon pairs into readable street addresses directly inside your sheet.