A Google map that will not behave is nearly always the key rather than the app. Go through these in order and stop when it starts working.
1. Check the key is the right one
Compare what is in Settings → Appearance, on the Google tab, with the key in your Google Cloud Console. A key copied with a trailing space, or from the wrong project, looks identical at a glance.
2. Enable all three APIs
In the Google Cloud Console, under APIs & Services, all three of these have to be enabled on the project the key belongs to:
Maps JavaScript API, which draws the map
Places API, which powers the address suggestions
Geocoding API, which turns a search into a point on the map
If the button on one of them reads Enable rather than Disable, it is off. Missing one of these is the usual reason a map draws fine but search returns nothing.
3. Check the referrer restriction
A new key has no restrictions and works. If you added HTTP referrer restrictions, this address has to be on the list:
https://sl-widget.proguscommerce.com/mainYour own shop domain on its own is not enough. The locator runs in an iframe served from our servers, so that is the referrer Google sees.
4. Check billing
Google Maps APIs need a billing account on the project, even inside the free allowance. If the map shows a BillingNotEnabledMapError, go straight to the article about that error, which walks through fixing it.
5. Check quotas and the browser console
Google reports usage per API in the Cloud Console, so you can see whether you have run into a limit. And open your locator page with the browser console open: Google writes the real reason there, usually as a named error you can search for.
6. Ask us
If none of that does it, tell us in the chat what the console says and we will look. You can also switch the map to one of the providers that needs no key at all, which gets your locator working again while you sort the key out.
Stuck on any of this? Open the chat in the bottom right corner of the app and we will help you set it up.