You have reached the daily allowed geocoding limit, you can read more here.

This is very likely related to Google making a requirement to have an active billing account You can read more about that here.

recently, i’ve the same problem. maybe is this a new rule by google? @mmaydesign have you resolved?

• This reply was modified 6 years, 2 months ago by endriu88rm.

@endriu88rm Google requires an active billing account since last July ( they give you $200 credit a month ). Setting that up should fix it.

@tijmensmit We have billing enabled for this account and are getting the same error when adding a new location. It appears we have the setting for the Geocoding API at ‘Unlimited’ as well. What else do you think the issue could be?

If the issue keeps showing up after enabling billing, then you will have to contact billing support. It sometimes takes a while before changes are processed, or there could be a problem with the credit card details itself.

@tijmensmit

I’m working with billing support and they have responded with the following:

I understand that you have enabled billing. Reports on my end aren’t showing me the errors you are describing for that key. This would tell me that the requests are possibly key-less/unsigned(missing a key= parameter) and/or the request is malformed and truncating the credential parameter.

Kindly, would you be able to produce a query that reproduces this issue? I’d like to see how the request is formed to be sure the key= parameter is not truncated by a character that is not properly URL encoded.

Would there be a way I can provide the key= parameter information from the plugin?

• This reply was modified 6 years, 1 month ago by John Scrivner.

Ah yeah, that could be a good reason for it to not work as well.

If you open the store locator page in your favorite browser, then do ctrl + u ( view source ) and search for ‘https://maps.google.com/maps/api/js’. Then look for the key= part in the URL. Is it there?

@tijmensmit

I do see it on the live site where we are using the WP Store locator, but not while in the WordPress Admin. To be clear, I viewed the source while logged into the site and selected the store I want to publish and did a search for ‘maps.google.com/maps/api/js’.

Again, I did find it on the site where the store locator is viewed publicly, but not sure how that would help Google determine the issue of adding a new location since they have access to the API key. I got the impression from Google Support that they would be able to make a determination as to what the issue based off the key parameter information from the time of submitting the new location.

I will provide what I found on the live site and see what they respond with.

New locations are created with a server key in the background with PHP, this is not something you can just check. But often the same ( limit reached ) error shows up on the front-end when you make a search if there’s a billing issue.

It does show that error in the browser console on the front-end?

I have the same problem.
How can I fix it?

I’ve seen that this post mark as Resolved.

@omritk1 this post contains the answers.

once i activated the billing and sorted out some issues with connected to the correct billing account, the issue was fixed.

I have found a way to fix it…
What I should do is to get the Latitude & Longitude by pressing the preview location after adding the address.

Of course, I needed to set building info at Google.

I too was able to resolve this by entering the Latitude & Longitude. To get this I entered the address in maps.google.com and copied the first set of numbers after the @ symbol for the latitude and the second set for the longitude:

https://www.google.com/maps/place/London,+UK/@51.5285582,-0.2416795

I hope that helps.

Thanks!

• This reply was modified 6 years, 1 month ago by John Scrivner.

Sane problem. Active billing account, did that means Google now take payment for the service? :/