SEO localization explained: why translation is not enough, how to research keywords per market, set up URLs and hreflang, and get cited by AI in each language.

In short
SEO localization adapts a website to how people search in each target market: their words, their intent, their units, prices and references, and the signals search engines use to pick the right version. Translation converts the text; localization starts from fresh keyword research per market, then adapts content, URLs, hreflang annotations and local trust signals. It decides whether a translated page ranks for queries people actually type, and whether AI assistants cite it in that language.
Want to go further? Ask
A translated page can be perfectly written and still invisible. The usual reason: it targets a literal translation of an English keyword that nobody types in that country. SEO localization fixes this by treating each language and market as its own search landscape. This guide covers the difference with translation, the localization process step by step, the technical setup that Google documents and what changes when AI assistants answer in several languages. For the broader strategy (choosing markets, domain structure), see our guide to international SEO.
Language drives buying decisions. In CSA Research's "Can't Read, Won't Buy" survey of 8,709 consumers in 29 countries, 76% of online shoppers prefer to buy products with information in their own language, and 40% never buy from websites in other languages (CSA Research, 2020). For search, the stakes are simpler still: a page that does not use the words of the market does not match its queries.
Localization also changes which pages compete. The same topic can be dominated by forums in one country, by retailers in another and by public institutions in a third, so the format that wins the top 10 differs too.
| Element | Translation | SEO localization |
|---|---|---|
| Keywords | English keywords translated word for word | New keyword research in each market, then mapping to pages |
| Search intent | Assumed identical everywhere | Checked in local results: format and angle can differ |
| Examples and references | Kept from the source | Replaced with local brands, laws, institutions, holidays |
| Units, prices, formats | Converted mechanically, or not at all | Local currency, units, date and number formats, local prices |
| Metadata and slugs | Often left in English | Title, meta description, slug and alt text in the target language |
| Technical signals | Often missing | Separate URLs, hreflang, canonical tags, language switcher |
| Trust signals | Absent | Local reviews, addresses, payment methods, local links and mentions |
Translation remains the base of the work, and machine translation now produces a good first draft. Localization is what turns that draft into a page that matches local search intent.
Start from the topics, not from your English keyword list. For each market, run keyword research in the local language and location: seed terms, related searches, autocomplete, local competitors. Common surprises: a borrowed English term more searched than the native word (or the reverse), regional variants (Spain versus Mexico, France versus Quebec), and different words for the same product. When two phrasings compete, compare them in the target country with Google Trends.
Assign one primary keyword per page in each language, following your keyword strategy. Some pages will not need a local version (no demand), and some markets will need pages that do not exist in English (local regulations, local use cases). A one-to-one copy of the English site is rarely the right map.
Search each primary keyword in the target country and language. If the local top 10 favors comparison tables, calculators or official sources, adapt the format. This step avoids publishing an English-style guide where locals expect something else.
Use translation for the base, then have a native speaker or reviewer adapt: examples, legal references, prices and currency, units, holidays and seasons, tone and level of formality. Website translation software handles the volume; the review handles the meaning. Keep a style guide per language, and if you use AI to write, a brand voice profile per language keeps the tone consistent.
Translate the title tag, meta description, headings, slugs, image file names and alt text. A French page with an English slug and English alt text sends mixed signals and looks unfinished in the results.
Show local reviews, local contact details and payment methods, and earn links and mentions from sites of the market. Google lists local addresses and phone numbers, local language and currency, and links from other local sites among the signals that help identify a site's intended audience.
Google's guide to managing multi-regional and multilingual sites sets out the rules that matter most:
Our glossary entry on hreflang details the syntax, and a free hreflang generator builds the tags for every language pair. Each localized page should also carry a self-referencing canonical tag: pointing all versions to the English page would tell Google to ignore the translations.
| URL structure | Example | Main advantage | Main drawback |
|---|---|---|---|
| Country domain | example.de | Clear country signal | Cost, separate authority per domain |
| Subdomain | de.example.com | Easy to host separately | Users may not read the language from the URL |
| Subfolder | example.com/de/ | Shares the authority of one domain, simple to maintain | Single server location |
| URL parameter | example.com?lang=de | None worth the cost | Not recommended by Google |
On WordPress, multilingual plugins handle URLs and hreflang automatically; our WordPress SEO and GEO page lists the settings to check.
AI assistants answer in the language of the question, and they do not cite the same sources in every language. Sorank's study of French and English AI citations, based on more than 300,000 answers, found that the same platforms carry different weight: Reddit, for example, appears in 0.93% of French answers against 2.28% of English ones. Being cited in English says little about being cited in French, German or Japanese.
Three consequences for GEO. First, each language needs its own clear, sourced pages: assistants quote passages written in the language of the user. Second, local sources (national media, local directories, local review sites) feed local answers, so mentions there matter. Third, measure each language separately: AI mention tracking run on prompts in each language shows where your brand appears and who is cited instead.
Localization starts with what each market searches for, not with what your English site says. Research keywords per market, adapt content and examples, give each language its own URL with correct hreflang and canonicals, then measure rankings and AI citations language by language. Sorank runs this per site and per language: its automated keyword research finds what each market searches, and its articles are written and published on autopilot, with a 3-day free trial. Discover how Sorank works.
It is enough for a first draft, not for a finished page. Machine translation keeps the source keywords, examples and units, which rarely match how people search in the target market. A native review, local keyword research and adapted examples turn the draft into a page that can rank.
No. Country domains, subdomains and subfolders all work with Google if each language version has its own URL and correct hreflang annotations. Subfolders on one domain are the simplest to maintain and share the authority of the main site; country domains give the clearest country signal but cost more to build up.
No. Localize the pages that have demand in the target market, starting with the pages that bring business: product or service pages, pricing and the main guides. Some markets will also need pages that do not exist in your source language, such as content about local regulations or local use cases.
THEY TRIED SORANK BEFORE YOU
