First, inventory every listing for the address and who controls it
Search Maps for the business's current name, any previous names, the current and previous phone numbers and the current and previous addresses, each separately. Record every profile that appears, with its name, address, phone number, review count, whether it is marked as moved or closed, and whether the business manages it. For each one the business does not manage, find out who does: a former owner, an agency, a member of staff, or nobody, which suggests it was generated from outside data.
Then decide which listing is canonical. In most cases it is the one that holds the reviews and history and sits, or can sit, at the correct address with the correct details. Write that decision down before requesting anything, because a merge request for the wrong pair can move reviews in the wrong direction. The citations and NAP guide covers auditing the details across the wider web; this page uses the inventory to answer a narrower question: where did each extra listing come from, and is that source still active.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| A listing at a previous address or under a previous name | Dates of the move or rebrand; whether the old listing is marked moved | Old profile left behind after a move or rebrand | Mark it moved or request a merge into the current profile |
| A listing for one branch managed by an employee's account | Account that owns each profile; staff with access | Profiles created by local staff outside the central account | Transfer ownership to the company account or remove the stray profile |
| A listing nobody created that matches an old directory record | Aggregator and directory records for the business's old details | Aggregator or data-provider errors recreating a listing | Correct the aggregator record, then report the duplicate |
| Two profiles for one branch inside the company's own group | Upload logs and creation dates for the location | Bulk upload creating a second profile for an existing site | Remove the uploaded copy and fix the upload matching |
| A listing held by a former owner or a previous agency | Ownership request history; contracts with past agencies | Former owner's or agency's profile never transferred | Request ownership through Google's process, then merge or close |
Fix, verify and prevent each cause
A listing left behind by a move or rebrand
When a business moves or renames itself, the new details are often added as a new profile while the old one stays live, or the old one is updated while a copy at the previous address survives in Maps.
Fix: decide whether the old listing should be merged into the current one or marked as moved, then use the suggest-an-edit or merge route with evidence that both describe the same business, as the duplicates part of the citations and NAP guide describes; keep the reviews on the surviving profile.
Verify: searches for the old address and the old name lead to the current profile or show the old one as moved.
Prevent: follow the guide's change sequence for every move or rename, which updates the existing profile instead of creating a new one.
Profiles made by local staff
In multi-location businesses, a branch manager who cannot reach the company account sometimes creates a profile from a personal account, and it stays when they leave.
Fix: identify the owning account for every profile, ask the staff member to transfer ownership to the company account or request it through Google's process, and remove the stray profile if the official one already covers the branch, as the bulk management section of the location pages and listings at scale guide recommends.
Verify: every branch has exactly one profile, owned by the company account, with local managers added as managers.
Prevent: give branch staff manager access to their own profile so they have no reason to create another.
Outside data recreating a listing
Data aggregators and directories supply business records to many other sites, and a variant name or old address in those records can produce a second listing in Maps even after one has been removed.
Fix: find the aggregator or directory record that carries the old details, correct it at the source rather than at its copies, make sure the website's location page and its Schema MarkupStructured data vocabulary. state only the current details, and then report the duplicate.
Verify: the duplicate is gone and does not reappear at the next check, and the aggregator shows the canonical record.
Prevent: include the main aggregators in the routine checks of the canonical record, so that an old address is corrected before it spreads again.
A bulk upload that created a second profile
Spreadsheet uploads and connected tools can create a new profile when they fail to match a row to an existing one, for instance because the name or address is formatted differently.
Fix: compare the two profiles for the location, keep the established one, remove the uploaded copy, and correct the formatting in the master record so the next upload matches, as the location pages and listings at scale guide describes for keeping profiles in line with the master record.
Verify: a fresh upload updates the existing profile without creating anything new.
Prevent: test uploads on a few locations first and check the count of profiles before and after every bulk change.
A profile held by a former owner or agency
A business bought from a previous owner, or a profile set up by an agency that has since gone, can remain in an account the business cannot reach, and a new profile created alongside it becomes a duplicate.
Fix: request ownership of the original profile through Google's process, as the claiming step of the Business Profile optimisation tutorial explains, then merge or close the extra listing.
Verify: the business controls the surviving profile and its reviews.
Prevent: write ownership of profiles into agency contracts and into the paperwork of any business sale. When the business cannot manage its only listing at all, the diagnosis for being locked out of a Google Business Profile separates who holds it from a lost login, a limited role or a suspension.
Prevention: one owner account and a listing register
Duplicates come from listings nobody is watching. The prevention is organisational more than technical. Let one company account own every profile, with agencies and branch staff added as managers rather than owners, so profiles never leave with people. Keep a listing register: every profile and important directory listing, its URL, its owner, the details it shows and the date it was last checked. Record the canonical name, address and phone number once, in a master record, and change them there first whenever the business changes. After any move, rebrand, sale, staff change or bulk upload, search Maps by name, phone and address and update the register. Treat local search engine optimisation (SEOImproving visibility in unpaid search results.) as including this housekeeping: a single, complete Business Profile (GBPLocal listing on Google Search and Maps.) per location collects every review and signal, while a duplicate quietly dilutes them.
A bakery with three listings
A bakery that moved across town in 2021 and later became part of a small group finds three listings in Maps. The current one, managed by the group, has 41 reviews. A listing at the old address, unmarked, has 118 reviews and is owned by the founder's personal account. A third, under the old trading name with no owner, matches a record at a national data aggregator. The group asks the founder to transfer the old-address profile, then requests a merge into the current one with photos of the new shopfront and the lease; the 118 reviews move across. It corrects the old trading name at the aggregator and reports the third listing. Six weeks later one listing remains, with 159 reviews, and the register records all three changes.
Common mistakes
Deleting the listing with the reviews. Reporting a duplicate before correcting the aggregator that feeds it. Creating a new profile when the old one is held by someone else. Letting branch staff own profiles. Running bulk uploads without checking the profile count. Removing duplicates once and never checking again.
