Brand names are often shared across a business network. The same switchboard, logo and website homepage can appear on several legitimate branch profiles. A cleanup based on those common elements can remove useful local information. Start with the location identity and the customer journey, then decide whether the two records describe one branch, separate branches or an unresolved situation.
| Observed situation | Next review action |
|---|---|
| Different confirmed active branches | Retain both; clarify local details |
| Same confirmed branch | Document the duplicate request |
| Current and former address | Investigate relocation or closure |
| Insufficient evidence | Keep the decision pending |
Build a small comparison record
Place the public URLs side by side with their street addresses, unit numbers, local phone routes, location pages and operating status. Retain the values as they appear rather than immediately normalising away the differences. Mark missing fields explicitly. A blank local number is not proof that two records are identical, just as a shared number is not proof they are different.
Look for branch-specific evidence
Check the business's current branch information and ask the responsible location contact where necessary. A distinct unit, active location page or separate appointment destination may help establish two operating branches. Evaluate those details together. A website can retain a closed branch page, so its existence alone should not settle the question without checking the current arrangement.
Handle former locations separately
An old address beside a current address might represent a relocation rather than an active second branch. Record the business's confirmation of what moved and when. Do not merge records simply to remove confusing information if the platform offers a more appropriate move or closure process. The desired public outcome should reflect the real operation, not just a tidier search result.
Choose an action that fits the evidence
If both records describe separate active branches, keep them and improve any details that blur the distinction. If they describe the same branch, document the candidate duplicate and the intended correction before contacting the directory. If ownership or history is unresolved, retain the issue for review. Do not promise that reviews, images or account access will move automatically.
Inspect the result and preserve the reasoning
After a platform response, revisit both profile URLs. Confirm that valid branches remain findable and that the surviving or corrected record has the right local details. Record why the decision was made, including evidence that rejected a duplicate claim. That explanation helps the next editor avoid repeating a damaging cleanup based on the same shared brand name. Keep a note of evidence that remains unavailable, such as an unanswered question about whether one branch has closed.
Absence of a reply should not be converted into confirmation. When the business later supplies a clear answer, update the comparison record and reassess the specific action. That approach prevents a cleanup task from becoming an automatic purge of the less complete profile. The final public information should preserve each genuine customer location and remove confusion only where the facts support doing so. Use the same branch identifiers in subsequent audits.
Stable references make it easier to recognise a previously reviewed pair, even when logos, contact routes or public profile URLs change later.
Before closing the review
- Addresses compared before naming a duplicate
- Current branch information reviewed
- Former locations considered separately
- Public outcome checked after the request