How to Resolve Google Maps API Key Errors and Configure It Correctly for Your Store Locator

Google Maps API key errors can disrupt the functionality of your store locator. This guide explains common errors, their causes, and step-by-step solutions to ensure your API key is configured correctly.

Common Errors and Their Causes

1. API Keys with Referrer Restrictions Cannot Be Used with This API

This error occurs when an API key restricted by HTTP referrers (intended for client-side use) is used for server-side web services like Geocoding or Directions. Server-side APIs require IP address–restricted keys.

2. RefererNotAllowedMapError

This error indicates that your API key’s HTTP referrer restrictions do not include the domain where the map is loading.

3. Import Stopped: Google Maps Key Restrictions Blocked the Process

This error occurs when the allowed domains list for your API key does not include the domains used by the app or site.

4. This API Project Is Not Authorized to Use This API or REQUEST_DENIED

These errors indicate that required APIs are not enabled, or billing is inactive for the Google Cloud project associated with your API key.

Step-by-Step Troubleshooting Guide

Fixing HTTP Referrer Restrictions

Open Google Cloud Console.
Navigate to APIs & Services > Credentials.
Select your API key.
Under Key restrictions, choose HTTP referrers (web sites).
Add your site’s domain(s) as authorized referrers (e.g., https://yourdomain.com/*).
Save changes and reload your store locator.

Fixing Server-Side API Key Restrictions

Open Google Cloud Console.
Navigate to APIs & Services > Credentials.
Select your API key.
Under Key restrictions, choose IP addresses.
Add the IP addresses of your server(s).
Save changes and retry the operation.

Enabling Required APIs

Open Google Cloud Console.
Navigate to APIs & Services > Library.
Enable the following APIs: - Directions API - Geocoding API - Geolocation API - Maps JavaScript API - Places API
Ensure billing is active for the project.

Resolving Unrestricted API Key Warnings

Use separate API keys for client-side and server-side operations.
Secure the keys with proper application and API restrictions.
Monitor usage to prevent unauthorized access.

Best Practices for API Key Management

Use separate API keys for client-side and server-side operations.
Regularly review and update key restrictions to match your app’s requirements.
Enable only the APIs you need and ensure billing is active.
Monitor API usage in Google Cloud Console to detect unauthorized access.

Frequently Asked Questions

What URL Should I Use to Restrict My API Key to My Website?

Restrict the API key to your website’s domain using a wildcard path. For example: https://yourdomain.com/*. This ensures the key only works when called from pages on your site.

Why Did I Receive an Unrestricted API Key Warning After a Bulk Store Upload?

Google sends warnings when API keys are not properly restricted. Bulk operations can trigger these warnings due to active use across client- and server-side requests. Secure the key with proper restrictions to mitigate risks.