More threads by Linda Buquet

Linda Buquet

Local Search Expert
Jun 28, 2012
Reaction score
Google just killed Michael Cottam's Local Dupe Finder.

When I say killed it, I mean for the purpose most serious pros used it for.
To discover and LOOK AT duplicate Google+ pages - typically used for ranking troubleshooting.

For anyone unaware of what I'm referring to, here is a post I did that illustrated the power of Michael's Google Local Dupe Finder:
<a href="">GMB Dupe Finder & Spam Hunter - Infinitely Better Than Map Maker</a>

Paul Gordon reported at the forum yesterday:
<a href="">Google Places API now returns a google maps url rather than a google+ url</a>

I did some checking and found a post from Michael announcing the API problem, which affects his tool AND our ability to hunt down duplicate listings.

Michael's post: <a href="">Google Places API Quietly Divorces Google+</a>

Then found a post from Mike Blumenthal about Michael's post and the issue:
<a href="">Google Places API Drops G+ Page in Results</a>

So one more nail in the coffin for dupe hunting.

And one more nail in the coffin for Google+, at least as far as how it relates to Google Local.
G+ in general is still viable, kinda.
One by one are research tools are being crippled or taken away.

Maybe we should all just start calling support and say: "Could you please do duplicate research for me and give me a list of all related G+ L listings for this business, since Google hides them now and we can't easily find them." ;)
Do you pros think Google is doing this intentionally?

Sent from my SM-G900V using Tapatalk
Yes I do Cody.

But not to keep data from us and certainly not to hurt our dupe research. The API team is probably are not even tuned into Michael's tool or our need for dupe research.

But I think they are just doing everything they can to distance Local from Google+.
If they don't want to show the G+ page in search results, why would they want it to be shown on 3rd party sites that use their API.

And I think the main reason they are distancing from G+ PAGES is that they are just taking the data from the page and showing in various ways: In the Knowledge Graph, Local Finder and maps.
Nope it's the same Margaret.

Sorry maybe was not clear enough.

They both still work, the distinction is, they no longer take us to G+ Local pages like before. So you can't see at a glance the description, etc. You just can no longer get to the page.

Even on Pleper (which also pulls from the API, which is what caused the change) it links you to the maps result. NOT the G+ L page as before.
I found a temporary solution for Pleper. The tool became slower, but at least work for now.
How did you get it to go to the G+ L page? That's the issue here. Not whether it works, but whether it takes you to G+ L.
Ooh ooh ooh - he's right.
The link is there again.
So you get both the maps link and the local page link. Thx stankolev!
Awesome, thanks Stan!

So are you saying the API still does not give you the G+ L page, so you are pulling CID from the maps listing then converting that into the G+ L link?
No, API still does not return G+ id/page.

Not exactly convert, the script visit and extract G+ ID, after that with G+ API check if it is verified or not.
Cool Stan. I'm planning to do a new stand alone post tomorrow about your solution.

Login / Register

Already a member?   LOG IN
Not a member yet?   REGISTER

LocalU Event

LocalU - Level Up Your Content Marketing Game with AI

  Promoted Posts

New advertising option: A review of your product or service posted by a Sterling Sky employee. This will also be shared on the Sterling Sky & LSF Twitter accounts, our Facebook group, LinkedIn, and both newsletters. More...
Top Bottom