Skip to main content
Rasad

Blog

Blog Overview

Multilingual content operations: how English and Arabic stop drifting

PublisherAbwab Admin
Published OnNov 15, 2026
Reading Duration15 min read
Last UpdateNov 15, 2026
Multilingual content operations: how English and Arabic stop drifting

Drift is an operations problem, not a translation problem. This article puts the content model, the workflow, the glossary, the publishing gate and both directions into one system, so the two versions stay equivalent after launch rather than on launch day.

On most bilingual sites, drift does not happen all at once. It happens because an English page was edited in March while the Arabic stayed as it was in January, because someone added a new offer to the English version and forgot that the Arabic version is what most visitors read, and because an Arabic page went live last week with no English counterpart because the deadline was Thursday. Nobody decided to leave a language behind. There was simply nowhere that recorded the state of each language, and no one whose job was to compare them.

The cost of that drift does not appear in one report. It appears in an Arabic visitor reading an old price, in a policy page that says different things in each language, in a search engine finding two pages competing for the same question, and in a support team answering from copy that is no longer true. The fix is not a better translator. A good translator carries an existing text across; they cannot know that the English changed after they delivered, and they cannot force both versions to publish together. The fix is an operating model: one source of truth, a content model that stores both languages in the same record, a workflow with explicit states, a glossary, and a release gate that stops one language getting ahead of the other.

Where the drift actually starts

Four patterns repeat in almost every project. First, translation is treated as an event rather than a state: a translator is sent a text, returns a file, someone publishes it, and nothing in the system links the Arabic version to the English one. Second, the CMS stores pages rather than fields, so the Arabic page becomes an independent page with its own title and date, and nothing tells you it corresponds to another page. Third, release happens per page, so an English page can ship today and its Arabic version three weeks later. Fourth, ownership is split: a marketing team owns English, an unnamed person owns Arabic, and nobody owns the match between them.

These patterns are not individual mistakes. They are the result of a design that lets the two languages move at different speeds. That is why hiring a better translator or buying a translation tool is not enough. A tool that does not know the state of a language and does not link the two pages will produce the same text you produce today, only faster. The repair starts in one place: every content unit becomes one record that carries two languages, and each language inside it has a state, a date and an owner.

One source of truth, not two versions

The source of truth is not the first language; it is the fact itself. The official figure, the service scope, the published price and the legal wording all live in one place that both languages read from. In our work, for example, the company figures live in one source and both the Arabic and the English versions read from it, which is why one version cannot claim five years of experience while the other says something different. Prices follow the same rule: the published price bands are the reference, and the numbers are not typed by hand into a page or a deck.

The text itself, however, is not a copy of the other language. An Arabic page written by translating English word for word reads like English wearing Arabic clothes: long nominal sentences, passive constructions in every line, and information ordered to suit another language. Good Arabic copy is written for the Arabic reader from the same facts, in an order that starts with what matters to them, using terminology they recognise. That does not mean the two pages differ in substance: the facts, figures and scope stay identical, and the phrasing follows the language.

The practical decision to settle early is which language is written first. On a site selling to a Saudi audience, many of the pages that carry the decision should be written in Arabic first and then translated into English, because translating from Arabic forces the writer to decide what they are saying before they start. On a site aimed at an international buyer or a government buyer reading English, the reverse may be right. What matters is that the decision is written down per content type rather than left to the team's habit.

The content model before translation

A content model is the difference between a system that knows each page has two languages and a system that only knows it has many pages. Fields are what get translated, not pages. When the field is the unit, you can see at a glance which field is missing in which language, send the translator only what they need, and reuse the text elsewhere without copying it.

FieldRuleWho decides
Main titleWritten for each language, not translated word for wordContent editor
Excerpt or summaryAn independent decision, not a copy of the first sentenceContent editor
Page bodyWritten or edited in Arabic, then translation passes a reviewerWriter, then language reviewer
Button labels and messagesOne glossary for the whole interface, not fresh wording per screenUX owner
Page pathOne decision, fixed once: translated or transliterated, then stableSite owner
Image alternative textWritten per language according to what the image actually showsContent editor
Product and brand namesKept as they are, or transliterated by a documented decisionBrand owner
Numbers, dates and currencyOne format per language, no mixing inside a pageContent owner
Legal pagesReviewed legally in both versions, never one without the otherLegal adviser

