The easy way to build a multilingual site is to install a translation plugin. The way that actually performs in search is different, and it has to be planned from the start.
The four most common mistakes
An auto-translation plugin. The page reads, but it is not original content to Google — and bad translation damages corporate trust directly.
Missing or one-way hreflang. On a three-language page each language must point to the other two and to itself. A one-way declaration is ignored, and the wrong language gets served to the wrong country.
All languages on one URL. If language switches by cookie, search engines only ever see one version; the others are never indexed.
Translated but not localized. If keyword research was only done in the source language, the other pages target phrases nobody searches for.
What a correct setup includes
- A separate, permanent URL structure per language
- Complete, reciprocal hreflang tags including x-default
- A sitemap per language, verified in Search Console
- Meta titles and descriptions written per language against local search intent, not translated
- A real RTL interface and bidirectional text support for Arabic
- Menus, forms, error messages and automated emails separated by language
- A language switcher that goes to the equivalent page, not to the homepage
Which stack
Polylang or WPML on WordPress, Shopify Markets or a multilingual WooCommerce build for commerce, or language handling at the application layer for custom software. Which one fits depends on your current stack and content volume — we make that choice with you, not for you.
This site is the example
The page you are reading is published in Turkish, English and Arabic on exactly this setup: a URL per language, three-way hreflang, per-language meta, and a real RTL Arabic interface. The language switcher takes you to this page’s equivalent, not to the homepage.
Get in touch — we will review your current multilingual setup and send you the errors we find, free of charge.