Attempting to correct a location takeover - Google couldn't verify your edits

Hi Team,

I am attempting to correct two instances of ‘location takeovers’, however Google is rejecting my edits. I noticed while going back in my timeline that the place names/category had changed while the historical ratings, reviews and photos remain.

I know the original places because I have travelled to these places. For verification, you may read all the reviews and photos updated on the location.

Location #1 (Hyperlink)

Actual Name: Sri Lakshmi Narasimha Swamy Temple

Actual Tamil (Local Language) Name: ஸ்ரீ லக்ஷ்மி நரசிம்ம ஸ்வாமி கோவில்

Actual Category: Hindu Temple

Actual Map Marker: G6M6+5WQ

Google’s Response: Google couldn’t verify your edit

Location # 2 (Hyperlink)

Actual Name: Sri Arasadi Vinayagar Temple

Actual Tamil (Local Language) Name: This is correct. Remains unchanged.

Actual Category: This is correct. Remains unchanged.

Actual Map Marker: This is correct. Remains unchanged.

Google’s Response: Google isn’t accepting edits to this location’s phone number

I have noticed some other ‘location takeover’ instances but I need to scour through my Timeline to identify and attempt to restore them. From my past experience, I have been unsuccessful in correcting them. I am also surprised how Maps allowed edits in the first place but is blocking attempts to correct them.

Please help to update the above two locations to their original names!

Regards,

4 Likes

Hello Everyone, please help with this one! It is a genuine issue I am noticing where people are ‘taking over’ locations that already have lots of positive reviews. They edit such Maps locations and make it their own - company or shop, and they change the Map Marker, Contact etc., I am trying to restore such locations because I review my historical timeline from time to time and I see an unknown place at a location somewhere else from my actual travelling path.

Hi @Madrasi

Thanks for sharing this. You most likely will need help from a kind Google Moderator like @MashaPS to get this fixed.

Cheers

Morten