More threads by LightOfHeaven

LightOfHeaven

Member
Joined
Sep 18, 2025
Messages
28
Reaction score
7
So I got a call from this barbershop, and they've been struggling to rank. When I audited their GMB & site, everything looked phenomenal. They had great on seo and even better off page with amazing backlinks, citations, 250+ reviews, and over 200 photos. They posted daily and even hosted events.

Their business was "Located In" a building whose GMB was marked as permanently closed. The building is 1) not closed, 2) not verified either, and 3) the barbershop is a storefront, so it's technically not located "in the building."


Before :

1786381866443.webp


After : It took me months and multiple requests to have it remove from their GMB, their rankings are now coming back alive and maintaining.

1786382511316.webp



just a reminder to keep thinking outside the box.

Having the "located in" feature is not a bad thing at all especially if it's under a well maintained GMB.

1786383197629.webp


1786383389172.webp
 
Last edited:
What's infuriating about "located in" is that there's no owner control on it whatsoever. We've had several clients move away while leaving these in and every time it's a huge hassle to get rid of them afterward because Google systems are completely useless.
 
This is great thanks for sharing. You mentioned it took multiple requests to get it removed - was it not possible to remove it via the mobile maps interface? Did you delete it there and it it still kept showing?
Would be great to know! Thanks!
 
You can change this field via the API. Through the interface there is little you can do.

You can change the field through the mobile maps interface (that's the work around I know/use). That's how I have previously done it. However I was curious to understand if maybe once the content from the located in field was removed it still showed, so Google had to be contacted. Sounds though this route wasnt tried?!
 
Back
Top Bottom