Multilingual websites: opening new markets without a Google penalty

When a Saudi company decides to serve customers beyond the local market, the first decision is usually: "let's add an English version of the site". And it is usually executed in the worst possible way — machine-translated text and a second copy of the site, then waiting for customers who never arrive.

A multilingual site is not a translation project; it is a technical architecture project. These four decisions determine whether it succeeds.

1. Hreflang: without it, Google thinks you are repeating yourself

When the same page exists in ten languages, Google needs an explicit signal saying: "these are not ten competing pages, they are language versions of one page — show each user the right one."

That signal is the hreflang tag. Without it, Google may treat the versions as duplicate content, pick one and ignore the rest — meaning you paid to translate ten versions for one to be seen. This is the most common and most expensive technical mistake in multilingual sites.

2. URL structure: three options, not one

• Subdirectories (site.com/fr/) — the right fit for most companies: all domain authority accumulates in one place, management is simpler, cost is lower.
• Subdomains (fr.site.com) — Google treats these as semi-independent, so authority must be built separately for each.
• Country domains (site.fr) — strongest for targeting one country, and far more expensive to run.

For a company beginning international expansion, subdirectories are the practical call in most cases.

3. Machine translation alone will hurt you

Unreviewed machine translation produces text that is grammatically fine and commercially strange. Worse, it translates words but not search intent: a German customer does not search the same term a French one does, even when the meaning is identical.

A concrete example: someone searching for Jeddah in German types "Dschidda", not "Jeddah". If your German version only says "Jeddah", you do not exist for that searcher. City and country names are written in each language's own convention, not copied across.

4. Real RTL support, not a mirrored template

If your site is originally Arabic and you add Latin languages — or the reverse — it is not just about flipping text direction. Icons, arrows, form order and button placement all change. Templates that "mirror" a design automatically produce broken interfaces that lose trust in the first second.

What actually needs translating?

Partial translation is worse than none. The full list includes:

• Meta titles and descriptions for every page — not just visible text.
• Image alt text.
• Form labels, submit buttons and error messages.
• Legal pages: privacy policy and terms.
• The sitemap, covering every language version.

A site translated 80% leaves a foreign visitor on a page half in their language and half incomprehensible — a worse impression than one clear single-language site.

When we advise against going multilingual

If you cannot actually serve the foreign customer — no international shipping, no team answering in their language, no payment method that suits them — translation will bring you enquiries you cannot close. Operational capability is built first; the website then reflects it.

In short

An additional language is not a translate button. It is a new acquisition channel with its own technical structure and its own keywords. Done right once, it opens an entire market — done quickly, it adds pages nobody visits.