Multilingual Website SEO: A Practical Guide to hreflang, URLs and RTL

Adding languages to a website looks simple: translate the pages, add a language switcher, done. Then the problems surface — Google shows the English page to Arabic searchers, translated pages compete with each other, and rankings stall in every market at once. Multilingual SEO is mostly about getting a handful of structural decisions right before launch. This guide walks through them in order.

1. Choose the Right URL Structure

Search engines need one unambiguous URL per language version. There are three workable patterns:

Structure	Example	Best for
Subdirectories	example.com/en/, /ar/	Most sites — consolidates domain authority, simplest to run
Subdomains	ar.example.com	Teams operating each market separately
Separate ccTLDs	example.ae	Strong local legal/branding needs and a budget to match

For most manufacturer and B2B sites, subdirectories are the right answer. They keep all SEO equity on one domain, and adding a language later is a routing change rather than a new infrastructure project. Avoid the one genuinely bad option: serving different languages on the same URL based on cookies or browser settings. Search engines crawl without your cookies and will only ever see one version.

2. Implement hreflang Without the Classic Errors

The hreflang annotation tells search engines which language versions of a page exist and which audience each serves. It is the most error-prone part of international SEO, and most failures come from four mistakes:

• Missing return links. If /en/products points to /ar/products, the Arabic page must point back. One-directional annotations are ignored.
• No self-reference. Each page must include itself in its own hreflang set.
• No x-default. Always declare a fallback version for visitors who match none of your languages.
• Annotating redirects or noindexed pages. Every URL in an hreflang set must be a real, indexable page.

The practical lesson: do not manage hreflang by hand. Generate it from your routing system, so every page automatically declares its full language set. This is a strong argument for building multilingual support into the site architecture rather than bolting it on with plugins.

3. RTL Is a Layout Project, Not a Translation Project

If the Middle East is one of your target markets, Arabic support means full right-to-left layout: mirrored navigation, reversed icon direction, flipped spacing and alignment, and careful handling of mixed content such as English part numbers inside Arabic sentences. Retrofitting RTL onto a site designed left-to-right is expensive; building with logical CSS properties from day one makes it nearly free. If Arabic is on your roadmap at all, decide this before development starts — it is one of the clearest cases where a custom-built site outperforms template platforms, whose RTL support is often an afterthought.

4. Translate for Buyers, Not for Word Counts

Google's guidance and buyer behavior point the same direction: pages that read like machine output neither rank well nor convert. For B2B sites, three rules keep quality high without exploding costs:

• Localize commercial vocabulary. Terms like MOQ, lead time, and product category names have established equivalents in each market. A literal translation of your English phrasing often reads as translationese and erodes trust.
• Machine-translate the first draft, then have a native or industry-experienced reviewer fix it. This hybrid keeps cost reasonable while catching the errors that matter.
• Prioritize depth by page value. Product pages and the inquiry flow deserve full localization. Blog archives can wait.

Also translate the metadata — titles, descriptions, image alt text, and URL slugs where practical. A perfectly translated page with an English title tag is only half done.

One more step separates adequate localization from effective localization: keyword research in the target language. The term your English page ranks for is not necessarily what buyers type in Arabic or Russian — a literal translation of your main keyword can have a fraction of the search volume of the phrase local buyers actually use. Before finalizing page titles and headings for a new language, spend an hour checking what real search suggestions and competitor pages in that market look like, and write the metadata around those native terms rather than translated ones.

5. Watch Each Market Separately After Launch

Verify the site in Google Search Console and review performance filtered by country and by language directory. The typical pattern after a correct multilingual launch: impressions rise within weeks as each language version starts appearing in its own market's results, then clicks follow as rankings settle. If one language shows impressions but the wrong pages are ranking, that usually signals an hreflang gap — check the return links first.

Also remember that Google is not the only search engine that matters internationally. If Russian-speaking markets are a priority, Yandex has meaningful share; the good news is that the same clean URL structure, sitemaps and hreflang annotations serve it as well. Solid fundamentals travel across search engines better than any engine-specific trick.

Launch Checklist

Item	Done
One indexable URL per language, subdirectory structure	☐
hreflang generated automatically, with self-reference and x-default	☐
Sitemap lists all language versions	☐
RTL layout verified on real pages, not just the homepage	☐
Titles, descriptions and alt text translated	☐
Language switcher links to the equivalent page, not the homepage	☐

Conclusion

Multilingual SEO rewards getting the architecture right once: clean URLs, automated hreflang, native-quality copy on the pages that convert, and RTL planned from the start. We build multilingual B2B sites with all of this in place by default — including a live four-language project with full Arabic RTL you can inspect in our portfolio. Planning a multilingual site or fixing one that underperforms? Contact us for a free consultation.