This is a field guide to website maintenance plan for the Saudi market. No theory you can't act on, and no advice that assumes a US search landscape.
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.
The question underneath the question
The honest starting point for website maintenance plan 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.
Performance budgets prevent slow decay
Agree a maximum page weight, a maximum number of third-party scripts and a target for Interaction to Next Paint before development begins, then enforce them in review. Sites do not become slow in one release; they accumulate a chat widget here and a tracking pixel there until a fast build is a slow site two years later. A written budget is what stops that drift.
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.
Visibility is no longer a position on a page. It is whether the machine composing the answer considers you a source worth naming.
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.
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.
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.
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.
Speed is a conversion variable
Every additional second before content appears removes a measurable slice of conversions, and the effect is sharper on mobile connections. Before commissioning a redesign to fix conversion, check whether the current site simply loads too slowly. Performance work is cheaper, faster to deploy and more reliable in its effect than most creative changes.
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.
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.
Test the big thing, not the button colour
With modest traffic volumes you cannot detect small effects. Test changes large enough to move behaviour meaningfully: a different offer, a restructured page, a removed step, a changed payment option, a new proof element. Colour and copy micro-tests belong to sites with tens of thousands of weekly sessions; below that they generate noise that gets misread as insight.
What to verify first
- Place the language switch top-right in English and top-left in Arabic, preserving the current page
- Reduce the primary enquiry form to three fields
- Increase Arabic line height by roughly 10–15% relative to the Latin scale
- Confirm numerals, phone numbers and Latin brand names stay left-to-right inside Arabic text
- Check contrast ratios survive direct sunlight on a phone screen
- Set correct language attributes so screen readers pronounce Arabic properly
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.
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.
If you take one thing from this: measure the baseline before you change anything. Everything else on this page becomes arguable without it, and unarguable with it.
