Most of what gets published about arabic ui microcopy is generic. This guide is written for the Saudi market specifically — the platforms, the regulation, the buying behaviour and the costs that apply here.
Bilingual, mobile-first and fast is the baseline in this market, not the ambition. The differentiation happens in the details — typography that respects Arabic, layouts that mirror properly, and conversion paths that match how Saudi buyers actually behave.
Why this matters commercially
Treat arabic ui microcopy as a system with four parts: the asset you own, the demand you capture, the trust you demonstrate, and the measurement that tells you which of the three to invest in next. Weakness in any one caps the others. In Saudi Arabia, the part most commonly missing is trust demonstration — buyers here verify before they enquire, and the sites that make verification easy convert at multiples of those that do not.
Design for a mid-range Android on a moving connection
Internet penetration reached roughly 99% of the population at the end of 2025 and around three-quarters of people can reach a 5G device, but the median handset is not a flagship and a large share of sessions happen in transit. Design to that reality: generous tap targets, minimal script, images sized for the viewport actually served, no layout dependent on hover, and a first meaningful paint under two seconds. Test on a throttled mid-range device before signing off, not on the designer's laptop.
Trust signals Saudi buyers look for
A visible commercial registration number, a national address, a landline in addition to mobile, a Maroof badge for ecommerce, named team members with photographs, real client logos with permission, and a WhatsApp route to a human. Saudi buyers verify before they enquire, and the absence of these elements costs more conversions than any amount of aesthetic refinement recovers.
If you cannot state what a page is for in one sentence, it will not rank and it will not convert.
The language switch is a conversion element
Put it top-right in the English view, top-left in Arabic, label it in the target language, and preserve the current page rather than dumping users on the homepage. Remember the choice. Default by browser preference on first visit but never trap: a visitor who wants English must always be one click away from it. This small component is one of the most frequently mishandled details on bilingual Saudi sites.
Navigation that reflects how customers think
Organise by the problem the customer has, not by your internal departments. Keep the top level to five or six items. Make the primary conversion route visible on every screen without a scroll. Mega-menus are useful for large service portfolios but become a liability on mobile — design the mobile navigation as its own artefact rather than a collapsed version of the desktop one.
Forms: ask for less, get more
Every field you add costs completions. Name, phone and one open field is usually enough to start a conversation; qualification can happen in the call. Support Arabic input properly, validate Saudi mobile formats without rejecting valid ones, offer WhatsApp as an alternative to the form entirely, and confirm submission with a message that says what happens next and when. Silent success screens are why prospects call competitors.
Arabic typography deserves its own scale
Arabic script has no capital letters, taller ascenders and connected letterforms, so it needs roughly 10–15% more line height and often a slightly larger optical size than Latin text at the same nominal point size. Choose a family with a genuine Arabic cut rather than a Latin face with bolted-on glyphs. Test with real content at real lengths — Arabic translations commonly run shorter than English, which breaks layouts tuned to the wrong measure.
Rendering strategy for JavaScript sites
Client-side rendering delays indexing and makes AI crawlers — most of which do not execute JavaScript at all — see an empty shell. Server-side rendering or static generation for anything that must rank is no longer a preference. If a full re-architecture is out of scope, prerender the templates that matter commercially and leave the application behind login as a SPA.
Positioning before aesthetics
Identity work that begins with mood boards produces decoration. Begin with the commercial question: who exactly is the customer, what alternatives do they weigh, what do we credibly do better, and what will we deliberately not claim. Once those four answers are written and agreed, visual decisions become straightforward and arguments about colour largely disappear.
Typical project shape
| Stage | Typical window | What you should see |
|---|---|---|
| Discovery and content | 2–3 weeks | Usually the critical path, not development |
| Design system and key templates | 3–4 weeks | Bilingual from the first artboard |
| Build and integrations | 4–8 weeks | Varies most with third-party systems |
| QA, RTL testing and launch | 1–2 weeks | Real devices, throttled connections |
Windows assume consistent execution and a market of ordinary competitiveness. Treat them as planning ranges, not commitments.
Logs tell the truth that reports do not
Server log analysis shows which URLs Googlebot actually fetches, how often, and where it wastes budget. On large Saudi catalogues the usual finding is that most crawl activity goes to filtered listing URLs while new product pages wait weeks. Fixing that with parameter handling, pagination discipline and a clean XML sitemap is often worth more than any content project running in parallel.
Social proof that reads as real
Named clients with logos used by permission, quantified outcomes, photographs of actual work, video testimonials in Arabic, and review counts pulled live rather than typed as static text. Vague claims — 'trusted by hundreds' — reduce credibility rather than build it. Specificity is the whole mechanism: the more precise the claim, the more it is believed.
The working checklist
- Add a WhatsApp route to a human on every page
- Confirm numerals, phone numbers and Latin brand names stay left-to-right inside Arabic text
- Set correct language attributes so screen readers pronounce Arabic properly
- Test the full journey on a throttled mid-range Android before sign-off
- Set a performance budget for page weight and third-party scripts, then enforce it in review
- Give form fields visible labels and visible focus states
Redirects, migrations and the cost of getting it wrong
Map every old URL to its closest new equivalent one-to-one; never bulk-redirect to the homepage. Use 301s, not 302s. Keep the old sitemap live for a few weeks so the redirects are discovered. Preserve internal links, then update them. Watch Search Console coverage daily for the first fortnight. Migrations that lose traffic almost never lose it to bad content — they lose it to missing redirect mappings nobody checked.
Duplicate content in a bilingual, multi-branch site
Faceted navigation, session parameters, printer views, and city pages that differ by two words all create near-duplicates. Set self-referencing canonicals, block parameter crawling deliberately, and give each city page genuinely distinct content — local pricing, local case work, local landmarks and directions. If two pages can be swapped without a reader noticing, Google will pick one and it may not be the one you want.
Where to start this week
Test your site on a throttled mid-range Android. Time it. Then check the Arabic version for mirrored layouts, correct typography and a language switch that preserves the page. Add the trust elements Saudi buyers look for — registration number, national address, real photographs, a WhatsApp route. Most sites gain more from that afternoon than from a full redesign.
Pick the two changes above with the clearest link to revenue and ship them this month. Momentum matters more than completeness at the start, and a finished small change beats a planned large one.
