Short answer: A proper KSA bilingual site is two real layouts — RTL Arabic and LTR English — not a machine-translated mirror. You need matching hreflang, local CTAs (often WhatsApp), and fonts that hold Arabic line-height. Bolting AR on after launch usually breaks nav, forms, and SEO.
What “bilingual” must mean
Separate URLs or a clean language switch with hreflang pairs (en-SA / ar-SA). Content that a human would actually send a customer — not raw MT. Forms that accept Arabic names and +966 numbers. Buttons that do not flip into the wrong corner.
RTL is layout, not a CSS flip
Icons, carousels, and absolute-positioned media need logical properties (inline-start / inline-end). If your package cards put images on the “end” side in English, they should stay on the end side in Arabic — physical left/right, not a broken mirror.
SEO and GEO for both languages
Each language needs its own title, meta, and answer-first intro. AI search and Google both prefer clear locale signals. Canonicals must not point AR pages at EN shells. FAQ blocks help both humans and citation engines.
WhatsApp still wins the CTA
Many KSA visitors will not fill a long form. A bilingual site that ends in a dead email link wastes the dual build. Deep-link WhatsApp with a short prefilled line in the visitor’s language.
How Viewkeeper ships it
We design mobile-first, then lock AR and EN strings together so neither language is a leftover. Packages list bilingual work toward the higher end of VK Site when both languages are in scope from day one.