A Duplicate Merge Is More Than Deleting One Profile

Two listings may each contain information worth keeping. One has the current phone number, the other has the claimed owner account. One holds useful photos, while the other has the correct category and address.

Confirm that the records represent the same business

Compare name history, address, phone, website, location, ownership, and operating context. Shared premises and franchise branches can look similar without being duplicates.

Choose a surviving record deliberately

The primary profile may be the claimed version, the older stable ID, or the record with the strongest data relationships. Document the reason.

Merge fields by accuracy, not by age alone

The newest value is not always correct. Review conflicts before choosing what survives.

Preserve important relationships

Redirect old profile URLs where appropriate, map external identifiers, and transfer legitimate ownership or media instead of simply deleting the secondary record.

Keep an internal merge history

Future imports may try to recreate the retired duplicate. A merge record helps the system recognise it.

A careful merge produces one clearer profile while preserving the useful history and data that existed across both records.

A merge should preserve the strongest record from both profiles

Duplicate cleanup is not simply a matter of deleting one page. One profile may contain the verified phone number while the other has the correct category, owner claim, or useful photos. Before merging, compare the records field by field and decide which values should survive.

Redirect or reference the retired profile where the platform supports it so old links do not lead to a dead end. Claims, reviews, and internal history may need special handling and should not be combined blindly. Record the reason for the merge and the identifiers involved. A safe workflow produces one clearer business record without losing legitimate information that happened to be split across two entries.