Six months ago, we launched the AlsheikhMedia blog with a commitment that felt simple on paper: every post, in Arabic and English, at the same time.
It has not been simple.
Not because the idea was wrong — bilingual publishing is the right call for a media company operating between Arabic-first and English-first markets. But because building a bilingual content operation from scratch surfaces problems that no single-language blog ever has to solve. Problems of workflow, of translation philosophy, of audience behavior, of technical infrastructure, of what it actually means for content to feel native rather than translated.
This is what we learned.
What We Assumed Going In (That Turned Out to Be Wrong)
We assumed translation was the hard part. It is not. Translation is a task. You can systematize a task. The hard part is deciding which language to write in first — and that decision shapes everything that follows. If you write Arabic first and translate to English, you produce content that reads naturally in Arabic but sometimes sounds formal or stilted in English. If you write English first, you risk producing Arabic that feels imported: the cadences are wrong, the idioms do not land, the references are culturally distant. We spent the first two months getting this backwards.
We assumed the same content would work for both audiences. It does not — not reliably. Arabic readers arriving at our site via Google search have different prior knowledge, different trust signals, and different content expectations than English readers arriving via the same query. A piece that works well in English sometimes needs structural changes — not just translation — to earn the same engagement in Arabic. The post that generated our highest English traffic in month two was our third-highest performer in Arabic, behind two posts that barely registered in English. The audiences are not mirrors of each other.
We assumed bilingual SEO was just translating your keywords. It is substantially more complex. Arabic SEO requires understanding how Arabic speakers actually phrase search queries — which is influenced by dialect, formality level, and platform. “Social media marketing” in Gulf Arabic search behavior is not simply “تسويق عبر وسائل التواصل الاجتماعي” — that is the formal written Arabic phrase, but actual search patterns include variations, transliterations, and hybrid Arabic-English queries that require research, not assumption.
What Actually Broke First
The Workflow
Our original workflow was linear: write in English, send to translator, review Arabic, publish both. This took eight to ten days per post and produced inconsistent results depending on the translator’s availability and the subject matter’s technical depth.
The problem was not capacity — it was structure. We were treating translation as a handoff rather than a parallel creative process. When we restructured so that the Arabic writer was briefed on the same source material at the same time as the English writer (rather than receiving a finished English draft), quality improved noticeably. Both versions now feel like original writing that happens to be published simultaneously, not a primary text and its translation.
The Technical Infrastructure
RTL and LTR content sitting in the same codebase sounds manageable. It creates more edge cases than you expect. Shared components that look fine in English render poorly in Arabic because of punctuation placement, number formatting, quotation mark conventions, and text wrapping behavior in short containers. Our blog card design worked for all English headlines but broke for Arabic headlines longer than a certain character count — not because our Arabic titles were too long, but because Arabic wraps differently.
We also underestimated the SEO infrastructure implications. Separate hreflang tags, separate sitemaps, separate indexing behavior — all of these need to be set up correctly from the start. We set up the Arabic blog after the English blog was already live and indexed, which created a month-long gap in Arabic search visibility while things propagated correctly.
The Review Process
Arabic content needs native speaker review that goes beyond grammatical correctness. It requires someone who understands not just the language but the register — the level of formality appropriate for our audience, the vocabulary that signals expertise without sounding academic, the phrases that are technically correct but culturally off. We went through two reviewers before finding a workflow that produced consistent results. This is one of the slowest-to-fix problems in bilingual content because it is a talent search, not a tool upgrade.
What Worked Better Than Expected
Arabic-original content outperforms translated Arabic content. Posts where we wrote the Arabic version first, or where the Arabic writer developed the framing rather than receiving it from the English side, consistently outperform posts that feel like translations. Readers notice. The difference is subtle — a turn of phrase, a local reference, an idiom that actually fits — but it compounds.
The bilingual format builds trust signals that single-language blogs cannot. For a company positioning itself between Arabic and English-speaking markets, showing that you can produce genuinely good work in both languages is a stronger proof point than any testimonial. Clients have told us directly that they began following the blog in Arabic specifically because they wanted to evaluate whether our Arabic thinking matched our English thinking. It is an unusual credibility test, but a real one.
Consistent publishing cadence mattered more than format perfection. We had lengthy internal debates about whether to launch the Arabic blog only when we were confident the quality was high enough. In hindsight, launching on a consistent Tuesday-Thursday schedule from the beginning — even when the early Arabic posts were not our best work — built the audience habit that made later high-quality posts land well. The audience you have on month six is partly a function of the consistency you demonstrated in month one.
The Metrics That Surprised Us
Arabic readers spend more time on page than English readers across almost every post. We do not have a complete explanation for this, but our hypothesis is that the Arabic-reading audience for professional content in our category is still relatively underserved — readers who find relevant content stay with it longer because there is less competition for their attention in Arabic.
English posts get more inbound links, which drives English posts up in search rankings faster. Arabic posts get more direct return visits from existing readers. These are different distribution mechanics, and they require different amplification strategies. Treating them identically leaves value on the table.
Our highest-performing post in Arabic — a piece on RTL-first web development — found a technical audience that our English post did not reach at all. The Arabic tech content community is smaller but more concentrated, and a piece that addresses their specific context rather than translating from Western tech discourse gets a disproportionately strong response.
What We Would Do Differently From Day One
Commission Arabic and English simultaneously, with separate briefs. Not the same brief translated, but briefs written for each audience’s context and prior knowledge. This takes more planning upfront and pays for itself within two weeks.
Build the technical infrastructure bilingual from the start. Every month you wait to implement proper hreflang, RTL CSS, Arabic font loading, and bidirectional text handling is a month you accumulate technical debt that eventually needs to be cleared. Clear it at zero, not at six months.
Hire for Arabic editorial judgment before hiring for Arabic language production. The writer who can produce grammatically correct Arabic business content is easier to find than the editor who knows whether that content will resonate with a Riyadh executive versus a Dubai startup founder versus a Cairo marketing manager. The editorial layer is the constraining resource — invest in it first.
Track Arabic and English separately from launch. Treating them as a single combined property in analytics masks divergent behavior. The insights from separate tracking are where the interesting content strategy decisions live.
Publish in Arabic first. We are a company that talks about Arabic-first markets. Publishing in English first sends the wrong signal about how we think. We reversed this at month four. We should have started there.
What Bilingual Actually Requires
Running a bilingual blog well is not twice the work of a single-language blog. It is a different kind of work — one that requires building two parallel editorial capabilities, two SEO strategies, two distribution channels, and two sets of reader relationships, while maintaining consistency of voice and perspective across both.
The companies that do this well treat bilingual publishing as a strategic capability, not a content format. They invest in it accordingly — not with double the budget, but with genuine organizational commitment to producing original-quality work in both languages.
We are still building toward that standard. Six months in, we have learned more about our own operation than any internal audit would have surfaced. That, at least, is exactly what a genuine retrospective should do.
AlsheikhMedia publishes bilingual content every Tuesday and Thursday. If you are building a bilingual content operation and want to compare notes, get in touch.
