Most of the cost of Arabic website development gets decided before anyone translates a word. The templates decide how right-to-left text behaves, and the forms decide whether Arabic names get through. Settle those early and the Arabic version adds little to the bill. Leave them until the translation arrives and you usually end up rebuilding templates after launch.
Good Arabic website development starts with
lang="ar"anddir="rtl"on the html element and a stylesheet written with logical properties. Give each language its own URL and link the pair with reciprocal hreflang tags. Mirror the layout and anything that points along the reading direction, but leave numbers, logos and media controls alone. Have a human translator write the Arabic.
We run this site in twelve languages, and the Arabic version at mecanik.dev/ar/ finds our bad assumptions first. The fixes we made apply to Arabic website development on WordPress, Shopify, Next.js, Astro or a custom stack.
Arabic website development starts with two attributes
Every Arabic page needs two attributes on the root element.
1<html lang="ar" dir="rtl">
They are the cheapest part of the whole project. The W3C says dir="rtl" on the html element sets the default base direction for the whole document
. The same guidance says CSS should never set the base direction, because the direction can affect what the content means and has to survive even when the stylesheet does not load.
The lang attribute is what browsers use to select suitable fonts
, and speech synthesizers rely on it as well. Google, though, says it does not use the HTML lang attribute to detect page language
. Plain ar suits most sites, since ar-AE only earns its place when you publish different Arabic content for different countries.
On every Arabic website development project we drive lang and dir from one variable in the layout. That way no page goes out with Arabic text running left to right. When that mismatch slips through, full stops land on the wrong side and lists hang off the wrong edge.
Right-to-left layout and typography
Logical CSS in place of left and right
Logical properties save us more time than anything else in Arabic website development. Properties like margin-left assume text runs left to right. MDN describes them as a way to define direction-relative equivalents
of the physical ones. The same rules then work in either direction.
Converting a stylesheet is mostly renaming. margin-left becomes margin-inline-start, padding-right becomes padding-inline-end, and a positioned left becomes inset-inline-start. Here is a card with an accent bar down one side and an arrow.
1.card {
2 padding-inline: 1.25rem;
3 border-inline-start: 4px solid var(--accent);
4 text-align: start;
5}
6[dir="rtl"] .card__arrow { transform: scaleX(-1); }
With dir="ltr" the bar sits on the left. Switch to dir="rtl" and it moves to the right with no second stylesheet. The arrow is the only rule that mentions a direction, so we flip it on purpose. Flexbox and grid already follow the document direction, so a row of items reverses by itself.
Arabic website development on an existing theme starts with a search of the stylesheet for left, right, float and translateX. Third-party plugins hide most of the leftovers, so we also test each one in Arabic before agreeing to use it.
What to mirror and what to leave alone
Flipping the entire page is a mistake. In an Arabic layout we mirror anything whose meaning depends on reading order and leave the rest alone.
| Mirror it | Leave it alone |
|---|---|
| Page layout, menu order, sidebars | Logos and brand marks |
| Back, forward, next and previous arrows | Numerals and phone numbers |
| Breadcrumb separators | Media play, pause and seek controls |
| Progress bars and sliders | Clocks and most real-world pictograms |
| Text alignment and form label position | Code, URLs and email addresses |
| Carousels and step indicators | Charts that plot time |
Media controls trip teams up most often. We leave the play triangle and the timeline as they are, because they describe how the media plays and have nothing to do with reading order. When we are unsure about an icon, we ask a native reader whether the flipped version looks wrong.
Mixed Arabic and English on one line
Arabic website development in the UAE rarely means Arabic alone. A typical page mixes the Arabic with Latin brand names, prices, phone numbers and product codes. The W3C bidi basics article explains that neutral characters such as punctuation take the base direction where two opposite runs meet. That is how a full stop ends up at the wrong end of a mixed line.
Isolate any text you cannot predict. MDN recommends the bdi element for dynamically inserted text of unknown direction
, such as customer names, feed titles and reviews.
Form inputs and comment bodies should carry dir="auto", because their direction depends on what the user types. However, the W3C admits that it is not foolproof. Setting unicode-bidi to isolate in CSS gives the same visual effect as bdi. Still, MDN warns that the property is meant for document type designers. We only use it when we cannot change the markup.
Fonts, spacing and digits
Most Latin fonts have no Arabic glyphs at all, so the browser falls back to a system font and the page looks patched together. That makes font choice an early step in Arabic website development. Noto Sans Arabic, IBM Plex Sans Arabic and Cairo would all make our shortlist. We pair one with a Latin font of similar weight and x-height so mixed lines look even.
Arabic letters carry dots and marks above and below the line, so the text needs more generous leading than English. We set a larger line-height under :lang(ar) and check it on a long paragraph, because a short heading hides the problem.
Arabic letters also join up, and MDN warns that letter spacing on Arabic script
can make the text look broken. Set letter-spacing to zero on Arabic text even when the English headings use positive spacing.
Digits are a smaller decision in Arabic website development, but they still need one. Arabic text can use Arabic-Indic digits (٠١٢٣) or the Western digits (0123) used in English. For prices, phone numbers and order references we recommend Western digits, since customers copy them into forms. Whichever set you choose, use it consistently and test search and form validation with it.
Forms are where Arabic website development usually breaks
Visitors notice a broken Arabic form before anything else. Labels and fields follow the page direction, so the label sits on the right. Fields that always hold left-to-right data, such as email addresses and phone numbers, should carry dir="ltr". Then the value does not jump about while someone types.
Validation written for English also breaks quickly. A name pattern that only accepts A-Z rejects every Arabic name. Similarly, a phone rule that cannot cope with +971 turns away real customers. We accept Unicode letters in name fields and normalise digits on the server. We also strip the invisible direction marks that copy and paste can drag into a value.
Text stays UTF-8 from end to end, including the database collation, email templates and PDF invoices. Order confirmations, SMS messages and invoices belong to Arabic website development too, and they need the same right-to-left treatment as the pages.
We fix Arabic forms like these on existing sites as well as on new builds, through our website development service .
Arabic website development and search engines
Each language needs its own URL. We use subdirectories such as /en/ and /ar/ on one domain, which Google lists as easy to set up and low maintenance
on a single host. Some sites switch language on one URL with a cookie. Google recommends separate URLs over cookies and warns that it might not find and crawl every variation.
Google’s guide to localized versions
sets out the rules. Each language version lists itself and every other version, and the annotations have to be reciprocal or Google ignores them. The x-default value marks the fallback for everyone else.
1<link rel="alternate" hreflang="en" href="https://example.ae/en/services/" />
2<link rel="alternate" hreflang="ar" href="https://example.ae/ar/services/" />
3<link rel="alternate" hreflang="x-default" href="https://example.ae/en/services/" />
Both pages carry the same three lines, each with its own canonical URL. We wrote up the failures we hit running hreflang across twelve languages , including translations that drift apart in structure.
Arabic keywords need their own research, because people in the UAE may search in Arabic, in English or in a mix. Dialect, spelling variants and transliterated brand names pull Arabic queries away from a literal translation. So we research them with native speakers and Search Console data, then write the Arabic titles and metadata from scratch. The rest of the technical groundwork works as it does in English, and our technical SEO audit checklist covers it.
Who should write the Arabic
In Arabic website development, machine translation makes a reasonable first draft for internal review. For a customer-facing UAE site, though, our experience is that it reads stiffly and often gets Emirati business and legal terms wrong.
Brand pages, services and the home page need a human translator, plus a second native reader. Legal pages also need review by your legal adviser. A large product catalogue can start as a machine draft if a person reviews the titles, key attributes and best sellers. Interface strings need a translator who can see the real screens. A button label sent without its screen is a guess.
Agree a glossary of approved terms before translation starts, or one service name will turn up in three Arabic spellings. Arabic can also run shorter or longer than the English, so fixed-width buttons and tight tables tend to break.
Arabic website development does not stop at launch, so someone has to own changes. When an English page changes, flag the Arabic one. Otherwise the two drift apart and the hreflang pair stops describing the same content. If the site takes bookings or payments, have a native reader try the whole journey on a phone, error states included.
How Arabic website development changes the quote
The extra effort for Arabic lands unevenly. A flat percentage on top of the English price rarely fits, because each part grows with something different. Design work grows with the number of unique components, while translation grows with the number of pages. Testing grows with every integration, since each payment, booking or CRM plugin has its own right-to-left quirks. The extra work stays modest on a small marketing site built right from the first template. On a large store with many plugins it is considerably more.
Ask any agency to price the Arabic website development work as a separate line listing templates, languages, translation source and test devices. If you are still choosing a platform, we compared WordPress, Wix and Squarespace for business sites.
We build bilingual sites as part of our web development work. Our Arabic website development starts at the first template, with the right-to-left layout, hreflang and translation workflow set up there. If you are planning an Arabic and English site, ask us for a quote . Tell us the platform, the languages and the integrations you need to keep.