0 comments on “API keys with referer restrictions cannot be used”

API keys with referer restrictions cannot be used

You’ve tried typing in addresses into your WordPress Store Locator Plus® map page but always get “location not found”. Being a tech savvy person you took a look at your browser developer console and notice an “API keys with referer restrictions cannot be used with this API.” in the JavaScript console.

Thankfully our MySLP users don’t have to deal with this sort of thing; but if you are using the self-managed WordPress plugins, read on.

You’ve found the telltale sign that your restricted browser API key has been set in the Store Locator Plus geocoding key field. Coming soon with the WordPress Store Locator Plus 5.0.4 release is a new message that will show in your map results telling you what error codes Google is sending back.

WPSLP Message when a GoogleAPI key has a referer restriction set — likely the result of saving the Browser Key in the Geocoder Key setting in WPSLP.

There are a couple of correct ways to setup your Google API keys for Store Locator Plus

0 comments on “Google Maps API Returning Inaccurate Results”

Google Maps API Returning Inaccurate Results

Google does not openly advertise the fact that they have different location data for different users. However there is good anecdotal evidence an hearsay that Google Maps API returning inaccurate results may be by design.

The evidence is most prevalent in the geocoding of locations. The latitude and longitude Google assigns to different addresses is not “set in stone”. It is an interesting anomaly given the fact that places on earth should not move with regard to their latitude & longitude outside of plate tectonics.

The team at Store Locator Plus® has long held a theory that Google intentionally subverts accurate location data; quite likely to gain competitive advantage for their own products and services.

0 comments on “Google Maps Pricing Changes”

Google Maps Pricing Changes

Google Maps pricing changes have finally gone into effect after multiple instances of Google playing “kick the can down the road”.  The initial changes where supposed to go into effect on June 11th, 2018. Google gave everyone a break from scrambling to implement API keys after announcing that change less than a month before they intended to shut down free access to their maps — they extended the “drop dead” date to July 16th, 2018.

Google Maps pricing change announcement
Google Maps pricing change announcement

Today is July 16th, 2018 — free Google Maps access is a thing of the past.

What that means for Store Locator Plus™

If you are using the WordPress plugins you must now have a Google Maps API key and an attached billing account for that key or your maps will stop appearing on your site.   Users of the My Store Locator Plus™ fully managed locator service do not have to worry about this — we take care of all the licensing for you.

Luckily Google has provided everyone a credit for 2 months of free API access for your maps.   You will need to get an API key and create a Google billing account so they can charge you for their pay-as-you-go service.  Unlike in the past, both small sites and larger sites will start to incur fees under the new Google Maps pricing structure.

New Google Maps Pricing

Every plugin or service that implements Google Maps , which is most of the maps and locators you will find — especially on WordPress, will use the Google Maps JavaScript API.   This is what Google terms “Dynamic Maps” in their new pricing table.     Again, services that include the maps access as part of their monthly subscriptions , like My Store Locator Plus™, take care of these fees for you.

For users of the WordPress plugins you will need to look at the Google Pricing Matrix under “Dynamic Maps”.

  • The base fee is $0.007 for each call to the Google Maps API for the first 100,000 API calls.
  • The fee after 100,000 API calls is $0.0056 per call.

For a typical site where the map is displayed and lists a dozen-or-so locations the fee will roughly correlate to how many visitors the map page receives.    If you have 100 page views of your “locator page” every month you will have approximately 200 API calls for the geocoding request of the user’s location plus the map tiles loading.     100 page views will cost $1.40.

Geocoding location also incurs a fee under the new Google Maps pricing scheme.   If you import 1,000 locations with the Power add on import feature you will record 1,000 geocoding requests in addition to ongoing map views.    1,000 locations will incur a $7.00 charge from Google when they locations are imported.  Again, MySLP covers these fees for you.