If you imported and your csv file is incorrect, or your header rows are not accurate or have wrong field names, the columns may be misaligned and data field for an address could not import. Check your import message log
Google does not recognize an address. See FAQ post
Some clients have datasets of 200,000 locations, none of which include latitude/longitude coordinates, only U.S. street addresses. Often customers want to know import limitations to including Google’s limit of 2,500 daily requests.
In order to perform bulk location imports with a CSV file you will need to the Power add-on installed. The following constraints can keep the locations from loading or cause slower processing.
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 (Tagalong) category data. If you use this along with pre-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. Continue reading “Importing Large Lists into Store Locator Plus”→