Bilingual Copywriting (EN + AR Mirrored Sites)

I write the English and Arabic versions of your content in one pass, as one project, so both languages read natively instead of one being a translation of the other. The usual workflow — write English, then hand it to a translator — produces Arabic that limps. Writing both sides together means each version gets its own headlines, rhythm, and persuasion while saying the same thing, which is what bilingual audiences in Dubai, Abu Dhabi, and Sharjah actually notice.

For websites, the deliverable is a mirrored structure: every English page mapped one-to-one to its Arabic counterpart with matching sections, headings, and metadata — exactly what your developer needs to implement hreflang tags correctly and what search engines need to index /en/ and /ar/ versions without duplicate-content confusion. A consistent terminology glossary is built as I write, so your product names, service terms, and key phrases stay identical across every page, menu, and form in both languages.

CTAs get special attention because button copy that converts in English often falls flat rendered into Arabic — I write CTA pairs that carry the same intent and fit the same button widths in both directions. And it is not just websites: free-zone and mainland SMEs use the same one-pass approach for restaurant menus, company brochures, and presentation decks where English and Arabic sit side by side on the same spread.

How it works

1. 1
   Content map and glossary kickoff

   We list every page or asset, agree the EN/AR structure mirror, and seed the terminology glossary with your existing brand terms.

2. 2
   One-pass bilingual drafting

   I write each page in English and Arabic together, delivering them side by side so you can review the pair as a unit.

3. 3
   Review and alignment round

   Your feedback is applied to both languages simultaneously, keeping the versions in sync rather than letting them drift.

4. 4
   Mirrored handover package

   Final delivery: paired page docs, the EN-AR glossary, bilingual metadata, and an implementation note for your developer on the /en/ /ar/ structure.