How to Fix Duplicate and Outdated Business Listings Without Losing the Right Record
Find every affected record, work out which business or branch each one represents, and choose the right correction route before you create or delete anything. A wrong phone number, a lost login and a duplicate profile are three different problems, and each needs its own remedy.
The goal is a public identity customers can rely on and the business can maintain. A neat spreadsheet of requests sent does not prove the wrong information has gone.
This guide gives you a case-based process, including the evidence to collect and the checks to run after a platform makes its decision.
Classify the problem before you change anything
| What looks wrong | Likely case type | First useful action |
|---|---|---|
| Right business, out-of-date phone or hours | Factual correction | Confirm the current facts and edit through authorised access |
| Right business, nobody can manage it | Access or ownership | Recover the linked account or request authority |
| Two records describe one operation | Possible duplicate | Compare identity, location, history and access before choosing a fix |
| One brand runs two shops | Potentially legitimate branches | Establish how each branch really operates and whether the platform allows it |
| Two independent businesses share a building | Separate identities | Compare names, operators and what each does for customers |
| An old location survives after a move | Relocation or history problem | Show continuity and use the platform's move or correction process |
| A listing names someone else's business | Misidentification or misuse | Keep the evidence and report the specific problem |
A shared phone number, street address or similar name is a clue. None of them proves on its own that two records should be merged.
Build an inventory of the public records
Search for the current name, any old name, current and former phone numbers, addresses and the main website. Check the likely records on each platform your customers use.
Give every public URL its own row. A single row that says "Google" or "directory" hides the fact that two profiles on one platform can be two separate cases.
| Case field | What to record |
|---|---|
| Record reference | The public URL and any visible profile identifier |
| Displayed identity | Name, location or coverage, phone and website |
| Current state | Public, closed, marked duplicate, inaccessible or uncertain |
| Access | The current owner or manager, where you legitimately know it |
| Suspected issue | One short description of the error |
| Intended correction | The exact fact or identity outcome you want |
| Evidence | A protected reference to the supporting material |
| Submitted action | Date, platform route and case or reference number |
| Public recheck | Date, what you saw and what is still wrong |
Do not put sensitive ownership documents in an open worksheet. Store the evidence privately and record a reference that authorised people can follow.
Settle the correct facts independently
Before you edit any public record, confirm what the business actually wants to maintain: the trading name, who has authority, the current operating location, working contact routes and whether the operation continues.
For a move, pin down the date the customer-facing service changed location. For a rebrand, decide whether it is the same continuing business or a different one. For a branch, confirm it really can serve customers the way the record says.
An old profile can hold useful history, and a current profile can hold mistakes. The newest record is not automatically the one to keep.
Keep private enquiries and customer information separate from identity decisions. A justified public merge does not settle who should gain access to old messages or other private records.
Deal with urgent errors first
An exposed home address, a phone that rings the wrong person or directions to a closed building can do harm straight away. Use the correct report or correction route for those, and keep the wider identity case documented alongside.
Make each request specific. Name the exact record and field, the current value, the correct treatment and the evidence. "Please fix everything" gives a reviewer nothing to act on.
If you already hold legitimate management access, use it. If you do not, never try to manufacture access by editing someone else's business into your own identity.
Use Google's separate access and duplicate routes
For an existing verified Google profile controlled by someone else, follow the ownership-request process. Regaining access and resolving a duplicate can be related, but they are not the same thing. Google's ownership guidance
Google treats several situations differently: a duplicate created by mistake, a merge request, and separate eligible businesses wrongly combined. Its guidance also says to update the existing profile after a move instead of creating a new one. A merge can combine reviews while losing review replies, so be sure which record you want to keep before you ask for it. Google's duplicate and ownership guidance
Follow the current route for your exact case. A video tutorial made for another account can skip a step that applies to you, or show wording that has since changed.
Write a correction request a reviewer can follow
A good request explains the identity and the action you want without a long account of the dispute. This fictional template covers a possible duplicate:
These two records appear to represent the same continuing business at the same operating location. Record A is the profile the owner currently manages. Record B repeats the business under an older name. Please review the duplicate relationship. The public links, current trading information and evidence of authority are supplied through the requested channel. We are not asking to combine a separate branch or an independently operated business.
Adjust the wording to fit your evidence. Do not claim authority you are still asking for, and do not attach unrelated customer records to strengthen the case.
For a simple out-of-date phone number, a short factual request is enough. State the wrong number and the contact the owner has approved, and keep the scope of the case in proportion.
Worked case: three similar records, two real operations
This case is fictional. Oak Lane Locksmiths has a workshop and a separately run mobile team under one business identity. A former owner also created a profile for an earlier workshop address. The team finds three public records with overlapping names and phone numbers.
They first work out how the current workshop and the mobile operation really work, and check the platform's profile rules. They do not assume every service deserves its own profile. They also confirm the old workshop no longer receives customers.
The case file identifies the managed identity, the older location record and the extra service record. The owner asks for the right correction to the historical and duplicate information, backed by the actual operating facts. Where separate records are not eligible, they follow the platform's resolution rather than keeping them for extra exposure.
The website is updated to describe the current workshop and the mobile coverage clearly. Public rechecks confirm customers no longer get stale arrival instructions. The team keeps the evidence and case history in case the old details reappear elsewhere.
What matters is the correct identity model. Cutting three records down to one was never the target.
Check the result after the platform responds
A "case closed" message can mean only that a review finished. It does not tell you every related public surface now agrees.
Check the real result:
- Open the affected public URLs and the relevant search result.
- Inspect the name, contact details, address or coverage, status and website.
- Follow any redirect and confirm it lands where you intended.
- Confirm the owner still has the right management access.
- Confirm a legitimate branch or distinct business was not removed.
- Record what happened to any content or relationships that mattered to the case.
- Update the register with the date and any follow-up action.
Look from the customer's side as well as the management side. Save a short note of what is visible instead of relying on memory of what you submitted.
If the same error comes back
Look for where it is coming from. Your website, another maintained profile, an old supplier feed or a conflicting record may still publish it. You may also be looking at a different record, or at a result that has not caught up with an accepted change.
Record each recurrence with its URL and date. Correct the upstream facts you legitimately control and add specific evidence to the case. Sending the same vague report again and again hides the pattern.
If you disagree with a platform's decision, use its review or appeal process. Creating replacement profiles to get around the decision only adds another identity problem.
Prevent the next round
Keep a short business identity register. Give one person responsibility for the current facts, and give the business owner a separate way to recover access.
Trigger a review whenever the phone, address, name, website or operating status changes. Tell suppliers and agencies which public record is the authoritative one before they submit a new one.
For a planned move or rebrand, use the changeover guide. It covers effective dates, old contact routes and website transitions before customers meet stale information.
A correction process lasts when it leaves a clear record of facts, authority, actions and public outcomes. The next person looking after the business should be able to understand it without rebuilding the whole dispute.