International SEO is a set of measures for promoting a website to audiences in different countries and languages. It involves more than simply translating content: URL structure, hreflang configuration, geotargeting in Search Console, and adapting content to local needs all affect visibility in each country. This guide covers the key aspects of international SEO.
Goals of international SEO
- Multilingual — one website, multiple languages (for example, Russian, English, German)
- Multiregional — targeting different countries (Russia, Kazakhstan, Belarus)
- Combined — different languages and regions (en-US, en-GB, de-DE, ru-RU)
The setup approach depends on your goals. A website for Russian and Kazakhstani audiences in Russian is multiregional. A website in Russian, English, and German is multilingual.
Choosing a URL structure
There are three main options:
Subdirectories (recommended)
example.com/ru/
example.com/en/
example.com/de/Pros: One domain, consolidated link equity, simple setup. Cons: More difficult to geotarget by domain.
Subdomains
ru.example.com
en.example.com
de.example.comPros: Clear separation, option to use different hosting providers. Cons: Link equity is split across subdomains, more technical work.
Separate domains
example.ru
example.de
example.co.ukPros: Strongest local signal for search engines. Cons: Link equity is split, and maintaining multiple domains is more complex.
Google states that it does not favor any particular structure. The choice depends on resources, branding, and existing infrastructure. Subdirectories are the most versatile option.
Configuring hreflang
Hreflang is critical for multilingual websites. Without it, Google may:
- Show the wrong language version
- Treat versions as duplicates
- Dilute indexing across versions
For detailed configuration, see the hreflang guide. In brief:
- Each page links to all versions (including itself)
- x-default is specified
- Correct ISO codes are used
- URLs are absolute
You can check the markup with the hreflang tool on reChecker.
Geotargeting in Google Search Console
Configure geotargeting for subdomains and separate domains:
- Search Console → Settings → International targeting
- Select the domain/prefix
- Specify the target country
Geotargeting by URL is not supported for subdirectories (example.com/ru/). Regional signals come from content, hreflang, server geolocation, and other factors.
Content for international SEO
Translation vs. localization
Translation conveys meaning in another language. Localization adapts content to culture, units of measurement, date formats, examples, and legal considerations.
Localization is necessary for a serious international presence. “The product costs 1000 rubles” on an English version for the US should be “Product costs $11”, taking the exchange rate and currency into account.
Keywords by market
Keywords differ by country. “Купить ноутбук” and “buy laptop” are different queries. “Laptop” in the US and “notebook” in Germany are different, too. Research keywords separately for each market.
Content and duplication
The same content in different languages is not duplication. Google distinguishes between language versions. However, unedited machine translation may be considered low-quality content.
Technical aspects
Page language
Specify the language in HTML:
<html lang="ru">For pages in multiple languages, use the language of the main content.
Server geolocation
For multiregional websites, having a server in the target country may provide a small advantage. A CDN with points of presence in different regions improves speed for local audiences—this affects Core Web Vitals and indirectly affects SEO.
International accessibility
The website should be accessible from target countries without blocks. Check accessibility using a proxy or services that test from different regions.
A comprehensive technical review is provided by the reChecker technical audit.
Content structure by market
Centralized vs. decentralized
Centralized: One domain, all languages. Content is managed in one place. Suitable for medium-sized websites.
Decentralized: Separate domains/subdomains with local teams. Suitable for large international brands with local content and marketing.
Content available in only some markets
Some pages may not exist in all languages. For example, a service may be available only in Russia, so an English version is not needed. In this case, hreflang should not link to non-existent versions. The set should include only URLs that actually exist.
Avoiding common mistakes
| Mistake | Solution |
|---|---|
| One domain with no language indication | Add hreflang and lang in HTML |
| Redirecting to one language based on IP | Use hreflang and let users choose |
| Automatic translation without editing | Localize the content |
| Different URLs for the same content without hreflang | Configure hreflang |
| Geotargeting the wrong country | Check Search Console settings |
International SEO checklist
| Stage | Actions |
|---|---|
| Strategy | Identify target markets and languages |
| Structure | Choose subdirectories, subdomains, or domains |
| Technical setup | Configure hreflang, lang, canonical |
| Content | Localize and research keywords by market |
| Search Console | Add all versions and configure geotargeting |
| Monitoring | Track indexing and rankings by country |
Local search engines
Yandex
Yandex is critical for Russian-speaking audiences. It supports hreflang. Geotargeting is configured through Yandex Webmaster. Consider regional targeting during setup.
Baidu, Yandex, Naver
China (Baidu), Russia (Yandex), and Korea (Naver) have local search engines with their own rules. If targeting these markets, review each search engine’s requirements.
Bing and international search results
Bing supports hreflang and is used by Yahoo and DuckDuckGo. Configuration is similar to Google’s.
Content strategy by market
Prioritizing languages
Not all languages are equally important. Define Tier 1 (primary markets), Tier 2 (growing markets), and Tier 3 (experimental markets). Prioritize content and localization for Tier 1.
Adapting to local queries
The same query may be phrased differently in different countries. Both “SEO” and “поисковая оптимизация” are used in Russia. Research search volume and phrasing separately for each market.
Local trends and seasonality
Black Friday in the US, sales in China (11.11), and local holidays—all mean that content and promotions should take each market’s calendar into account.
Technical infrastructure
Domain and SSL
Use a separate SSL certificate for each domain. Wildcard certificates simplify management for subdomains.
Hosting and CDN
A server in the target country or a CDN with points of presence reduces latency. For audiences in Europe, Asia, and the Americas, use a multiregional CDN.
Language switchers
The language switcher should be easy to find and link to the corresponding versions. Check that all pages have language alternatives (or that the absence of a version is clearly indicated).
Measurement and reporting
Metrics by country
Set up separate goals in Analytics by country. Track conversions, traffic, and pages per session for each market. Compare the performance of language versions.
Indexing by version
Use the Search Console report by country to see how many pages are indexed for each language. Hreflang issues are shown under “International targeting.”
A/B testing localization
Test wording, structure, and CTAs across markets. What works in one country may not work in another.
Legal and cultural considerations
GDPR and local laws
For European audiences, consider GDPR. Websites for the EU must comply with requirements for cookies, consent, and personal data. Other regions have their own regulations.
Local currency and payment methods
Display prices in the local currency. Support local payment systems (UnionPay in China and local methods in different countries).
Cultural adaptation
Colors, images, and gestures have different meanings across cultures. Visual localization is just as important as text localization.
Tools
- Google Search Console — international targeting, indexing by country
- Google Analytics — traffic geography, browser language
- reChecker hreflang — markup validation
- reChecker Tech Audit — technical review of a multilingual website
Case studies and examples
Case study: E-commerce site in three languages
A product website in Russian, English, and German. Structure: subdirectories /ru/, /en/, /de/. Hreflang on all product and category pages. x-default points to the English version. Geotargeting through content and hreflang (subdirectories do not support geotargeting in GSC). Result: search results show the correct language for each country.
Case study: Geolocation-based redirect
The website detected the country by IP and redirected users to /ru/ or /en/. Problem: search engines could see only one version. Solution: remove the IP-based redirect for bots and add hreflang. Let users choose a language using a switcher. Both versions are available through direct links.
Case study: Partial content by language
The blog is in Russian; services are in Russian and English. Hreflang for service pages includes ru and en. For blog articles, hreflang includes only ru (there are no English versions). Do not add non-existent URLs to hreflang.
Related materials
For technical hreflang configuration, see the complete hreflang guide. Common mistakes and fixes are covered in the hreflang errors article. Check the markup and technical status using the hreflang tools and the technical audit on reChecker.