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.
There are a couple of correct ways to setup your Google API keys for Store Locator Plus
If you have recently ported a WordPress site from another server or from a staging site to a production site and the address lookup in Store Locator Plus is failing — you may have an incomplete port. There are a few simple ways to tell that the WordPress configuration is incorrect. This video for our WordPress folks will help you determine if your “ported configuration” is the culprit.
Thankfully our MySLP users never have to deal with this sort of issue — but for our WordPress users that may have an incorrectly ported site, watch this:
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.