504 error on geocoding

Are you saying you could import with an earlier version of SLp and power but cant with version 4.9.14?

A 504 error is a time out error so it is possible that you do not have a correctly formatted csv file and therefore the wheel keeps spinning. Do you see the downloaded csv file in your media library?
How large a file are you importing?

what is your site configuration, php, WP memory , General settings etc? Are you on a shared server? A screenshot of the SLP Plugin information which you can find under the SLP Plugin Info tab is preferable.

Please refer to importing docs
https://docs.storelocatorplus.com/blog/importing-large-lists-into-store-locator-plus/

Refer to additional information about CSV file formats

https://docs.storelocatorplus.com/blog/csv-import-file-header/

https://docs.storelocatorplus.com/blog/q-my-locations-will-not-geocode-why/

https://docs.storelocatorplus.com/blog/power-import-and-wpslp-4-9/

I cannot look at your site since you have not provided your site url, otherwise I would look to see any Google APi errors You can do this your self by using any browser developer tool and inspect , look under Console. If there are no Google MAP API errors then changing the key is not the answer. If you had a key before it will still work now.

Here are some other places to look to assist you.
https://docs.storelocatorplus.com/blog/geocoding-stopped-working/

Thanks for letting us know. I am guessing that your server is timing out if the CSV file isn’t in the right format or getting stuck while trying to geocode. Try “skipping: the geocode and getting the file to import first and check the locations to see if they imported the correct fields. You can then go back and check off under the bulk actions to geocode all.
Other geocoding error messages you may see if they are over the query limit etc.
https://docs.storelocatorplus.com/blog/geocoding-errors/

useful information also about that sl_id column and when to use and when to not use it under the duplicate handling in documentation. If the locations do not exist you do not want the sl_id column. If they do exist , do not make up your own.
How this works

https://docs.storelocatorplus.com/blog/csv-import-duplicates-handling/

The error message above says it all. You have added a referrer restriction , perhaps inadvertently. I believe Google has added some verbiage that is very misleading for the API key. Their new documentation basically tells you to add a restriction when you go to production. that is NOT desired and will break third party plugins that need a Google API key . I am not sure if they are misleading the public on purpose to drive business licenses or not but they have changed the verbiage in the past few months and I find it misleading..

get a new key and REMOVE any restrictions. The restriction makes it so you cant geocode, it restricts servers from talking to Google for geocoding. Which in turn makes it so a visitor to your site cant get the location geocoded either. If you do this as Google tells you: “select HTTP referrers (web sites)” the your web server itself, Versus surfing from their own laptops , phones or PC to access your site.

See STEP 4 under our Getting started guide (I guess I need to make the print larger now that Google has changed their verbiage or actually put STEP 4 in the fore front) it states do NOT add referrer restrictions.
.

https://docs.storelocatorplus.com/blog/getting-started/

I am glad you provided us with that error message