Short answer: A multilingual real estate website is a structure built with a separate URL, separate content and correct hreflang tags for each language. Browser translation or plugins that switch language on a single page are not counted as separate pages by search engines, so international buyers cannot find you in their own language. Rebel Co. Group publishes each language in its own folder with its own title and description, and links the language versions to each other with hreflang.
When a company decides to sell to international buyers, its first move is usually to add a language menu to the site. Most of the time this means installing a translation plugin and translating pages automatically. The result: the site looks multilingual, but search engines do not show those pages to the right audience, and buyers do not trust what they read.
In this article we cover how a multilingual real estate website is really built, from technical decisions to content decisions.
URL structure: the first and most permanent decision
This is the most expensive decision to change later, because changing it means every address changes. There are three options.
| Structure | Example | Pros | Cons |
|---|---|---|---|
| Subdirectory | example.com/ru/ | Authority stays on one domain, simple setup | Weaker country targeting |
| Subdomain | ru.example.com | Easier separate management | Splits authority, needs a separate setup |
| Separate domain | example.ru | Strongest country signal | Each domain builds authority from scratch, high cost |
For most real estate companies the right answer is a subdirectory. A separate domain only makes sense if you are going to build a permanent, separate operation in that country.
Hreflang: the most common and quietest mistake
Hreflang is the tag that tells search engines about the different language versions of the same content. When it is set up wrong you get no error message at all. The wrong page is simply shown to the wrong user, and it takes months for you to notice.
- Every version must point to all the other versions and to itself. One-way annotations are treated as invalid.
- An x-default should be defined to specify which page is shown when no language matches.
- Do not confuse language codes with country codes. Russian speakers do not live only in Russia.
- Untranslated pages should not be included in hreflang. Pointing to an empty or half-finished page does harm.
Temporarily keeping pages without a finished translation out of the index is safer than going live with half-finished content. Sefa Aydın explains the limits of speeding up multilingual production with AI in his article on multilingual content production.
Localization: more than translation
Real localization does not end with changing the language of the text. Every element the buyer needs to make a decision has to be brought into their context.
- Currency: Prices in the currency the buyer decides in. Showing only Turkish lira makes comparison difficult.
- Units of measurement: Square meters are understood in most markets, but what the area figure covers (gross or net) should be stated clearly.
- Process explanation: Title deed, valuation and payment steps should be explained with concepts that buyers from that country already know.
- Contact: The promise of an advisor who speaks that language, and a response commitment that takes the time zone difference into account.
- Legal content: Citizenship and residence permit information should be accurate and not exaggerated. The minimum amount for citizenship by investment is $400,000, a three-year no-sale annotation is recorded on the title deed and the valuation is carried out by an SPK-licensed firm.
Search engine setup is done separately for each language
This is the most frequently skipped step of a multilingual site. Google Search Console gets set up and the work stops there. Yet if you are targeting Russia, you also need a separate setup on Yandex, since about 70 percent of searches in Russia go through Yandex.
- Google Search Console: submitting the sitemap and monitoring the international targeting report.
- Yandex Webmaster: separate verification and sitemap submission for the Russian version.
- Bing Webmaster: feeds both Bing and some AI interfaces.
- A separate sitemap for each language, or hreflang alternates defined within a single sitemap.
Performance: a slow site is even slower abroad
A site that looks fast from Turkey can slow down noticeably when opened from Moscow or Dubai. Because real estate sites are image-heavy, this risk is high. Serving images in modern formats, using a content delivery network and removing unnecessary scripts directly affect conversion. We covered this topic in detail in our article on site speed and Core Web Vitals.
What it looks like in practice
The structure we built for Realty Galaxy Global is live in nine languages and includes a VIP portal for investors, a live exchange rate integration and a separate lead management interface. For Istanbul Citizenship we built a structure that explains the process step by step, published with an English main version and five additional languages, and we completed the search console setup.
The real lesson here is not the number of languages. It is that every language version should be an asset that stands on its own and genuinely answers someone searching in that language. Nine half-finished languages bring in less business than two complete ones.
The measure of a multilingual site is not how many languages you launch, but how many languages you can genuinely answer buyers in.
If you want to build your structure or audit your current setup, talk to Rebel Co. Group. Related services: web design and SEO consulting.
Frequently asked questions
Which URL structure should a multilingual site use?
The most common and manageable structure is a subdirectory, such as example.com/ru/. The domain's authority stays in one place and the setup is relatively simple. A subdomain or a separate country-code domain is also possible, but it splits authority and needs more maintenance.
What is hreflang and why do you need it?
Hreflang is a tag that tells search engines about the versions of the same content in different languages. If it is not set up correctly, a search engine may show a Russian user the Turkish page or treat the versions as duplicate content. Every version should point to all the others and to itself, and an x-default should also be defined.
Is using machine translation harmful?
Publishing raw machine translation creates two problems: it damages trust in a high-stakes decision, and it sends a low-quality content signal to search engines. Using machine translation as a draft and having someone who knows the language edit it is a reasonable approach. Publishing it without any editing is not.
Which currency should I show prices in?
In the currency the buyer makes decisions in. International investors mostly think in dollars or euros, and showing amounts only in Turkish lira makes it harder for them to compare. Offering a currency option and stating the date of the exchange rate builds trust.