Bilingual Website in Arabic and English: Why Yours Loses Customers

Most of your potential customers in Egypt and Saudi Arabia search Google in Arabic. If your site has no real Arabic version — one Google reads, not just the browser — you are absent from the larger market, however beautiful the English site is. The reverse holds for companies selling to Gulf enterprises: English builds trust with multinational teams.

A bilingual website is not decoration or a translate button; it multiplies the market you can reach. But the gap between a bilingual site that brings customers and one that merely looks bilingual is enormous, and it is all execution: URL structure, what Google sees in the page source, the quality of the Arabic, and consistency from landing page to checkout.

This guide is for business owners, not developers. At Jad Digital we have built Arabic-English sites for years and see the same failures repeatedly. We cover the Arabic search opportunity, what genuine localisation means, bilingual technical SEO in plain language, the common mistakes, content strategy per language, and how Saudi and Egyptian audiences differ — with a checklist you can run today.

Search in Arabic for a web design company, an inventory system or an online store and you find enormous monthly volume across Egypt and the Gulf, while the number of serious Arabic pages answering those questions stays small. Most specialist content online is English; most searchers in our markets type Arabic. That gap is your opportunity.

So competition on Arabic keywords is far lighter than on English equivalents, where the whole world competes. A well-made Arabic page about a specific service in a specific city can reach page one far faster than you expect.

Intent matters more than volume. Someone typing in Arabic here usually wants a local supplier who speaks their language, understands their market and issues a proper invoice — not general information. Those visits sit closer to a purchase than generic English traffic from half a world away.

Long-tail phrases deepen the advantage. A website for a dental clinic, an inventory system for a spare-parts shop: dozens of searches a month, but whoever types them is ready to discuss a real project. In Arabic those slots are nearly empty.

Yet many companies still build English first "because it looks more professional", then spend on ads to compensate for their absence from Arabic search. Ads stop when payment stops; an indexed Arabic page works every day. To understand how indexing and ranking work at all, read our plain-language SEO guide for business owners.

Translation converts words. Localisation makes the site look and behave as if it was built for an Arabic reader from the start. The difference shows in details a customer notices within seconds, even without naming them.

Right-to-left changes the whole page structure: menu and button positions, arrow and progress direction, table column order, icon placement inside buttons. Some elements must flip (navigation arrows), some must never flip (logos, play symbols, clocks). Sites that mirror everything automatically look broken to an Arabic eye.

Type is part of this. A Latin font pulling an Arabic fallback produces poor spacing and tiring text. Arabic screen fonts such as Tajawal, Cairo or IBM Plex Arabic change the impression entirely — and Arabic needs more line height, with string lengths that break tight layouts.

Small decisions get forgotten and break consistency: Arabic-Indic numerals or Western ones? Most readers in Egypt and the Gulf read the Western forms comfortably online, but the point is to choose one and stay consistent. The same goes for date order, the Hijri calendar where it matters to Saudi audiences, currency formatting and symbol placement, and phone numbers that must stay tappable in the right direction.

This is where money is actually lost. A contact form that rejects Arabic names, an address field designed for American cities, a search box that cannot ignore diacritics — each ends the visit. In stores: product names, descriptions, error messages, checkout steps, shipping notifications and the invoice must be Arabic too. An Arabic storefront that ends at an English payment page loses the sale.

Localisation does not stop at text. A hero banner with English typed inside the image stays English in the Arabic version, because no translator sees inside a picture. Testimonials, case studies and client logos that impress one market may mean nothing in the other.

The practical rule: pull text out of images and make it real page text — better for translation, indexing and screen readers at once. Use alt text in the page's language and name image files in readable words.

This section is what to require from whoever builds your site. You do not need to implement it; you need to verify it.

A quick test anyone can run: open an Arabic page, choose "view page source", and search for a sentence you can see on screen. If it is not in the source, Google does not see it either.

• A separate URL per language: the Arabic version has its own addresses such as ‎/ar/services that open directly and can be shared. If switching language does not change the URL, your Arabic probably does not exist for Google.
• hreflang tags: the signal telling Google this page is the Arabic version of that English one, with x-default for unknown languages. Without it, the wrong version reaches the right searcher.
• Server-side rendering: Arabic must be inside the page source on load, not injected by JavaScript seconds later.
• An Arabic title and description per page: they appear in results and decide the click. A literal translation of the English title loses the phrase people actually search.
• A sitemap covering both languages and pointing at each page's alternates.
• lang and dir at page level, not on one inner element, so browsers and screen readers understand direction.
• Schema in the page's own language for your company, services and articles.
• Internal links that keep the language: every link on an Arabic page goes to the Arabic destination.

