How to structure an Arabic and English website in Kuwait

A bilingual website in Kuwait is not one website with a language toggle. It is two full versions of the same site, each with its own URLs, its own copy, its own layout direction and its own presence in search. Build it that way and both languages work. Bolt Arabic on afterwards and you usually end up with a version nobody can find and nobody enjoys reading.

The decisions that matter are made early and are expensive to reverse: how the URLs are structured, how the two versions tell search engines about each other, how the layout mirrors, and whether the Arabic is translated or rewritten. Everything else is detail.

This is how we structure Arabic and English sites for Kuwait, in the order the decisions come up.

Choose a URL structure first

There are three sane options, and one to avoid.

• Subfolders. example.com/en/ and example.com/ar/. This is what we use for almost every client. One domain, one set of accumulated authority, simple hosting, simple analytics. It is the default for a reason.
• Subdomains. ar.example.com. Workable, sometimes forced by an existing platform, but you are running two properties and reporting on two.
• Separate domains. Only worth it when the business genuinely operates as two brands in two markets, which is rare for a Kuwaiti company.
• A language parameter, such as ?lang=ar. Avoid. It is fragile, it is easy to serve the same content on many URLs, and it gets messy the moment you add filters.

Pick one and be consistent, including the homepage. Decide whether the root serves a landing choice or redirects, and make sure every page in one language has a real, indexable counterpart in the other. If a page exists only in English, that is fine, but do not send Arabic visitors to a stub.

Slugs are worth a decision too. English slugs are lowercase words. For Arabic you can use Arabic script in the URL or a transliteration. Arabic slugs are readable to users and handled correctly by search engines, though they look like percent encoded strings when pasted into a spreadsheet. Whichever you choose, use the same rule across the site.

Tell search engines the two versions belong together

Hreflang is a small piece of markup with a large effect. It tells a search engine that this Arabic page and that English page are the same page in two languages, so the right one is shown to the right person, and neither is treated as a duplicate of the other.

Three rules cover most of it. Every page lists all of its language versions including itself. The references must point both ways, so if the English page names the Arabic one, the Arabic one must name the English one back. Use full URLs, not paths.

Use en and ar if you serve one country, or ar-KW and en-KW if you run separate versions for other Gulf markets. Add an x-default for the page a visitor lands on when nothing matches. Then set the two attributes people forget: the language and the direction on the page itself, so browsers, screen readers and translation tools behave. Submit both language versions in your sitemap.

Check it after every redesign. Hreflang breaking silently during a rebuild is one of the most common causes of a sudden drop in Arabic traffic, and it is invisible unless somebody looks. This is the sort of thing we check first on any SEO project that involves two languages.

Right to left is a layout job, not a switch

Setting direction to right to left flips the page. It does not finish the design. What needs attention:

• Mirror the layout, not the content. Navigation, sidebars, alignment and list markers flip. Logos, product photos, video player controls and anything with real world orientation do not.
• Directional icons flip. Back and next arrows, progress steps, breadcrumb separators. A back arrow pointing the wrong way is the classic sign nobody tested the Arabic version.
• Numbers and Latin words stay left to right inside Arabic text. Prices, phone numbers, brand names and email addresses need to sit correctly inside a mirrored line, which is where sloppy markup shows up as scrambled text.
• Use logical spacing rules in your CSS rather than fixed left and right values, so one stylesheet serves both directions instead of two that drift apart.
• Forms deserve a pass of their own. Placeholders, validation messages, date pickers, phone country codes and file upload buttons are usually the last things anybody translates.

Test by using the Arabic site as a customer would, on a phone, all the way to a submitted form. Bugs in right to left layouts hide below the fold and inside states you only see when something goes wrong.

Translate the facts, rewrite the persuasion

Specifications, policies, delivery terms and legal text should be translated accurately. Headlines, taglines, buttons and campaign copy should be rewritten. A tagline translated word for word is almost always flat, and sometimes accidentally odd.

Our working split is simple. Body content and product detail get a good human translation with a glossary of your brand terms, so the same word is used the same way everywhere. Anything meant to persuade gets written fresh in Arabic by someone who writes in Arabic, with the English as a brief rather than a source. Buttons and micro copy are part of that: a call to action that works in English can read abrupt or oddly formal in Arabic.

On register, Modern Standard Arabic is the right default for a website. Kuwaiti dialect has its place in social captions and short video, where it sounds like a person. On a checkout page it can read as careless. Keep one voice per surface and be deliberate about it.

Arabic type on the web

Arabic is not Latin at a different size. It has taller ascenders and deeper descenders, it needs more line height, and the same nominal font size reads smaller. As a starting point, set Arabic body text a little larger than the English and give it noticeably more line spacing, then look at the two side by side and adjust by eye.

Choose a face designed for Arabic that matches the weight and personality of your Latin one. Never fake it by stretching a Latin font or by leaning on a system fallback, and never use elongation to justify text. Check the numerals question early: decide whether you are showing Arabic Indic or Western digits, and be consistent across prices, dates and phone numbers.

Performance matters here. Arabic font files are large because of the number of glyph forms. Subset them, serve modern web font formats, preload only the weights you use, and keep the family count down. Two weights well loaded beat five that block rendering.

How people actually search in Kuwait

Search behaviour here is genuinely mixed, and it is the reason you cannot translate a keyword list and call it research.

Many people search in English for categories and brand names, then read the page in Arabic. Others search in Arabic but type brand names in Latin script inside an Arabic sentence. Transliterated Arabic typed on an English keyboard is common in social and messaging, less so in search. Arabic queries tend to be shorter, are typed without diacritics, and vary in spelling, particularly around hamza forms and the final letters that people write interchangeably.

What that means in practice: do keyword research separately in each language, using each language's own results. Expect the Arabic and English versions of the same page to target related but different queries. Write Arabic page titles that read naturally rather than as translations of your English ones. And check what your own audience does, since a business selling to government buyers and one selling to teenagers on Instagram will see very different splits.

The mistakes we fix most often

1. Redirecting by IP address. Forcing Arabic on anyone in Kuwait removes the visitor's choice and can stop one version being crawled. Suggest, do not force, and remember the language switch.
2. A toggle that swaps text with JavaScript on the same URL. There is no second page for search engines to find, so half your site does not exist.
3. Machine translated Arabic published without a human pass. It reads as machine translated, and it teaches customers not to trust the rest.
4. Half a site. Arabic homepage, English everything else. The visitor hits the wall on the page that was meant to convert them.
5. Untranslated system text. Order confirmations, form errors, invoices and email templates left in English on an otherwise Arabic journey.
6. Losing hreflang in a redesign, then wondering where the Arabic traffic went.

Frequently asked questions

Should Arabic or English be the default?

Look at your own analytics rather than guessing. Most consumer businesses in Kuwait are better served by Arabic as the default with an obvious switch, while business to business and technical companies often see the opposite. Whichever you choose, make the switch visible on every page and remember the choice.

Does an Arabic version help my rankings?

It gives you a second set of queries to compete for, which is usually the bigger opportunity, and it lowers bounce for Arabic readers. It does not improve your English rankings on its own.

Can one team run both languages?

Yes, if one person owns Arabic quality and has authority to rewrite rather than only translate. Bilingual sites fail on ownership more often than on tooling.

We treat Arabic as a first version rather than a translation layer, which mostly means deciding structure, type and voice before anyone writes a line. If you are planning a bilingual build, our websites and digital products work covers the structure and the build, and the SEO side covers keyword research done properly in both languages.