How to find and fix duplicate business listings

Finding and fixing duplicate business listings is a core business listing management job: find, match, suppress, and protect reviews, in that order, across Google, Apple, Bing, and the directory network. Duplicates split reviews, confuse hours, and suppress the map pack. Do not delete first. Do not create a "clean" new profile and hope the old one dies. Choose a survivor, merge or report the rest, then re-scan until aggregators catch up.

This is a US field guide, not a theory of local SEO. Start on the BLM homepage for the product view, read what is business listing management? for the category definition, and use Google Business Profile vs. business listings when the team still equates listings with Google alone. For software that queues near-matches, see best business listing management software in 2026, compare listing software, and pricing. For the wider operating playbook (including how duplicates fit a full listings program), see the local listings management guide.

Why do duplicate listings appear in the first place?

Duplicates are usually not vandalism. They are a byproduct of how place data is created in the United States, and why business listing management has to treat listings as a graph rather than a one-time citation blast.

Common sources:

• Staff and franchisees. Someone could not get verification mail, so they created a new Google listing. Someone opened Apple Business Connect and started over.
• Agencies and vendors. A citation blast that used a slightly different name string. A call-tracking number that became a second identity.
• Moves and suite changes. The old address remains a live place. The new address is another. Both rank. Both collect reviews.
• Acquisitions and rebrands. Legal names, DBAs, and old brands coexist. Maps are not a brand guidelines PDF.
• Aggregators. If they hold two versions, directories will too.
• Closed, then reopened. The closed profile was never marked closed. The new one is "more correct" and less trusted.

You will not prevent all of these. You can detect them on a schedule and close them with a consistent rule: one canonical NAP per location, one surviving profile per publisher.

Duplicates hurt in three measurable ways. Reviews split, so social proof looks weaker. Hours and phones diverge, so customers get the wrong one. Ranking signals split, so the map pack prefers a cleaner competitor. Cleanup is reputation work, not janitorial vanity.

How do you find duplicates across Google, Apple, Bing, and the directory network?

In business listing management, you search like a customer and like a matcher. Both.

Customer search. Brand name plus city. Brand name plus neighborhood. Phone number. Address tokens (street number + street). Category plus city if the name is generic. Do this on Google Maps, Apple Maps, Bing, and Yelp at minimum. Note every profile that a reasonable person might tap.

Matcher search. Same phone on a different name. Same address with a legal suffix (LLC, Inc, DBA). Old brand names. Tracking numbers you retired. Former suite numbers. These catch the forks customers do not search for but algorithms still store.

Inventory the IDs. Google place / CID where you can, Apple place ids, Bing ids, Yelp biz urls. Two URLs that look like the same clinic often are not.

For more than a handful of locations, doing this in a browser tab is how duplicates survive. Start a free trial for a snapshot, and the product duplicate radar is the recurring version: near-matches on phone, place id, and name, queued as risk rather than a quarterly spreadsheet.

Record every candidate in one list: publisher, URL or id, NAP as published, review count, claimed/unclaimed, and a gut match score. You cannot suppress what you have not named.

How do you match two listings to the same location?

Matching inside business listing management is a judgment with evidence. Require more than a similar name.

Strong signals (any two together is usually enough):

• Same public phone, or a known tracking number mapped to that phone.
• Same address tokens (number, street, suite) after normalizing Ste/Suite/#.
• Same coordinates within a tight radius and the same brand family.
• Shared photos or overlapping review text that clearly describe one place.

Weak signals (not enough alone): same city and category, same website domain, similar name without address.

Edge cases to handle explicitly:

• Two stores on one block: do not merge. Same brand, different canonical NAP.
• SAB versus storefront: both can be valid. Do not collapse them unless one is a mistake.
• Department listings: a hospital campus with a pharmacy pin is not a duplicate of the hospital.
• Closed vs open: if the business moved, follow the publisher's move/close path. Do not pretend two addresses are one place.

When in doubt, do not suppress. Watch for a week, collect another signal, then decide. Write the rule down so franchisees and agencies cannot invent local exceptions. Canonical name, address format, and phone live in the system of record. How it works puts unify NAP before close duplicates on purpose: you cannot pick a survivor if you have not picked a truth.

