Two languages. One coherent reading journey.

Start with the reader’s question

A bilingual business publication begins with the decisions its readers need to make. An Arabic-speaking owner and an English-speaking procurement manager may need different explanations of the same subject. Build a question inventory from approved customer enquiries, editorial interviews and search information available after launch. Separate the intent to understand a topic from the intent to compare an offer or request help. One article should answer a defined question. A language programme becomes easier to maintain when the team knows why each page exists and which next decision it supports.

Give each edition a stable address

Google recommends separate URLs for different language versions, with links that let readers choose the alternative edition. For a publication, a stable English article address and an equivalent Arabic address provide a clear foundation. A visitor should be able to open either directly and read the complete content. Do not make a language preference stored in the browser the only route to a translation. Use a predictable structure that editors can explain, and keep the addresses consistent when an article is updated so that saved links and shared references remain useful.

Map equivalent pages deliberately

Maintain a page-pair register with the article identifier, English URL, Arabic URL, responsible editor, latest substantive revision and review state. An article should not be marked fully bilingual when only its navigation has been translated. If one edition is genuinely unavailable, show an honest route to the language that exists instead of sending the reader to an unrelated homepage. Treat a local adaptation as a deliberate editorial decision. Record which sections differ and why, so the relationship remains clear when the same topic is revised several months later.

Localise the decision, not only the words

Translation quality becomes commercially important when readers need to act. Explain specialist terms in the language your audience uses, retain the meaning of measurements and distinguish a formal requirement from an editorial suggestion. Keep OMR amounts, reporting periods, project names and source references aligned across editions. For an illustrative property guide, an English phrase about a buyer information pack may need a more explanatory Arabic heading. The goal is the same useful decision, not identical sentence length. A fluent reviewer should check the answer and examples rather than approving a page from its title alone.

Make the language relationship explicit

Google’s language-alternate guidance explains that each version should identify itself and the other versions using complete URLs, with reciprocal references. Hreflang annotations express the relationship; they are not a ranking guarantee. For a small bilingual publication, maintain one reliable implementation rather than three systems that can drift apart. Keep technical metadata consistent with the actual article and its language. The deployment check should flag a missing pair, an incorrect address or a language link that lands on the wrong story. Repairing these errors protects the reader journey as well as discovery.

Build links around useful next steps

Organise the site into a manageable set of subject desks, then connect closely related questions inside each desk. A guide to a hotel’s booking journey can link to an enquiry process or a campaign calculation when those links help the reader continue. Use clear link text that describes the destination. Avoid creating nearly identical pages for every city or keyword variation when the answer and evidence have not changed. Distinct pages need distinct jobs. A concise topic introduction and a well-chosen reading route can be more useful than a long page of disconnected article cards.

Test the complete Arabic experience

Test the Arabic edition as a complete product. Read it on a narrow phone screen, check right-to-left layout, mixed Arabic and Latin names, numerals, tables and form labels. Open an article, switch languages and confirm that the equivalent article appears. Try search with an Arabic question and a common English technical term. Check downloadable briefs for the same definitions shown on the page. These are practical quality tests, not claims about a search algorithm. Accessibility, clear contrast and visible keyboard focus should remain part of both language editions.

Measure language editions separately

After public launch and measurement setup, review the editions separately before combining their results. Compare relevant search queries, article entrances, useful next actions and qualified enquiries. Differences may reflect audience needs, translation quality, distribution or sales follow-up rather than the language itself. Maintain a small list of unanswered questions for each edition, with the evidence needed to answer them. Update a page when the substance changes, and record that change accurately. A strong bilingual publication grows through better coverage and dependable maintenance, not by multiplying translations that readers cannot confidently use.