Troubleshooting Updated 2026-06-02

Address geocoding failed during import

What this article helps you do

Fix geocoding failures when importing or syncing a large number of stores. Mapstore geocodes addresses to get coordinates for the map. When many addresses fail, use this guide to identify causes and fix them.

Before you start

  • You’ve run a CSV import or Google Sheets sync
  • The import/sync summary shows “X address(es) could not be geocoded” or similar
  • You know whether a Google Maps API key is saved in Settings

Step-by-step instructions

1. Understand when geocoding runs

  • CSV/Sheets import: Bulk geocoding runs when you have a valid Google Maps API key saved in Settings. Without that key, rows missing lat and lng stay ungeocoded.
  • Manual store create/edit: Use the store form’s geocode action or enter coordinates manually if needed.

2. Add lat and lng to your CSV when possible

If your data already has coordinates, include lat and lng columns. Mapstore skips geocoding for rows that already have valid coordinates. This avoids rate limits and failures for those rows.

3. Check address quality

Geocoding fails when addresses are:

  • Incomplete or vague (e.g. “Downtown” or “Store #5”)
  • Misspelled or non-standard
  • Missing city, state, or country
  • Using internal codes instead of street addresses

Improve addresses to full street, city, state/region, and country format.

4. Add a Google Maps API key for bulk imports

If rows are missing coordinates, save and test a Google Maps API key before re-running the import:

  1. Go to Mapstore settings
  2. Add and test your Google API key (see Configure Google API key and required APIs)
  3. Re-run the import

5. Handle Google Geocoding limits

  • OVER_QUERY_LIMIT / quota exceeded: You’ve hit Google’s rate or daily limit. Wait or upgrade your quota. Mapstore adds a small delay between requests to reduce rate limiting.
  • REQUEST_DENIED: API key issue or Geocoding API not enabled. Fix in Google Cloud Console.
  • INVALID_REQUEST: Address format may be wrong. Check for empty or malformed addresses.
  • ZERO_RESULTS: Address not found. Improve the address or add lat/lng manually.

6. Prefer coordinates for large datasets

For larger imports, the most reliable approach is to include lat and lng in the CSV or sheet. That avoids rate limits and removes guesswork from ambiguous addresses.

How to verify it worked

  • Import summary shows fewer or no geocoding failures
  • Stores that were failing now have lat/lng in the store editor
  • Store locator map shows the corrected locations

Common issues and fixes

IssueFix
Many addresses not geocodedAdd lat and lng to your file, or save a valid Google Maps API key before importing again.
”X address(es) could not be geocoded”Improve address quality. Add lat/lng where possible. Check API key and quotas if using Google.
OVER_QUERY_LIMIT / quota exceededWait and retry, or increase Google quota. Reduce import size or add coordinates to CSV.
REQUEST_DENIEDEnable Geocoding API and fix API key. See Configure Google API key and required APIs.
ZERO_RESULTS for specific rowsFix those addresses or add lat/lng manually.
Stores not on map after importStores without lat/lng don’t appear on the map. Geocode them successfully or add coordinates manually.