Two records with similar names can be duplicates, separate branches, related brands or unrelated businesses. Compare the identity details before asking a directory to combine them. When the evidence is incomplete, report a possible duplicate rather than declaring one.
Use this method while browsing the directory. It complements StumbleBees' entry criteria; it does not create a score or a judgment about either business.
Put the two records side by side
Record both listing URLs, not just the names. Then compare the facts each record claims:
| Detail | What to compare | What it does not establish |
|---|---|---|
| Website | Exact destination and any branch page | A shared platform does not mean shared ownership |
| Business description | The service and audience described | Similar services do not prove a duplicate |
| Public location | Whether the records describe different branches | A matching city is not enough |
| Public operator information | Any stated relationship between names | A missing explanation is an unknown |
Do not collect private addresses or personal documents to fill the gaps. Use only relevant public information. The guide to checking a physical business without publishing a home address explains the same boundary for location evidence.
Check for a legitimate difference
A business may have changed its trading name. A second record may describe a shop while the first describes an online service. Separate branches may need distinct details even when the operator is shared.
Ask: would merging these records lose information a reader needs? If the answer might be yes, describe the difference in your request. Do not choose a surviving entry simply because it appears first in results.
A directory's record model determines whether brands, branches or locations get separate entries. If its published rules do not answer that question, make the uncertainty explicit.
Send observations, not accusations
A concise request is easier to check:
Possible duplicate: [first listing URL] and [second listing URL]. Both currently link to the same public business website. I could not establish whether they represent separate branches. Please review the relationship.
This is an illustrative example, not a report about a real listed business. It separates what was observed from what a reviewer must decide.
Use Contact to report the issue. You can also consult Corrections for the published process. No sign-in is needed for a contact message; protected owner-edit tools use a separate account flow.
Keep the correction free and proportionate
StumbleBees' existing promise is that listings, checks and removal are free. Reporting a possible duplicate does not create a subscription or require a promotional purchase.
Ask for the specific record problem to be reviewed. Do not request a preferred ranking, a trust badge or the removal of a competitor because their name resembles yours. A correction should make the record more accurate for readers.
If you are the operator, say which listing represents the current business and link public information explaining any move or name change. Do not claim an ownership check has happened merely because you supplied an address.
Recheck the result
After a change appears, verify that the remaining record still has the correct destination and description. A fresh edit date does not mean every business fact has been checked again.
For that distinction, read what a directory check date can never prove. Accuracy improves when a correction has a clear scope, an observable result and a record of what remains uncertain.
