Getting Started with Store Locator Plus®

This article covers the first 3 steps (2 if you are using our SaaS product) for getting started with Store Locator Plus®.

Store Locator Plus® makes it easy to add interactive location maps and directories on your website. Our latest technology is included in the Store Locator Plus® Maps and Directories SaaS offering. Some of our customers still prefer the self-managed WordPress plugins available via our Store Locator Plus® for WordPress plugins.

Regardless of which method you prefer, both can be setup quickly and have a fully functional site map or directory listing online in minutes.

Step 1: WordPress Store Locator Plug-in Users Need A Google API Key

SaaS users can skip this step. Store Locator Plus® for WordPress plug-in users need a Google API key to utilize the full features available in the the plugin. WordPress administrators who are self-managing their plugin updates, security, and Google services need to setup a Google API account so they can start billing for map services. 

If you are a subscriber to  Store Locator Plus® – our SaaS directory and locator service, you can ignore this page, we’ve got it covered. Go to our Getting Started guide and move on to Step 2.

For the Store Locator Plus® for WordPress users these instructions are a general guideline. You will need to visit the Google developers page and read their User guide to obtain a new account or update your existing account. Google will bill you directly for your monthly map views and location look-ups.

Geocoding stopped working suddenly

(This page has been updated to reflect the changes in Google Cloud Platform API changes)

Most likely reasons;

  • You moved your site or changed the domain name and did not change your Google Map API key or , as of JUNE 2018 Google API changes, did NOT ADD BILLING TO YOUR API KEY . See Getting Started
  • Check your Google Platform Usage reports
  • A self-imposed usage cap has been exceeded.
  • The provided method of payment is no longer valid (for example, a credit card has expired).
  • You have exceeded the QPS limits for a given API.
  • If you have the Power add-on and are using the import function , your csv file is incorrect, or your header rows are not accurate,  or they have wrong field names, the columns may be misaligned and the data field for an address could not import and/or does not geocode. Check your import message log.
  • Google does not recognize an address. See FAQ post

Store Locator Plus Location Imports troubleshooting

On  June 11, 2018  Google changed their API.  There is now a pay as you go billing requirement. You  will need to reconsider how to import, how often to import , and whether to break the list into smaller chunks , or skip geocoding.  (Or switch to the MYSLP SaaS managed service and choose the Professional or  Enterprise level plan ( restrictions apply) .

In order to perform bulk location imports with a CSV file for the WPSLP plugin you will need the Power add-on installed.  WPSLP Power add-on does not alleviate the need for you to obtain your own Google API key.  MySLP  SaaS users  do not need to obtain their own API keys but will need the Professional level plan or higher to import.

Importing Large Lists into WP Store Locator Plus

Hints for the WordPress Store Locator Plus stand alone, self managed plugin with Power add-on. Import features available with the Power Add-on

Load Data

If checked , use the faster MySQL Load Data method of file processing. Only base plugin data can be loaded, see the approved field name list.

This feature uses the MySQL Load Data command and is much faster than WordPress / PHP CSV file parsing, with the typical Google Geocoding limitations on performance and record counts (if you are not supplying, filling in the latitude/longitude data fields). This feature will only import basic location data. It does not import extended data fields or category data. If you use this along with  per-entered latitude and longitude values you can import 100,000 locations in less than 10 minutes on a basic web server. The column headers must be included in the file and must match the basic fields. You do NOT need to include all columns.