It produces text that is understandable but tonally foreign, full of terms nobody in the market uses. Readers feel it within two lines and leave. Use it as a first draft if you like, but never publish before someone who writes Arabic well and knows your field rewrites it.

A very common failure: the visitor reading a service page clicks "العربية" and lands on the homepage. That breaks the journey and raises bounce. A correct switch moves to the matching version of the same page and remembers the choice.

An Arabic heading with English buttons, an Arabic page with an English footer, an Arabic blog listing English titles. This confuses visitors and confuses Google about the page's language. The Arabic version must be Arabic throughout — buttons, system messages and the 404 page included.

Twenty English pages and three Arabic ones look worse than an English-only site, especially when the Arabic pages are stale and their services no longer match reality. Decide from the start which pages are bilingual, and commit to updating both together.

The best bilingual sites are not translated; they are written twice around the same message. The Arabic version uses the terms people actually type, examples from Cairo, Riyadh or Jeddah, and local references such as e-invoicing or familiar payment platforms. The English version is written for its own reader: clearer, shorter, closer to international business language.

The two need not be identical. Many clients publish long Arabic guides targeting local search alongside shorter English pages for partners and international buyers. Each language has an audience and a purpose. With limited budget, start Arabic on marketing pages and English on corporate ones.

Treat the blog as a main engine too. Service pages alone rarely compete for big keywords; deep Arabic articles earn the traffic and pass it on. That is how we work in SEO services.

Many companies add an Arabic version and then never learn whether it worked, because they read site numbers in aggregate. Separating the languages in measurement is what turns the site from a cost into a channel you can improve.

A timing rule: do not judge a new Arabic version before three months. Indexing takes weeks and trust takes longer, so any decision to abandon it earlier rests on nothing.

• Split traffic by language — the ‎/ar folder versus the rest — and compare enquiries, not visits.
• Watch in Search Console how many Arabic pages are indexed, which queries they appear for, and their average position.
• Track queries with impressions but no clicks: usually a weak Arabic title or description, not a weak page.
• Measure conversion per language; a wide gap points to a broken form or checkout step in one version.
• Ask every new client what they searched for. Those answers reveal phrases no tool will show you.

Modern Standard Arabic serves both, but the details differ. Saudi audiences search with their own vocabulary — an approved online store, e-invoicing compliance, Maroof, the commercial register — and expect mada, Apple Pay and instalment services at checkout. Egyptian audiences use their own terms, tools and payment methods.

The differences extend to tone, examples and buyer priorities, and one page addressing both usually convinces neither. The practical answer: shared core content in Standard Arabic, plus dedicated pages per market where the business case justifies it. If Saudi Arabia is your target, start with choosing a technology partner in Saudi Arabia.

A Cairo clinic with an English-only site. Every patient searches in Arabic for the specialty and the district. Adding an indexed Arabic version of the services, doctors and booking pages shifted the source of bookings within weeks from paid ads to organic search.

A software company selling to Gulf enterprises. The technical audience reads English, but the finance director who signs reads Arabic. The answer: English for product and documentation, full Arabic for the value, pricing, case study and contact pages.

An Egyptian store targeting Saudi Arabia. Same products, but the Saudi-facing Arabic pages needed different shipping and return terms, local payment methods, and language that reassures a Saudi buyer. A store that copies its pages unchanged loses the cart at checkout.

What the three share: the decision was never "should we add Arabic?" but "which pages deserve well-written Arabic first". Start closest to the money — your best-selling service, the contact page, and the two or three pages that answer what people ask you on WhatsApp every week — then widen. A planned partial Arabic version beats a sweeping bad translation.

• Does the Arabic version have its own URLs that open directly and can be shared?
• Is the Arabic text in the page source rather than injected by JavaScript?
• Are hreflang tags present for both versions, with x-default?
• Does every Arabic page have an Arabic title and description that were written, not translated?
• Does the language switch take you to the matching version of the same page?
• Is the RTL design genuine: proper Arabic fonts, correct arrows and directions?
• Are numerals, dates and currency consistent across the whole site?
• Are forms, checkout steps and error messages in Arabic?
• Do the Arabic pages appear as indexed in Search Console?
• Are both versions updated together, or has one been abandoned?

A bilingual site multiplies your reachable market: an Arabic audience searching in its own language with lighter competition, and an English presence for enterprise buyers, from one digital asset. The difference is execution — Arabic that Google reads and customers trust, not a translate button decorating the interface. That is how we build in web development, and how this site was built. If you are still comparing agencies, choosing a web design company in Cairo and the complete guide to choosing a software company in Egypt will save you several rounds.