Google Places Work Around: We currently do not support the location

When working in Places the message that we all dread to hear: We do currently do not support the location is a Google message that instills the fear of god in the most expert of us. In normal situations it will show when a newly created listing has not yet been integrated in the Maps index. Give it 48 hours and the message goes away.

However there has been a more sinister occurrence where it will show up all of the sudden on a long claimed and stable record and it’s the bane of who ever runs into it . Until now it was not known what caused it or how to fix it. It is a message that shows up all too often in the forums raising its head there 3 or 4 times a week.

Fortunately for all concerned, a frequent contributor to the German Places Forums, Spinatmensch has discoved a work around for this most devastating of Google Places Bugs. Here are the instructions as detailed by EHG, another frequent contributor:

1. go into the GooglePlace account containing the “unsuported” location.
2. click the name of the entry to get the URL of the analytics site of the entry opened in a new tab of the browser.
Its URL should look like:[the numbered Place identifier]&hl=en&gl=US
3. Now enter any  content into the field below the line “Share an update on your place page” and hit the button Share” to publish the new content.

I have tested this recently with Andrew Baker whose Places Page was experiencing the problem. This solution may actually recover some of the listings that were edited during the Pending problem as well.

A hat tip and a huge thanks to EHG and Spinatmensch for solving this problem!

Please consider leaving a comment as your input will help me (& everyone else) better understand and learn about local.
Google Places Work Around: We currently do not support the location by

68 thoughts on “Google Places Work Around: We currently do not support the location”

  1. I’ve been fighting this problem with no results, but I just found another piece of the puzzle. Despite making changes and hitting “submit” with each change, I was still getting no where. Then it dawned on me to try using a PC. (I was using my iMac & MacAir with both Safari & Firefox and having no luck!). When I switched over to the PC, it worked on the first change.

    Hope that helps another extremely frustrated person!!!

  2. This rarely works for any Place Page, and likely applies to only the erroneous Place Pages that were affected around the time this article was published.

    1. @Christina
      Firstly the new Google data flow automatically generates this message on every new claim and every reverification. It will last for 24 to 48 hours and then will go away as the index picks up the listing. No amount of poking the record in that situation will do anything. You just have to wait.

      If a listing has been in that state for more than 48 hours then you need to report it via the Google Help File Fix a Problem Troubleshooters.

  3. Mike – It makes me really sad but this fix doesn’t appear to work anymore because the “share an update” is taking a long time to show up on the listing. So I guess for now there is no fix….

  4. Yesterday I changed one category in our clients Google Places listing. They rank near the top usually and this drives them lots of new customer.

    This morning I got the panic phone call that they had been removed from Google. Sure enough it’s this dang “we do not support this location” issue.

    I did this fix about an hour ago, but like comment #63 nothing has changed immediately. Mike, in comment #62 are you saying that for every edit to the listing this might happen, but only for 24-48 hours?

    There is only one tricky thing about this listing – it’s merged with another listing because Google created another listing and they claimed it too. Should I apply this fix to both listings or just the one? Thanks!

    I’ll post an update after 48 hours and hopefully I’ll have some good news.

  5. Good news! After 24 hours this listing is back in it’s proper place atop the search results! We’ll never know if it was the fix that did it, or if it just needed time to come back online after the update.

Leave a Reply to Mike Blumenthal Cancel reply

Your email address will not be published. Required fields are marked *

Comments links could be nofollow free.