Search your company in Arabic and you get one business. Search it in English and Google shows a different panel, a namesake in another country, or nothing at all. That is entity confusion: Google's Knowledge Graph cannot decide that your two names belong to one business, so it splits your facts between two entities, merges you with someone else, or describes the wrong company. AI assistants inherit the confusion, because they lean on the same public signals. The fix is not to abandon one name. It is to declare, consistently and in both scripts, that the two names are one entity.
The short answer: one entity, two declared names — everywhere, in the same form
Choose one canonical English name and one canonical Arabic name, and use that exact pair everywhere: website, Organization schema, Google Business Profile in both languages, social profiles and directories. In schema, one name goes in name and the other in alternateName, with sameAs links tying the entity to its official profiles. Then claim or correct the Knowledge Panel so it reflects the pairing. Google reconciles conflicting sources; your job is to stop giving it conflicts. The steps below run in order.
How to tell you have entity confusion (split panel, merged panel, wrong company, no panel)
Four symptoms cover almost every case. A split panel: each name produces a different panel — or a panel for one name and a plain results list for the other — with facts divided between them. A merged panel: your panel carries another company's description or website, usually a namesake with a similar transliteration. A wrong-company result: your name returns a competitor or an unrelated firm that Google is more confident about.
The fourth symptom is no panel at all, despite years of trading, reviews and press — the signals are so divided between the two names that neither reaches the confidence threshold alone. Our AI visibility audit checklist covers the wider audit; this diagnosis is the specific repair when two scripts are involved.
Why two scripts break Google's confidence: transliteration, word order and legal vs trading names
Transliteration is the first fault line. Arabic names rarely have one settled Latin spelling: the same name can appear with different vowel renderings, with or without "Al-", and with the article attached or separated. Each spelling looks like a candidate for a different entity.
Word order differs too: an Arabic trading name may lead with the family name where the English version leads with a descriptive word, and the legal form on the licence may match neither signage nor website. Add a Business Profile entered in Arabic, social profiles in English, and directories that scraped whichever version they found first, and every source Google checks disagrees in a small but confidence-destroying way.
Step 1 — Choose the canonical pair: one English name, one Arabic name, and the variants you will retire
Start with an inventory: every form of the name in use — licence, signage, website, Business Profile in both languages, social handles, invoices, directories, press. You will usually find four to eight variants. Pick the pair you will defend: the English name customers actually search and the Arabic name on your signage, each spelled one fixed way.
Write the pair down as a rule — capitalisation, spacing, and how the Arabic name is transliterated in Latin characters — and list the variants you are retiring, because later steps work from that list. Keep the legal licence name where required, on invoices and contracts, but stop using it as the public brand name if it differs from the trading pair.
Step 2 — Make your website the entity home both names point to
Google treats your website — in practice the homepage and About page — as the entity home: the source it reconciles other signals against. That page must present both names together as one business. State the pairing plainly on the About page: the business trades as the English name and the Arabic name, at this address, with these contact details. Repeat it in a crawlable footer, not buried in an image.
The About page should also carry the facts a panel displays — what the business does, where it is based, when founded — identically in both versions. If your site runs separate English and Arabic page trees, our guide to SEO for bilingual Arabic and English websites covers the structure; here the point is narrower: both trees describe one entity, with the same facts.
Step 3 — Say both names in code: Organization schema with name, alternateName and sameAs
Schema makes the pairing machine-readable. Add Organization structured data to the homepage: the canonical name in name, the other-script name in alternateName, and still-common transliteration variants as further alternateName entries. Add url, logo, and a sameAs array linking to the profiles unambiguously yours — Business Profile, social accounts, directory or Wikidata entries.
Two details matter. The schema must match the visible page: the names in code should be names a visitor can read on the entity home, not a list invented for search engines. And keep the block identical across both language versions; flipping which name sits in name between versions reintroduces the ambiguity you are removing. If Arabic is the primary trading name it can hold name — what matters is one fixed arrangement.
Step 4 — Align Google Business Profile, social profiles and directories in both languages
Apply the pair outward. On the Google Business Profile, the name must reflect the real-world name customers see on signage — Google's name guidelines are explicit that the profile name is the real-world name, not a keyword string — and the profile should carry it correctly in each language it serves. Our guide to Arabic Google Business Profile optimisation covers the Arabic profile in depth; the entity point is that neither language version carries a retired variant.
Then work through social profiles and the directories from your Step 1 inventory: same pair, same address format, same phone number, same website URL. Start with the sources Google and AI assistants visibly cite — major UAE directories and industry listings — and retire variants in that order.
Step 5 — Claim, suggest edits or request a merge on the Knowledge Panel — and corroborate with third-party sources
With your own sources aligned, address the panel itself. If a panel exists, use Google's claim and verification route for Knowledge Panels to take ownership, then correct the name and facts so the panel shows the canonical pairing. If no claim route is offered, use the panel's feedback and suggest-an-edit options, pointing at your entity home as evidence.
Where two panels exist for one business, the goal is a merge: corrections should make clear both names refer to the same entity, at the same address and website. Panels are rebuilt from corroborating sources, so support the request with independent evidence — press mentions using the pair, a Wikidata item with labels in both languages, and matching directory entries. Corroboration is why this step comes last: a merge request sent while your own website disagrees with itself rarely succeeds.
How to check the fix worked in Google and in AI answers
Check both scripts, in a clean session. Search each name separately: you want one consistent panel per language showing the same website, address and description, with no namesake facts mixed in. Then test the queries customers actually ask — name plus city, name plus service — and confirm the same entity answers all of them.
Then check the AI layer: ask the major AI assistants to describe your business from each name, and compare the answers with your entity home facts. Our article on how to get ChatGPT to recommend your business covers recommendation tactics generally. Expect lag — panels and AI answers update as sources are re-crawled — so re-check monthly, and run your details through our AI visibility check to see how the business currently presents.
Common mistakes that recreate the confusion
The most damaging mistake is rebranding one script only — a new English name launched while the Arabic signage, profile and directories keep the old one manufactures a fresh split. Close behind is keyword-stuffing the Business Profile name with services or locations, which breaches Google's name guidelines and gives the entity a third name.
Other repeat errors: letting a directory listing stand with a retired transliteration because it still brings calls; running social profiles under a nickname that appears nowhere else; schema whose name does not match the visible page. The discipline is simple: one pair, everywhere, and any future name change applied to both scripts in the same week.
FAQ
Why does Google show a different company when I search my business name?
Because Google is more confident about the other company's entity than yours. If your facts are split between an Arabic name and an English name, a namesake with one consistent name can outrank you for your own name until your signals are unified.
Should my Arabic or my English name go in the schema name field?
Use the name your primary market searches as name and the other as alternateName, then keep that arrangement fixed on every page and language version. Consistency matters more than which script leads.
Can I merge two Knowledge Panels for the same business?
Not directly. Align every source to one canonical name pair, claim the correct panel, and use feedback and suggest-an-edit routes to show Google both names are one entity. Corroborating third-party sources make the merge far more likely.
Do I need a Wikipedia or Wikidata entry to fix entity confusion?
No. A Wikipedia article is not required, and many UAE businesses would not meet its notability rules. A sourced Wikidata item with labels in English and Arabic can corroborate the pairing, but your entity home, schema and profiles do most of the work.
How long does it take for a corrected Knowledge Panel to update?
There is no fixed timeline. Panels update as Google re-processes the underlying sources, so changes land over weeks rather than days. Align sources first, submit corrections, and re-check monthly.
Get your entity audited and fixed (CTA)
If your panel is split, merged with a namesake, or missing in one language, diagnosis comes first, because the wrong first step can deepen the split. Our AI visibility service covers entity audits and correction for UAE businesses. Tell us both names as customers use them, and we will map every conflicting signal and reply with an itemised proposal within 24 business hours. WhatsApp: +971 52 595 3174 · hello@webstackrank.com.
