# An address didn’t geocode — Routelink

Source: https://routelink.app/help/troubleshooting/an-address-did-not-geocode/

# An address didn’t geocode

What to do when Routelink can’t place a stop on the map, or places it in the wrong spot.

Geocoding turns a written address into map coordinates. When it fails, the stop can’t be planned, because Routelink doesn’t know where to send the driver.

## Why it fails

Most failures come down to one of these:

*   The address is incomplete — no suburb, city or postal code.
*   It’s internal shorthand rather than an address (“Depot 2”, “the usual place”).
*   The street name exists in several suburbs and there’s nothing to tell them apart.
*   It’s a new development that isn’t in map data yet.
*   Typos, or a unit number written where the street number should be.

## How to fix it

**Complete the address.** Adding the suburb and postal code fixes the large majority of cases. Re-check it and the stop usually resolves.

**Drop the pin yourself.** For places that will never geocode — farm gates, informal addresses, a loading bay round the back — place the stop manually on the map. The coordinates are saved against the stop, so it works from then on.

**Fix it at the source.** If the same bad address arrives every week from your store or ERP, correcting it there saves you doing this again. Otherwise it comes back with the next import.

## Wrong location, not a failure

A stop that geocoded successfully but landed in the wrong place is more dangerous than one that failed, because nothing flags it. Scan the map after importing — a pin sitting far away from the rest of the cluster is almost always a mismatched suburb.

## Still stuck

If an address looks correct and still won’t resolve, send it to us and we’ll take a look at why.

Still stuck? Email [support@routelink.app](mailto:support@routelink.app) and we'll help you out.