If you have ever searched for your own business on Google Maps and found two (or more) versions of it staring back at you, you already know the damage duplicates do. Reviews that should be stacking on one authoritative profile are split across both, each listing underperforms against a competitor with half your real review count, and customers who tap the wrong card may land on a closed address or old phone number. Duplicates are common after rebrands, ownership transfers, or dual-language Arabic and English entries — and fixing them properly takes less time than most owners expect.
How duplicate Google Business Profiles appear in the GCC
Duplicates rarely appear because of a single mistake. They tend to accumulate through a combination of platform automation and well-intentioned but unsynchronised human actions.
Auto-created listings from Google Maps. Google's data ingestion pipeline pulls business data from third-party directories, government commercial registries, and aggregated user behaviour. If your business appears in a commercial register under a slightly different name or address format than your verified GBP, Google may auto-generate a second unverified listing to capture that data point. In the GCC, municipal address formats — Arabic transliterations of street names, alternative postal codes in Saudi Arabia, and Makani numbers in Dubai — are a particularly common source of auto-generated duplicates because the same physical location can resolve to several textually distinct addresses.
User-suggested edits that create new entries. Any Maps user can suggest a new place. A delivery driver who cannot find your location, a customer who noticed your hours have changed, or a new employee who wanted to help can trigger a new listing suggestion. If the suggestion passes Google's confidence threshold before you spot it, a second profile goes live with whatever partial information the suggester provided.
Employee-created listings without owner approval. In larger Saudi and Emirati operations — hospitality groups, retail chains, clinic networks — multiple staff members may independently attempt to claim or create a GBP. Without a centralised process that designates a single owner account, it is common for the brand to end up with two verified profiles, both carrying the same NAP but sitting in different Google accounts. Neither owner knows the other exists until a routine Maps search reveals both.
Dual-language Arabic and English entries. This is the GCC-specific duplicate pattern that catches the most businesses off guard. When a brand name exists in both Arabic script and Latin characters — a restaurant called 'مطعم الريم' in its trade licence and 'Al Reem Restaurant' in its signage — Google may index both as separate entities. Each can accumulate its own reviews, photos, and user edits. Left unaddressed, the two profiles will slowly diverge on hours, contact details, and category data, eroding trust with both Google and your customers.
Address changes left unmerged. When a business relocates, the correct process is to update the address on the existing verified profile. Many owners instead create a new profile for the new address — often because the update flow is less familiar than the creation flow — and leave the old listing live. The old profile continues to attract reviews from customers who found the old address in their Maps history. In Saudi Arabia, where VAT registration updates require a parallel commercial-address update, the address-change scenario is especially common during post-2020 compliance cycles.
For a foundation-level walkthrough of creating a clean profile before duplicates can form, see the guide on setting up a GBP from scratch in Saudi Arabia.
How to find your duplicate profiles
Discovering duplicates requires checking in three distinct places. Run all three checks before you file any merge requests — you want to know the full scope before you start.
Method 1 — Google Maps search variations. Open Google Maps (not Google Search — Maps surfaces more granular listing data). Search for your business name in English, then search again using your Arabic trade name if you have one. Also search your phone number and your street address. Note every listing that appears. Pay attention to listings marked 'Claimed' versus 'Unclaimed' — unclaimed duplicates are easier to merge because there is no conflicting owner account to coordinate with.
Method 2 — The 'Suggest an edit' flow. Navigate to your primary verified profile on Maps and tap 'Suggest an edit.' In the edit screen, scroll to the 'Remove this place' option and select it. Google will show you any related listings it has already identified as potential duplicates and may prompt you to choose a merge target. This is not the merge process itself, but it is a reliable way to surface duplicate candidates that Maps search alone may have missed, particularly auto-generated listings with slightly different name spellings.
Method 3 — The GBP duplicate tool inside Profile Manager. Log into your Google Business Profile manager at business.google.com. If Google has detected a potential duplicate associated with your verified location, a notification will appear on the profile dashboard — usually phrased as 'We found another listing that may represent your business' or 'Duplicate detected.' Click through the notification to review the candidate. This tool catches duplicates that share a phone number or place ID cluster with your primary profile even when the name differs.
Once you have your full list of duplicates, confirm that each one actually represents your same physical location and business entity before proceeding. A listing that shares your address but belongs to a different business — a co-working space tenant, a previous occupant — should not be merged; it should be reported separately.
The merge process, step by step
Merging is a support-mediated process, not a one-click action inside the GBP dashboard. Here is exactly how it works.
Step 1 — Claim both profiles. You cannot request a merge unless you are the verified owner of both profiles. If the duplicate is unclaimed, claim it through the standard verification process — postcard, phone, or video verification depending on what Google offers for that listing. If the duplicate is claimed by another account (an employee, a former owner, or an agency), you will need to request ownership transfer first through the 'Claim this business' flow and resolve the ownership dispute before proceeding to step two.
Step 2 — Align NAP data. Before filing the merge request, make the Name, Address, and Phone number on both profiles identical. Google's merge algorithm checks for NAP consistency; mismatching data is the primary rejection trigger. If your trade-licence name uses Arabic script, ensure the 'Business name' field on both profiles reflects the same transliteration convention. For Saudi addresses, use the same postal code format — five-digit postal code plus four-digit sub-code — on both entries.
Step 3 — File the merge request via Google Support. From the GBP dashboard, open the Help menu and select 'Contact us.' Choose 'Manage duplicate or fake listings' as your issue category. In the support chat or form, provide: the Place IDs of both profiles (find these by searching the profile name on Maps and opening the 'Share' menu — the Place ID appears in the URL), the reason for the merge (rebrand, address migration, system-created duplicate), and your business registration number if you are in Saudi Arabia, the UAE, or Qatar. A registration number accelerates verification significantly.
Step 4 — Wait and monitor. Google processes most GCC merge requests in five to fourteen business days. You will receive an email notification to the account address associated with your primary profile when the merge is complete. During the waiting period, do not edit either profile's core NAP data — edits during processing can reset the queue. You can continue responding to reviews on both profiles; those responses carry over.
What survives the merge. Reviews from both profiles aggregate; the combined count and recalculated average rating appear on the surviving profile immediately after merge completion. The surviving profile is determined by age — the oldest verified listing wins. NAP data defaults to the primary (older) profile. Photos from the secondary profile are merged into the photo pool but may require re-moderation. Posts and Q&A from the secondary profile do not carry over.
For guidance on which categories to select on your primary profile after the merge, see the deep-dive on GBP categories for Saudi Arabian businesses.
Pitfalls that derail merges or destroy data
The merge process is forgiving if you prepare correctly, but there are four failure modes that catch GCC businesses repeatedly.
Merging while reviews are pending. Google's review pipeline is asynchronous. At any given moment, some reviews submitted to your profile are in a moderation queue before they publish publicly. When a merge is executed, pending reviews are not guaranteed to transfer — they may be silently dropped. Before filing your merge request, scroll through both profiles and flag or respond to any reviews that appear in your notifications feed but have not yet appeared publicly on the listing. Once they publish, they will survive the merge.
Merging profiles with different NAP — the rejection loop. Owners who file a merge request without first aligning NAP data enter a frustrating loop: Google rejects the request, the owner updates the address on one profile, the address update triggers a re-verification wait, and by the time re-verification completes the support ticket has expired and must be re-filed. Avoid this by doing a full NAP audit on both profiles three to five days before you file the merge request, giving address updates time to propagate and verify before the support interaction begins.
Orphan listings after merge. In some cases — particularly when the secondary profile had a different Place ID cluster due to being auto-generated from a third-party data source — the merge completes on Google's backend but a ghost listing continues to appear in Maps for certain users pulling cached data. If your merged profile shows a duplicate in Maps two weeks after the merge confirmation email, re-open the support ticket, reference the original case number, and report the orphan. Google can force-purge the cached listing from its index.
Arabic-English dual-name profiles treated as different entities. This is the most consequential GCC-specific pitfall. When you file a merge request for an Arabic-name profile and an English-name profile, Google Support agents outside the MENA region may initially treat them as two different businesses rather than two language representations of one business. Include your commercial registration number, a photo of your physical signage showing both names, and a brief explanation of the dual-language brand convention in your support ticket. Request escalation to the MENA support tier if the first response treats the two profiles as unrelated.
What to do next
With your profiles merged, three follow-up actions lock in the gains.
First, set a reminder to run the three-part duplicate audit — Maps search variations, Suggest an edit check, and Profile Manager notification review — every ninety days. Google's data ingestion runs continuously; a new duplicate can appear at any time, and catching it early means a simpler claim-and-merge with no accumulated review split.
Second, connect your GBP to a monitoring tool that alerts you when a new edit is suggested on your profile. User-suggested edits are the most common source of new duplicates in the GCC, and catching an erroneous 'new place' suggestion before it reaches Google's confidence threshold means you can reject it rather than having to merge it later.
Third, audit your NAP consistency across the directories and aggregators that feed Google's data pipeline — Yelp, Foursquare, TripAdvisor, and the local GCC equivalents such as OpenSooq and Dubizzle Business. NAP inconsistency in these sources is what triggers auto-generated duplicates in the first place. A clean external data footprint is the best long-term prevention.
Ready to get the rest of your profile working as hard as your reviews? Start with Taqymat's guided GBP onboarding to connect your profile and turn on monitoring in under five minutes.