The workflow from draft to publish

A good workflow is simple enough for people to remember: draft, review in the source language, ready for translation, translated, reviewed, published. Then a seventh state, the most important one: needs update. When the English text changes, the Arabic moves automatically to “needs update”, and that shows on one board. That state alone prevents most drift, because it turns what one person knew into something everyone can see.

Delivery is not publication. The translator delivers a text, the language reviewer approves it, the content editor publishes, and the content owner accepts that the two pages are equivalent. That separation is not bureaucracy; it is what stops an unreviewed machine draft reaching a page a customer reads. And the exception has to be written down: if you must publish one language before the other, record the reason, the due date and who follows it, otherwise the exception becomes the rule within two months.

Machine translation can be a first draft and nothing more. It is useful for turning a long text into a fast structure, and harmful if it reaches production unreviewed, because it translates the same term two ways, drops what it does not recognise, and produces sentences that are grammatically correct and meaningless in context. If you use it, feed it your glossary first, and make every output pass a person who knows the product, not a spell checker.

Glossary and language decisions

The glossary is the cheapest tool in all of this and the one with the most effect. A short list is enough to start: service names, order states, role names, and the terms that appear in buttons and messages. Each term gets one decision: translated, kept as is, or transliterated by a rule. The glossary lives next to the editor, not in a folder on a drive nobody opens, otherwise it exists in theory and is absent in practice.

There are smaller decisions that appear on every page, and each becomes a source of inconsistency if it is not settled: Arabic-Indic or Western digits, Hijri or Gregorian dates and which comes first, how the currency is written, whether the reader is addressed in the singular or the plural, and whether the register is formal Arabic or a local touch on certain pages. There is no single right answer, but there is one answer per site. Write it on one page, call it the language policy, and put it where writers will see it.

Language review is not only proofreading. It is the reviewer asking: would this sentence be said this way in Arabic, or is it English in Arabic clothing? Is this the term the customer uses, or an internal one? Does the text carry the same promise as the other language, or a weaker one? The difference between “we deliver on the agreed date” and “we strive to respect deadlines” is not a difference in elegance; it is a difference in what the customer reads.

From reading to shipping

Want this built, not just explained?

Bring us the problem behind the article. We will tell you what it takes, what it costs, and whether we are the right team.

Direction is not fixed by flipping it afterwards

Material Design's bidirectionality guidance is explicit: an RTL layout reverses alignment and ordering, and components must be designed for both directions rather than flipped afterwards. That sentence sounds technical, but it is an operating decision. If the screen is designed in English and then flipped, you discover after design that the arrow points backwards, the progress bar runs the wrong way, the table puts its first column in the wrong place, and the close icon has moved to the side the user reads as “continue”.

In practice that means using logical properties in styling, start and end rather than left and right, designing the component in both directions at the design system level rather than the page level, and testing directional icons, tables, charts, steppers and bars. It also means watching mixed text: an order number, an email address or a URL inside an Arabic sentence needs isolation so its order does not flip. Above all it means testing with real Arabic copy rather than placeholder text, because length and shape change, and Arabic needs a family with appropriate metrics, such as Noto Kufi Arabic or IBM Plex Sans Arabic, not a Latin face with an Arabic fallback.

What we see most often is a complaint about something “flipping” on a page after a new feature ships. The cause is usually not the font but a component built on a single-direction assumption and then dropped into an Arabic page. The earlier article on Arabic RTL design mistakes shows specific examples, and it is where we usually start when reviewing an existing interface. The rule we work by: if the component has not been designed in both directions, it is not ready, and it cannot be repaired by flipping it later.

URLs and hreflang: one address per language

Each language gets one stable address, not one address with a parameter appended. A stable address can be shared, linked and indexed on its own. A parameter such as “?lang=ar” makes the two pages look like one page to some visitors and some tools, and makes it harder for anyone copying the link to get the version they wanted. The address should reflect the language in the path, an Arabic path and an English path, and stay stable afterwards.

