AI
- 40Pages
- 13Chapters
- 106Sources
Get your copy of Arabic First.
40 A4 pages with live right-to-left examples, a regulation matrix, a RACI, a 16-week plan and a release QA checklist. Free. We also email you the link so you can share it with your team.
Or book the free Health Check →More than 400 million people use Arabic every day, yet W3Techs measures Arabic on about 0.6% of websites. Most Arabic defects come from writing the Arabic last.
Our short answer
Most of the defects we find in Arabic sites trace back to a missing owner, a missing review step or a missing release check.
Name one Arabic owner with a veto. Keep English out of the Arabic fallback chain. Let AI draft and a native speaker approve. Then test the Arabic site first, on every release.
- 400M+People use Arabic daily
- 0.6%Share of classified websites that are in Arabic
- 16 weeksFrom decision to launch, in four stages
- 27Release checks for the Arabic site
Thirteen chapters, one line each
Arabic readers are online. Arabic pages lag far behind.
400M+ people use Arabic daily; 0.6% of classified websites are in Arabic.
Decide where each content type is born.
Originate, transcreate, translate or protect. Name one Arabic owner with a veto.
The rules target documents your site produces.
Invoices, terms, disclosures and ads need Arabic. Check every line with counsel.
Fallback is the setting that leaks English.
Let ar-SA borrow from ar. Keep English out of the Arabic chain, and test delivery.
AI drafts, a native speaker approves.
Leave Keep workflow state cleared, so AI Arabic starts in Draft.
Direction is front-end code.
dir and lang in markup, logical CSS, isolated phone numbers, a font with the riyal sign.
Arabic traffic needs a complete Arabic page.
Reciprocal hreflang, encoded Arabic slugs, and a search box that normalizes Arabic.
Hosting and AI processing are two questions.
In-country SitecoreAI is announced and not yet confirmed live. Ask where AI runs.
MSA by default, dialect by decision.
Neutral noun phrases on buttons avoid choosing a gender.
Measure the gap between languages.
Parity, lag, defects and reviewer edits, every month.
Sixteen weeks to launch.
Decide, build foundations, pilot, scale. Then run.
Score yourself honestly.
Twenty-four statements, 0 to 3 each. Start with your lowest area.
Test the Arabic site first.
Twenty-seven checks. Fallback, workflow and forms failures block the release.
Summarized from Arabic First, an Arcsen guide, 40 pages, November 2026. Every figure in the full guide has a numbered source, checked on 4 November 2026.
Quick answersQuestions this guide answers
Why do Arabic pages show English text?
Can AI translate a SitecoreAI site into Arabic?
What does a right-to-left Arabic front end need?
How should Arabic pages be set up for search?
Should Arabic website copy use MSA or dialect?
How long does an Arabic-first SitecoreAI launch take?
Who it is for
Who publish in two languages and are measured on both.
Who own the SitecoreAI roadmap, the workflow and the release calendar.
Who build the right-to-left front end and the translation pipeline.
From Arcsen’s Sitecore practice: a Sitecore partner and a Salesforce Summit partner with teams in Riyadh, Jeddah, Dubai, Doha and Cairo.