Setting up a Google Maps API key takes about 10 minutes. Once it's done, your store locator will load Google Maps with search, directions, and the "near me" feature your visitors love.

This guide walks you through every step, from creating the key to pasting it into StoreRocket.

You'll need:

Don't want to deal with Google? You can use Mapbox instead. Mapbox is free for up to 50,000 map loads per month and doesn't require a credit card. You can switch your map provider anytime in your Map Provider settings.

Almost certainly not. Google gives you 10,000 free requests per month for each API we use. Each limit is counted separately, so using all your map loads won't eat into your geocoding allowance.

For most StoreRocket users, Google Maps ends up being completely free. Beyond the free tier, Google charges per-service:

Exact pricing can vary by volume, region, and currency. You can set up budget alerts in Google Cloud so there are never any surprises.

Google requires a billing method during setup, but think of it like saving a card on file. No charges unless you go over the limits.

Go to the Google Cloud Console and sign in with your Google account.

If this is your first time, Google may ask you to agree to their terms of service. Just accept and continue.

Every API key lives inside a "project." Think of it as a folder for your API settings.

Make sure your new project is selected in the dropdown before moving on.

This is the step people skip or do halfway, and it's the number one reason maps don't load. Go to APIs & Services > Library and enable each of these:

Optional but recommended: if your project also has Places API (the legacy one, without "New") available in the library, enable it too. Our widget uses Places API (New) by default but falls back to the legacy one if the new one ever fails, so keeping both enabled is the safest setup. New Google Cloud projects may not show the legacy Places API option, and that's fine.

Quick check: After enabling, go to APIs & Services > Enabled APIs and confirm you see all four (or five) listed.

Google won't activate your APIs without a billing account, even though you're unlikely to be charged.

That's it. Your free tier starts immediately.

Don't close this page yet. You need to restrict your key before using it.

An unrestricted API key is a security risk. Anyone who finds it could use it and rack up charges on your account. Takes about a minute to lock it down.

Click Edit API Key (or click the key name in the Credentials list).

Under Application Restrictions:

If Google's UI asks for full URL patterns, use https://*.yourdomain.com/* instead.

Platform-specific additions:

Under API Restrictions:

Select Restrict key and check every API you enabled in Step 3:

Important: Enabling an API in your project (Step 3) is NOT the same as allowing it on your key. Both need to pass. If an API is enabled on the project but NOT checked here, it will still be blocked.

Click Save when done.

Last step! Go to your Map Provider settings in StoreRocket, paste your API key into the Google Maps API Key field, and click Save.

Your store locator should now display Google Maps. Give it a minute to kick in, then check your widget preview.

This is the most common issue and it means one thing: billing isn't set up on your Google Cloud project.

Fix: Go to Google Cloud Billing and make sure a billing account is linked to the project that contains your API key. You need an active billing account with a valid payment method, even though Google almost certainly won't charge you.

Almost always points to one of:

If the map loads fine but the search bar returns no results, and you see an error like this in the browser console:

This API key is not authorized to use this service or API. Places API error: ApiTargetBlockedMapError

This means your API key's API restrictions list is blocking the Places API. It's a different setting from the APIs you enabled on your project.

Fix:

Why both? Our widget uses Places API (New) first but falls back to the legacy one if the new one ever fails. Having both in the allowed list makes that fallback work.

You might see this error in your browser console:

You're calling a legacy API, which is not enabled for your project.

Despite what the message suggests, the fix is to enable the legacy Places API (if your project supports it), not to remove it. Our widget tries to use the new API first, and this error only shows up when the fallback path needs the legacy API but it's not enabled.

Fix:

Keep "Places API (New)" enabled either way.

Your domain isn't in the allowed referrers list for your API key.

Fix: Go to Credentials, click your API key, and check that your referrers include:

The most common mistake is forgetting the *.storerocket.io/* entry (with the dot). You need both *storerocket.io/* and *.storerocket.io/*.

The Maps JavaScript API is not enabled on your Google Cloud project.

Fix: Go to the API Library, search for "Maps JavaScript API", and click Enable.

Your API key is missing, mistyped, or doesn't exist in Google Cloud.

Fix: Go to your Map Provider settings and re-paste the key. Make sure there are no extra spaces or line breaks. If you deleted the key in Google Cloud, create a new one.

You've exceeded the free tier or a budget cap.

Fix: Go to Google Cloud Billing and check your usage. You can raise your quota or increase your spending limit from the same dashboard.

A few things to check:

This is a catch-all error from Google. Check these in order:

Still stuck? Hit us up on live chat and we'll sort it out.