Google Maps and Mapbox Troubleshooting

Check the common problems and fixes for Google Maps and Mapbox.

Skip to...

• Google Maps Troubleshooting
• Mapbox Troubleshooting

Google Maps

1. “Something went wrong” on the map

This error typically appears when your Store Locator page URL hasn't been authorized in your Google Maps API settings. To fix it, add your store locator URL to the Google Maps API Referrer list. See this article for step-by-step instructions. Additionally, please check:

• The website domains were added correctly (including asterisks and slashes)

• The URL in your browser matches one of the allowed domains

  (for example, if you do not see the myshopify.com     URL, it most likely has not been added to the allowed domains list.)

• The API key you edited matches the key added in StoreLocator → Api Key

👉 You can click Show key in the Google dashboard and compare the last characters.

2. I can’t find my Google Maps API Key

If your key isn’t listed in the dashboard:

1. Check the project selector at the top and try any other listed projects
2. Try signing into any other Google account that may have been used

Unfortunately, Google does not provide a way to identify which email address was used to create a specific API key.

If you’re unable to locate your key, an easy alternative is to switch to default map provider.

Your existing store locations and map settings will continue working with it.

3. "This Map May Not Work Correctly" or "For Development Purposes Only"

This warning — sometimes shown as a darkened map — indicates a billing issue with the Google Maps key connected to your app. Google requires up-to-date billing details to serve maps, even within the free tier.

Common reasons this appears:

• Your Google free trial has ended
• Your billing account hasn't been set up
• Your billing details are outdated

For a full troubleshooting guide, see this article.

Mapbox

1. Map shows up gray, with no roads or imagery behind the pins

This almost always means Mapbox is rejecting the token. Check the following, in order:

• The token was copied in full, with no missing characters or extra spaces at either end
• You copied a token that starts with pk.  — that's a public token. A token starting with sk.  is a secret token and won't work for displaying a map in the browser
• The domain in your token's URL restrictions exactly matches what's in your browser's address bar when the map page is open (no http://  prefix, no trailing path, no typos)
• The token hasn't been deleted or regenerated in the Mapbox dashboard since you added it

2. Browser console shows a 403 error when loading the map

A 403 from Mapbox means the token was recognized but rejected — usually one of two reasons:

• The request came from a domain that isn't in the token's URL restriction list
• The token is missing a required scope (public tokens should have all public scopes enabled by default, so this is rare unless scopes were edited manually)

3. You just added or changed a URL restriction, but it still doesn't work

Browsers and Mapbox's own infrastructure can cache the previous (denied) response for a short time. Try loading the map page in an incognito/private window, or from a different device, before assuming the token itself is the problem.

4. Map fails to load only through the theme editor or a preview link, but works on the live site

This is usually a URL restriction issue, not a broken token — theme preview and editor URLs often come from a different domain than your live storefront. If you need the map to render in those previews too, add shopifypreview.com  and your myshopify.com  domain to the token's URL restrictions, as described in step 7 above.

5. Map area is completely blank, not even gray

This is less common and usually isn't a token problem at all — check your browser console for a Content Security Policy (CSP) error mentioning a blocked image or connection. Some themes or third-party CSP apps restrict which external domains can load resources; if that's the case, *.mapbox.com  needs to be allowed.

If none of the above resolves it, generate a brand-new token in Mapbox (rather than editing the existing one) and update it in the app — this rules out any issue with the token itself.

Do you need help?

If you have any questions or run into issues, please contact us — we’re happy to help.