Alongside that, each page needs reciprocal signals telling a search engine that this is the Arabic version and that is the English one, with a signal for the default version when neither language applies. The signals must be reciprocal: if Arabic points to English and English does not point back, the signal is incomplete. Three mistakes are common here: a language switcher that returns the visitor to the homepage instead of the same page, internal links in an Arabic article that point to the English page, and an automatic redirect by country that stops a visitor reaching the language they wanted.

The path decision itself has to be made once: Arabic script in the path, transliteration in Latin letters, or a short English word? No option is free. An Arabic path is readable to an Arabic reader and sometimes awkward to copy; a transliterated one works everywhere and is less clear. What matters is one decision, and a redirect map if an old path changes, because changing paths without redirects erases whatever standing you built in search results.

Release: how one language stops getting ahead

The parity gate is the procedure that turns intention into a rule. The simple form: no new page ships in one language without a recorded exception. The practical form: a page has a counterpart field filled in at creation, and the publishing system refuses to publish when the field is empty or the state is “needs update”. That is not heavy engineering, but it needs a written agreement, because the first person to ask for an exception will be a manager with a deadline.

Release itself needs a sequence. If content freezes on Wednesday, translation has to arrive before Tuesday, not start after it. If there is an urgent change to a page carrying a price or a legal term, both versions change in the same release, or the page comes down in both languages until the second is ready. A page that says one thing in one language and another thing in the other is worse than a missing page, because it creates an obligation you cannot honour.

Operations needs one owner of the outcome, not a committee. The content owner is accountable for the two versions being equivalent, and each language has an editor who executes. Once a quarter, take a sample of the most visited and most decision-relevant pages, read the two versions side by side, and log the differences in a list with an owner and a date. That periodic review is the difference between a system that stays equivalent and one that was equivalent on launch day. The work itself sits inside web platform development, because the content model and the publishing gate are part of the platform, not an addition to it.

The checklist before you build the second language

Eight items decide whether the second language stays equivalent months after launch or becomes an old copy with a nice title. Review them before translation starts, not after.

  1. One entry per page: both languages inside the same record, not two separate pages with no link between them.

  2. A state per language: draft, review, ready, published and needs update, visible on one board.

  3. One owner of the outcome: a person accountable for parity, an editor per language, and not a committee.

  4. An approved glossary: a short approved list, next to the editor rather than in a forgotten folder.

  5. A parity gate before publishing: no page ships in one language without a recorded exception with a date and owner.

  6. Reciprocal signals between languages: each page points to its counterpart and the default version, and the switcher keeps the page.

  7. Components designed in both directions: designed and tested with real Arabic copy, not flipped automatically after handover.

  8. A quarterly freshness review: a sample read in both languages, differences logged, and a fix list with an owner.

Frequently asked questions

Do we write in Arabic first or English? The audience decides, not habit. If the decision is made in Arabic, write Arabic first and translate from it, because that forces you to settle what you are saying. If the buyer reads English, reverse it. The requirement is that the decision is written per content type and the facts stay identical.

Is machine translation acceptable? As a first draft only, with the glossary fed in advance and a human review by someone who knows the product. An unreviewed machine text is fine as a starting point and unfit as a page a customer reads.

Do we need a new CMS? Not necessarily. Many systems support a field per language, and the problem sits in the configuration rather than the product. If the system stores separate pages with no counterpart field, that is the first thing to fix.

How do we measure drift instead of feeling it? Count pages with no counterpart, pages where one side changed without the other, and the age of the gap between the two dates. A quarterly report is enough, provided it has an owner and a fix list.

Can the two pages differ in style? Yes, and they should. Style follows the language and the reader. What may not differ is the promise, the scope, the price and the facts, because a non-Arabic reader is not a less important reader.

Sources

Cover image: Ferdinand Schulthess, Public domain, via Wikimedia Commons.

Get in Touch

We'd love to hear from you. Fill out the form and we'll get back to you soon.