International SEO: A Practical Guide to Multilingual and Multi-Regional Sites

Originally published: June 24, 2022 · Last updated: August 14, 2026

International SEO becomes important when a website serves people in more than one language, more than one country, or both. The difficult part is not translating a page. It is creating a structure that lets users and search engines understand which version belongs to which audience.

Google distinguishes between multilingual sites, which offer content in several languages, and multi-regional sites, which target users in different countries or regions. A website can be one, the other, or both.

Decide whether you need language versions, regional versions, or both

A French and English version of the same site is multilingual. Separate English pages for the United Kingdom and United States can be multi-regional even though both are written in English.

Do not create regional copies merely because you can. Separate versions make sense when the content genuinely differs: pricing, currency, shipping, legal information, product availability, terminology or local services.

If the same English page works for everyone, one strong version may be easier to maintain than several nearly identical regional pages.

Give each language version its own URL

Google recommends using different URLs for different language versions rather than changing the page only through cookies, browser settings or automatic redirects.

Common structures include:

• country domains such as example.fr and example.de;
• subdomains such as fr.example.com;
• subdirectories such as example.com/fr/.

Each model has tradeoffs. Country-code domains send a strong geographic signal but require more infrastructure. Subdirectories are often simpler for a small organization because one domain can share authority, analytics and maintenance.

Whatever structure you choose, keep it consistent. Do not mix several patterns without a clear reason.

Use hreflang for alternate language and regional versions

hreflang tells Google that several URLs are localized alternatives of the same or closely related content. It helps Google show the version that best fits the user’s language or region.

A language value uses a supported language code such as en, fr or de. You can optionally add a regional code, for example en-GB or en-US, when the pages are specifically targeted to those markets.

Do not invent codes such as en-UK. Language and region values need to follow the standards Google documents.

Hreflang annotations must be reciprocal

If page A identifies page B as an alternate, page B should identify page A as an alternate too. Each group should also include the page itself.

That reciprocal structure helps Google verify that the pages intentionally belong together. Broken or incomplete clusters are a common source of international SEO errors.

Use x-default when you have a neutral fallback

The optional x-default value can point to a language selector, global homepage or another fallback page for users who do not match one of the specified language or region variants.

It is not a replacement for the actual language annotations. Think of it as the default destination when none of the explicit versions is the obvious choice.

Keep one primary language on each page

Google determines a page’s language primarily from its visible content. Avoid building pages where navigation, headings and body copy constantly switch between languages unless that mixed-language experience is genuinely the purpose of the page.

Translate the whole user journey where practical: navigation, forms, buttons, error messages, checkout information and important supporting text. A translated article surrounded by an interface in another language is a poor experience even if the SEO markup is technically correct.

Do local keyword research instead of translating keywords literally

Search behavior does not translate word for word. Two markets can use different terminology for the same product or problem, even when they share a language.

Start with the meaning and intent of the original page, then research how the target audience actually describes that need. Titles, headings and descriptions should sound natural to the local reader, not like machine-translated SEO fields.

Do not rely on automatic location redirects

Locale-adaptive pages that change content based only on IP address, browser language or cookies can be difficult for Google to crawl completely. They can also frustrate travelers, multilingual users and people using VPNs.

Offer a visible language or region switcher and let users choose another version. Automatic suggestions can be useful, but avoid trapping visitors in a version they cannot easily leave.

Canonical and hreflang solve different problems

A canonical tag tells Google which URL is preferred among duplicate or very similar pages. hreflang identifies localized alternatives. They should not contradict each other.

For genuinely translated pages, each language version normally remains independently indexable and can be self-canonical. For same-language regional pages that are extremely similar, canonicalization requires more care because collapsing one page into another can affect how the localized versions are handled.

Do not apply a blanket canonical rule to every international site. Review the actual duplication and purpose of the pages.

Translate metadata and structured content where it helps users

Titles and meta descriptions should be localized for the audience. Image alt text, form labels and other meaningful text should also be translated when the image or interface serves the localized page.

Structured data should describe the page users actually see. If the price, currency, event location or organization details differ by region, keep those values consistent with the visible localized content.

Keep sitemaps and internal links coherent

Make sure localized URLs are discoverable through internal links and included in the appropriate XML sitemap. Do not create language versions that exist only in hreflang annotations but are otherwise isolated from the site architecture.

A language selector can also use normal crawlable links so visitors and search engines can move between versions.

Do not follow obsolete Search Console advice

Older international SEO guides often tell site owners to use the legacy International Targeting report in Search Console to set a target country or debug hreflang. That guidance is obsolete. Modern international SEO should be built around clear URLs, localized content, correct hreflang, appropriate domain choices and other current signals documented by Google.

Test international pages as a user

Technical markup is only part of the work. Open each version and check:

• Does the language switcher work?
• Does it send users to the equivalent page rather than always to the homepage?
• Are prices, currency and contact details appropriate?
• Are forms and validation messages translated?
• Does mobile navigation expose all language options?
• Are legal, shipping or service claims accurate for the target market?

A practical international SEO workflow

1. Define which languages and regions genuinely need separate experiences.
2. Choose one consistent URL architecture.
3. Create complete localized pages rather than partial translations.
4. Research terminology and search intent in each market.
5. Add reciprocal hreflang annotations.
6. Add x-default when a neutral fallback is useful.
7. Keep canonicals consistent with the localization strategy.
8. Localize titles, descriptions and important interface text.
9. Link localized versions normally and include them in sitemaps.
10. Test the complete user journey and monitor indexing.

The practical rule

International SEO is an information-architecture problem before it is a translation problem. Give each audience a stable URL, complete language experience and clear relationship to the other versions. The simpler and more consistent the system is, the easier it becomes to maintain as the site expands.

Official references: Google international and multilingual sites, Google localized versions and hreflang, and Google multi-regional site guidance.