Everything below is written for decision-makers who need logistics and freight website saudi arabia to produce commercial results, not for people collecting best practices.
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.
Setting the scope
The honest starting point for logistics and freight website saudi arabia is an audit rather than a plan. Half of what most Saudi businesses need is already present and broken — a profile nobody maintains, pages nobody links to, data nobody reconciles. Fixing existing assets typically returns faster than building new ones, and it is considerably cheaper. Build only after you have exhausted the repairs.
RTL is a layout system, not a text direction
Setting dir="rtl" flips text and starts the argument. Navigation order, breadcrumbs, progress steps, sliders, form alignment, icon direction, chart axes and animation origin all need deliberate decisions. Meanwhile numerals, telephone numbers, email addresses, currency codes and Latin brand names stay left-to-right inside a right-to-left sentence. Use logical CSS properties — inline-start and inline-end rather than left and right — and the two directions can share one stylesheet honestly.
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.
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.
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.
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.
Content-first, not template-first
Design around real copy, real product names and real image assets. Layouts built on placeholder text collapse when Arabic headings run longer than the English mock or a product name has fourteen words. Ask for the content before the visual sign-off; it changes the design, and it changes it far more cheaply at that stage than after development.
If you cannot state what a page is for in one sentence, it will not rank and it will not convert.
Arabic fonts are a performance decision
A full Arabic typeface can weigh several hundred kilobytes because of the glyph count and contextual forms. Subsetting to the ranges you actually render, using font-display: swap, self-hosting rather than calling a third-party origin, and preloading only the weights above the fold together take a second or more off first paint on a mid-range Android device — which is what most of the Kingdom is browsing on.
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.
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.
Hreflang without the usual mistakes
Use ar-SA and en plus an x-default. Every annotation must be reciprocal — if the Arabic page points to the English one, the English page must point back, or the whole set is discarded. Point at canonical URLs only. Do not mix hreflang with a canonical that points to the other language. And remember hreflang selects between versions; it does not create authority. A thin Arabic page still ranks like a thin page.
Vision 2030 without the cliché
Every second Saudi brand deck now shows the same palette of desert gradients and geometric patterns. Differentiation comes from specificity, not from national iconography: your own story, your own proof, your own tone. Reference the national context where it genuinely shapes your offer, and resist it where it would make you indistinguishable from the competitor pitching in the next meeting room.
What to verify first
- Add a WhatsApp route to a human on every page
- Increase Arabic line height by roughly 10–15% relative to the Latin scale
- Replace stock imagery with photographs of the actual team, office or work
- Confirm tap targets are at least 44 pixels and nothing depends on hover
- Check contrast ratios survive direct sunlight on a phone screen
- Use logical CSS properties — inline-start and inline-end — instead of left and right
- Subset and self-host Arabic fonts, and preload only above-the-fold weights
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.
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.
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.
None of this is complicated. It is, however, cumulative — the results come from doing the whole sequence for several quarters rather than doing the exciting parts for one. Start with the measurement baseline, fix what is broken, then build.
