Techbanq

Web · Arabic-first

Design the site in the direction most of its readers read

For most organisations selling in Saudi Arabia, the Arabic visitor is the majority visitor, yet the site is usually designed in English and mirrored later. We design right-to-left from the first wireframe — grid, typography, content and navigation — so the primary reader gets the primary experience, and the English version inherits the discipline rather than lending it.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

High-rise towers in the Riyadh business district at dusk

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The reading path

Where a right-to-left visit breaks on a site designed left-to-right

Follow one Arabic-reading visitor through a page and the mirrored-afterward site gives itself away at each stage. These are the moments an Arabic-first design is decided.

01

The first glance

The eye enters at the top right and scans for the proposition and the way in.

The visual hierarchy is composed for a right-entry scan: the headline, the imagery and the primary action sit where that scan lands, not where the English grid left them.

  • Layout grid
  • Hero
02

Reading the argument

The visitor reads paragraphs, and Arabic script punishes type set for Latin metrics.

Typefaces, sizes and line heights are chosen for Arabic at interface sizes first, so body text reads comfortably instead of looking like a shrunken afterthought beside the Latin.

  • Typography
03

Finding the next page

The visitor navigates, and mirrored menus with unmirrored logic disorient them.

Navigation order, breadcrumbs, carousels and directional icons follow right-to-left logic throughout — including the details automation gets wrong, like arrows that should flip and media controls that should not.

  • Navigation
  • Components
04

Acting on it

They fill a form with a Saudi phone number, a Hijri-relevant date and an address in Arabic.

Inputs handle mixed-direction text, Arabic and Latin numerals, local phone formats and bilingual validation messages — the point where most translated sites quietly lose the enquiry.

  • Forms
  • Validation

The content

An Arabic page written from intent argues; a translated one merely corresponds

Translation preserves sentences; it does not preserve persuasion. An Arabic page produced by converting approved English copy inherits English sentence rhythm, English idiom and an argument ordered for a different reader, and the result reads as what it is — a document about the organisation rather than a page addressed to the person reading it. The visitor rarely complains. They simply weigh the organisation as one that speaks to them second-hand.

We work the other way: the content brief is developed in Arabic, for the question the Arabic-speaking buyer actually arrives with, and the English version is then written to the same brief rather than serving as its source. This matters beyond tone. Search intent differs between the languages — what a buyer types in Arabic is not a translation of what they type in English — so pages born in Arabic rank for queries a converted page never targets.

One boundary keeps this page honest: hotels are a special case with their own economics and their own page on this site, covering the booking journey specifically. Everything here applies to the wider case — a contractor, a clinic group, a logistics firm, a public entity — any organisation whose Arabic-reading visitor deserves to be treated as the primary one.

The architecture

The structural facts a bilingual site has to keep true in both languages

Direction and copy are the visible half. Underneath them, a bilingual site holds structural commitments, and breaking any of them shows up as lost rankings or a second-class Arabic experience.

Every page exists in both languages at a stable address

A locale-aware URL scheme with correct hreflang pairing, so search engines serve the right language to the right query.

What it secures: Arabic queries land on Arabic pages, not on English ones with a language switcher.

The two versions say the same true things

One content model with paired fields per language, so a price, a name or a claim cannot be updated in one language and forgotten in the other.

What it secures: No drift between what the Arabic and English pages promise.

Direction is a design token, not a patch

Layout, spacing and iconography are built on logical direction-aware properties, so components render correctly in both directions from one codebase.

What it secures: A new feature ships in both directions on the day it ships.

Numbers, dates and names survive the boundary

Explicit rules for numerals, calendar display, currency and mixed Arabic-Latin strings, applied consistently rather than left to each browser.

What it secures: A phone number or an invoice amount reads identically wherever it appears.

Our role

What we deliver Arabic-first and what your organisation keeps deciding

  1. 01

    The Arabic experience as the baseline

    Wireframes, type decisions and component behaviour are designed and reviewed right-to-left first; the left-to-right version is derived from them, which is the reverse of how most bilingual sites are made and the reason ours do not read as mirrored.

  2. 02

    Content developed, not converted

    We build the Arabic content with your subject experts from an Arabic brief, and hand over a content model your team can maintain in both languages without a developer in the loop.

  3. 03

    The structural layer proven, not promised

    URL scheme, hreflang, direction tokens and mixed-content handling are tested against real Arabic content before launch, because these are the parts that fail silently and cost rankings for months before anyone notices.

What the organisation says, in either language, stays yours; we make sure the Arabic reader receives it as a first-class page rather than a courtesy copy, and leave your team the model to keep it that way.

Common questions

What buyers ask

If we design Arabic-first, does the English side of the site get worse?+

No — it usually gets better. Designing for the harder case first is an old engineering habit, and Arabic is the harder case: its script, direction and mixed-content behaviour expose weaknesses that Latin text forgives. A grid, a component set and a content model that survive Arabic handle English without effort. The reverse is not true, which is exactly why English-first bilingual sites need an endless queue of right-to-left patches. Both versions are written to the same brief, so neither is a translation of the other.

Our site already has an Arabic version. How do we tell whether it needs repair or a rebuild?+

Look at three layers. If the problems are content-level — stiff translated copy, missing pages — the structure may be sound and a content programme fixes it. If components misbehave in right-to-left — broken forms, unmirrored navigation, Latin-metric typography — the front end needs rework but the platform can stay. If the structure itself is wrong — no stable Arabic URLs, no hreflang, one shared template that only mirrors — repair costs more than rebuilding, because every fix fights the foundation. A short review places your site on that ladder before any budget is committed.

Who produces the Arabic copy — do we need writers on our side?+

You need subject knowledge on your side; the writing craft can sit on ours. The process that works is joint: your people supply what is true — the services, the differentiators, the answers buyers actually need — and our Arabic content work turns that into pages written from an Arabic brief, then the English is written to match. What we advise against is the shortcut of approving English copy and sending it out for translation, because the result reads translated no matter how good the translator, and the Arabic search intent it should target never gets addressed.

Start the conversation

A review of your current Arabic experience against the reading path a Saudi visitor actually takes, ending in a scoped plan for an Arabic-first rebuild or repair.

Start the conversation