How do you suppress a duplicate without losing reviews?

Business listing management suppresses duplicates without orphaning reputation. Reviews live on profiles. Delete the profile, lose the reviews. That is the whole game.

Google. Prefer merge over delete. In GBP, request a merge so reviews and photos can land on the survivor. Unclaimed duplicates can be reported. If you do not own the fork, you still report it; you just cannot merge from the inside. Never create a third listing to "start clean." For GBP-specific ops around verification and ownership, Google My Business management is the companion desk.

Apple Maps. Use Apple Business Connect where you have access; report incorrect places where you do not. Apple's process is slower and less merge-shaped than Google's. Document the surviving place id. Expect lag.

Bing Places. Claim both if possible, then mark the duplicate closed or report it. Bing will happily keep two pins if you only tidy Google.

Yelp and other directories. Claim, then use the site's merge or "this is a duplicate" path. Yelp reviews do not move because you merged Google. Treat each publisher as its own reputation store.

Aggregators. Update or flag the duplicate at the source when you can. Otherwise the fork will republish in a month. Cleanup is a cycle, not a ticket you close forever.

Survivor rules that keep reviews:

• Choose the profile with the strongest review history if its NAP can be corrected to canonical.
• If the high-review profile has the old address and you moved, follow that publisher's move/merge process.
• Screenshot review counts before you file anything.

Agencies should put this in the SLA: merge preferred, delete prohibited without written exception, reviews counted before and after. See business listing management for agencies.

What should you do after the surviving listing is chosen?

Suppression is the middle of the business listing management job, not the end.

• Fix NAP on the survivor so it matches canonical exactly.
• Align hours and categories on the survivor.
• Re-scan the graph in 7, 30, and 90 days. Aggregators recopy. Well-meaning staff recreate.
• Close the source process that created the fork (old citation sheet, franchisee habit).
• Do not blast new citations until the survivor is clean.

For footprint and budget, duplicates change the cleanup line more than the software line. Ten locations with forks are a project; ten clean locations are a subscription. Numbers are in business listing management cost in 2026 and on pricing: Starter at $49/month after trial, Growth at $149/month for up to 25 locations, Enterprise for bulk workflow at scale.

If you only remember four verbs: find, match, suppress, keep reviews. Everything else is publisher-specific paperwork.

FAQ

Should we just delete the listing with fewer reviews?

Almost never. Delete is how reviews disappear and how the remaining profile looks younger than it is. Merge or report as duplicate. Delete only when the profile is spam, a nonexistent place, or a clear policy violation, and still screenshot first.

How long until a suppressed duplicate disappears?

Google merges can show in days; remnants linger. Apple and directories often take weeks. Aggregator-fed copies can take months. Plan the 30- and 90-day re-scan. "We reported it" is not the same as "customers cannot tap it."

Can software close duplicates by itself?

Business listing management software can find and queue them, and in some networks it can file the request. A human still chooses the survivor when reviews are at stake. Good software makes that choice obvious (see duplicate radar on the product page). It should not hide the choice behind a bulk "clean all" button.

We already ran a citation campaign. Why are forks still here?

Because campaigns publish NAP; they do not reconcile identities. If the campaign used a tracking number or a different suite format, it likely created forks. Stop submitting. Inventory, pick survivors, then submit only the canonical record. A fresh listing auditor run is the cheapest way to see whether the campaign helped or multiplied you. For how this fits a full US listings program, return to the local listings management guide.

Sources

Publisher and local-search references checked 2026-09-06. Confirm the live help article before you file a change; product UIs move.

• Google Business Profile Help Center: claim, verify, edit, hours, categories, and troubleshooting for Google listings.
• About Google Business Profile: what a profile includes on Search and Maps.
• Guidelines for representing your business on Google: naming, addresses, and categories Google expects.
• Apple Business Connect: owner tools for places on Apple Maps and related Apple surfaces.
• Bing Places for Business: claim and manage listings that feed Bing and Microsoft map surfaces.
• Bing Places support: listing management help and contact paths.
• Moz: Local SEO: independent overview of local search, listings, and NAP consistency.