How to Do Multilingual SEO Effectively

This guide is for businesses that want to rank in more than one language: an exporter adding Arabic and French, a Pakistani brand serving customers in English and Urdu, or a SaaS company translating its product pages. I have kept it to what actually decides whether multilingual pages rank, in the order I set them up for clients, with a checklist and a hreflang workload calculator at the end of the technical section.

Multilingual SEO vs international SEO

The two terms get mixed up, and the difference changes your setup:

• Multilingual SEO targets languages. A Canadian site in English and French, or a Lahore retailer in English and Urdu, serves different languages to people who may live in the same country.
• Multi-regional (international) SEO targets countries. A UK and an Australian version of an English site differ by currency, spelling, shipping and law, not by language.

Many sites need both, which is why hreflang supports language-only codes such as fr and language-plus-region codes such as fr-CA. If you are targeting countries as well as languages, my guide to multi-country website SEO covers the regional side in more depth.

Step 1: Decide which languages are worth it

Each language is a second website to maintain. Before translating anything, I check three things:

1. Existing demand: in Google Analytics, look at visitors by browser language and country. In Search Console, filter queries by country and look for searches in other languages you already get impressions for.
2. Search volume in the target language: research it natively (step 3), not by translating your English keyword list.
3. Ability to serve: can you answer enquiries, process orders and handle support in that language? A French site that replies to French emails in English loses the sale anyway.

Start with one extra language, prove it works, then add more. Half-finished languages with 20% of pages translated create more problems than they solve.

Step 2: Choose a URL structure

Google’s guidance on multi-regional and multilingual sites says to use different URLs for each language version, rather than cookies or browser settings that change the language on the same URL. That rules out the common plugin pattern of one URL that swaps language by session. The real choice is between these options:

For the clients I work with, subfolders are the default answer. I compare all three in detail in ccTLD vs subfolder vs subdomain. Whatever you pick, keep the structure parallel: if the English page is /services/seo-audit/, the French one should be /fr/services/audit-seo/, with a translated slug.

Step 3: Research keywords in each language

Direct translation of keywords is the most common mistake I see. People rarely search the way a dictionary translates. Some examples of the gap:

• German searchers often use the English loanword “Software” or “Online Marketing” rather than a German translation.
• Spanish in Mexico and Spanish in Spain use different words for everyday items (a mobile phone is usually “celular” in Mexico and “móvil” in Spain).
• In Pakistan, many people search in Roman Urdu (“sasta mobile price”, “ghar ke liye solar”) as well as in Urdu script and English, so an Urdu page in Nastaliq script may miss a large share of searches typed in Latin letters.

The method I use: write a seed list with a native speaker, check volumes in a keyword research tool set to the right country and language, look at the actual results page in that language to confirm intent, and only then assign keywords to pages. My guide to international keyword research walks through this with tools.

Step 4: Translate and localise the whole page

Google is clear that it decides a page’s language from its visible content. If you translate only the navigation and footer and leave the main text in English, the page is still English to Google, and a poor result for the searcher. Translate the main content, then localise:

• Units, dates, currency and phone formats: PKR vs AED vs EUR, DD/MM vs MM/DD, local phone numbers with country codes.
• Examples and images: swap culturally specific references and screenshots with English interface text.
• Titles, meta descriptions, slugs, alt text and schema: all in the target language. These are the first things searchers see in results.
• Right-to-left languages: Urdu and Arabic pages need dir="rtl", a readable font, and a layout tested on mobile.

Can I use machine translation or AI?

Yes, as a first draft. The risk is publishing unreviewed output at scale. Google’s spam policies list “automated transformations like synonymizing, translating” of content that provides little value as an example of scaled content abuse. My rule is simple: machine-translate if it saves time, but have a fluent speaker edit every page before it goes live, and translate fewer pages well rather than every page badly.

Step 5: Set up hreflang correctly

Hreflang tells Google which language versions belong together, so it can show the French page to French searchers and the English page to English searchers. Google’s localized versions documentation sets the rules: each version must list itself and every other version, links must be returned (if page X points to page Y, page Y must point back), and codes must be ISO 639-1 language codes with optional ISO 3166-1 Alpha 2 region codes.

<link rel="alternate" hreflang="en" href="https://example.com/services/seo-audit/">
<link rel="alternate" hreflang="ur" href="https://example.com/ur/services/seo-audit/">
<link rel="alternate" hreflang="ar-AE" href="https://example.com/ar-ae/services/seo-audit/">
<link rel="alternate" hreflang="x-default" href="https://example.com/services/seo-audit/">

The same block goes on all three pages. Each page also keeps a self-referencing canonical tag; never canonicalise the Urdu page to the English one, or the Urdu page drops out of the index. You can build and check tags with my free hreflang tag generator and checker, and the basics are explained in what is a hreflang tag.

On large sites the tag count grows fast, which is why I often move hreflang into the XML sitemap. Use this to see your workload:

Step 6: Language switching, links and redirects

• No forced redirects: Google advises against automatically redirecting users to a language version based on a guess. Googlebot mostly crawls from the US, so IP redirects can hide your other languages from it. Show a polite banner suggesting the visitor’s language instead.
• A visible language switcher: plain links to the equivalent page in each language (not the homepage), labelled in the language itself, such as “Français” and “اردو”, not with flags.
• Internal links stay in language: French pages link to French pages. Mixed-language menus are a common leftover from partial translations.
• Sitemaps: include every language version, and submit them in Search Console. My sitemap validator flags broken entries before you submit.
• Links from each market: local-language links and mentions help each version earn authority; see my guide to international link building.

Multilingual SEO checklist

Mistakes I see on multilingual sites

• Hreflang pointing to redirected or noindexed URLs: Google ignores those pairs. Point only to final, indexable, 200-status pages.
• Wrong codes: “uk” for the United Kingdom (it is Ukrainian; use en-GB) or “pk” as a language (it is a region code; Urdu is ur, so use ur-PK).
• Translating only the template: 30 “French” pages with English body text.
• One language switcher link to every homepage: visitors lose their place and leave.
• Measuring only the total: a growing English section can hide a French section that never took off. Filter the Search Console performance report by the /fr/ folder.

Frequently asked questions

Sources

• CSA Research, “Survey of 8,709 consumers in 29 countries finds that 76% prefer purchasing products with information in their own language” (July 2020).
• Google Search Central, “Tell Google about localized versions of your page” (last updated September 2026).
• Google Search Central, “Managing multi-regional and multilingual sites” (last updated December 2025).
• Google Search Central, “Spam policies for Google web search” (accessed 2026).

If you are planning a new language or your translated pages are not ranking, my international SEO services cover hreflang audits, keyword research and rollout plans, or you can send me your site and the languages you are targeting.