Google Maps Issues: Index

Link: https://support.brilliantdirectories.com/support/solutions/articles/12000097715

There are 3 errors that can cause momentary interruptions to the Google Maps integration:


  1. Missing an API
  2. Missing HTTP Referrers
  3. Billing Errors


These errors can be identified using the browsers INSPECT TOOL:




The Google Maps Error Alert in the Admin

When Google refuses the Google Maps key, a red Google Maps Error button appears at the top of every admin page. The Google Maps API Status card on the dashboard (under My Website Resources) shows the same result. The card has two rows, because the site uses two separate keys:

  • Website key: used for maps and location search on the website. This key is tested in the browser.
  • Server key: used for member geocoding and imports. This key is tested from the server.


Each row shows its own result, such as Billing problem on your Google project, Google does not recognise this key, Maps JavaScript API is not enabled, or Google Maps key is working. Clicking a row, or the red Google Maps Error button, opens a details window that explains what Google reported and lists numbered fix steps.


Red and Amber Results

  • Red: Google reported a real problem with the key, such as billing turned off, a key Google does not recognise, or a required API that is not enabled. Follow the fix steps in the details window. Only red results raise the Google Maps Error button.
  • Amber (Maps blocked on this admin page): Google refused the key only on the admin address, which is normal when the key is restricted to the website's own domain. Nothing else about the key can be checked from the admin in that case, so the website's own maps and location search should be checked directly. When Google also refuses the key on the website itself, the result turns red (Google refuses your key on your website).
  • Green: Google accepted the key.


What the Details Window Offers

  • Google Cloud Console: opens the Google Cloud Credentials page in a new tab.
  • Test key: tests the website key with Google right now. When Google accepts the key, the Google Maps Error button clears immediately. The server key row has no Test key button; that key is re-checked when an admin page loads.
  • Your Google Maps Settings: the website key, the server key and the Use Places API (New) switch can be edited right in the window. Click Save & test and each key is tested with Google first. A key Google refuses is not saved. Leaving the server key empty keeps the saved server key. The switch is the same setting as Enable New Google Maps Places API in Advanced Settings.


Places API (New) switch.
The Use Places API (New) switch can only be turned on when the key works with Places API (New). If the switch will not turn on, the key most likely does not have Places API (New) enabled in Google Cloud. Enable it as described in Google Maps: Add APIs, wait a few minutes, and try again.


How the Alert Clears

After a fix, the alert clears itself. Admin pages re-check the keys about every 10 minutes and the Google Maps Error button fades once Google accepts the key. Test key or Save & test clears it immediately. A remembered error lasts at most 7 days. Placeholder sites on a directoryup.com address never show the alert, because the keys are checked only on live domains.


Missing an API


STEPS TO FIX: Google Maps Issues: Missing an API




Missing HTTP Referrers


STEPS TO FIX: Google Maps Issues: Editing HTTP Referrers



Billing Errors


STEPS TO FIX: Google Maps Issues: Billing Errors



****  Google requires that all Maps API Keys have a credit card on file for any charges that the API usage may incur. That is due to a change in their policy, beginning on June 11, 2018, Google requires all users to add billing information to their account in order to activate Google Maps API keys.

However, Google gives all users enough free credits each month so that the vast majority of websites will never have to pay anything for this service.  


In fact, with this update Google is actually giving users even more free credit than before.  The only difference is that they now ask for billing information during the setup process rather than after a user consumes all of their free credits.