A working guide to web design madinah for companies operating in Saudi Arabia — grounded in local search behaviour, local regulation and what we see across client accounts.
A website in Saudi Arabia has to work twice: once in Arabic and once in English, on a mid-range phone, for a buyer who will check your commercial registration before filling in a form. Design decisions here carry commercial weight that they simply do not in single-language markets.
What makes Madinah different
Madinah is a pilgrimage and education hub with year-round visitor traffic and a fast-growing hospitality sector. That shapes demand in concrete ways: the terms people use, the seasonality of enquiries, the competitors already visible, and the level of Arabic-first content required to compete. A national strategy applied uniformly across the Kingdom under-performs in Madinah for exactly this reason — the market has its own rhythm, and the businesses winning here built for it deliberately rather than inheriting a Riyadh plan.
The question underneath the question
Most teams arrive at web design madinah after something stopped working: enquiries fell, a competitor became visible, or a target was missed. That context matters, because the right first move differs depending on whether you are fixing a decline or building from a standing start. Diagnose which situation you are in before applying anything below — the sequence changes completely, and applying a growth playbook to a decline problem wastes a quarter.
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.
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.
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.
Accessibility is legibility for everyone
Contrast ratios that survive sunlight on a phone screen, focus states that are visible, semantic headings, labelled form fields, alt text in the page language, and no information conveyed by colour alone. In Arabic, ensure screen readers receive correct language attributes so pronunciation is right. Accessible pages are also cleaner for crawlers and AI extraction — the same structural discipline serves both.
Compliance built in during design costs a fraction of compliance retrofitted after enforcement.
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.
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.
Statistical honesty
Decide the sample size and duration before starting. Run full weeks to cover behavioural cycles — Thursday and Friday behave very differently from Sunday in this market. Do not stop the moment a variant looks ahead. Most reported CRO wins evaporate because the test was called early on an underpowered sample, and the organisation then builds strategy on a coin flip.
Rebranding: justified or vanity?
Legitimate triggers include a genuine change in what you sell, a merger, a market you can no longer credibly address, or an identity that fails technically in digital contexts. Boredom is not a trigger. When it is justified, plan the migration seriously: domains, redirects, profiles, signage, documents, email, app listings and directory entries all move together, or the equity you built leaks away during the transition.
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.
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.
Diagnose before you test
Running experiments without a hypothesis wastes traffic that most Saudi mid-market sites cannot spare. Start with session recordings, funnel drop-off in GA4, heatmaps and five customer interviews. You are looking for the one screen where intent dies. Nine times out of ten it is a form, a price ambiguity, a missing trust signal or a mobile layout failure — and it is visible within an afternoon of watching real sessions.
The Saudi checkout reality
Cash on delivery still carries a meaningful share of transactions and it is expensive — failed deliveries, tied-up stock, reconciliation cost. Move volume to prepaid by making Mada, Apple Pay and BNPL visibly available at the top of checkout, offering a small prepaid incentive, and building enough delivery confidence that customers stop using COD as insurance. Reducing COD share is usually worth more than a conversion-rate uplift of the same size.
A checklist you can run this week
- Show the commercial registration number, national address and a landline
- Set a performance budget for page weight and third-party scripts, then enforce it in review
- Increase Arabic line height by roughly 10–15% relative to the Latin scale
- Test the Arabic layout for correctly mirrored navigation, breadcrumbs and progress steps
- Add a WhatsApp route to a human on every page
- Reduce the primary enquiry form to three fields
- Confirm the success message after form submission says what happens next and when
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.
Serving Madinah specifically
Practical adjustments that matter in Madinah: name the districts you serve in your content and profile; publish prices in riyals with local context; show work delivered for recognisable local clients where permission allows; and make sure a person can reach you on WhatsApp during the hours Madinah customers actually enquire. None of this is expensive. All of it is visible to a buyer comparing three suppliers, and it is the part competitors most often skip.
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.
