SEO Localization: How to Rank in Another Language or Country (Keywords, URLs, Hreflang)

SEO localization is adapting a website so it ranks in another language or country: researching the keywords native speakers actually type, adapting the content, metadata and URLs to that market, and telling search engines which version is for whom with hreflang and a clear URL structure. It is not the same as translation. A translated page targets the words you used in English; a localized page targets the words people search for in that market.

This guide walks through the process in order: picking markets, choosing between ccTLDs, subdirectories and subdomains, localizing keyword research, localizing each page element, implementing hreflang, and measuring the result.

#SEO localization vs translation vs local SEO

Three terms get mixed up constantly. They solve different problems.

You can do local SEO without localization (one city, one language) and localization without local SEO (a SaaS selling across Europe with no physical location). If you sell physical services in several countries, you need both.

#Step 1: Pick your markets

Start with the markets where you already have demand. In Google Search Console, open Performance → Search results → Countries and sort by impressions. Countries with impressions but few clicks show people already searching for what you do and landing on a page in the wrong language.

Then decide what you're targeting: a language (all Spanish speakers) or a country (Spain specifically, with euro prices and Spanish shipping). Country targeting is more work but necessary when prices, laws, delivery or product ranges differ.

Check which search engine the market uses. Google dominates worldwide, but not everywhere:

Source: StatCounter Global Stats, all platforms. Yandex, Naver and Baidu each have their own webmaster tools and ranking quirks; our list of alternative search engines to Google covers the main ones.

One more reason to look beyond English: W3Techs finds that 49.5% of websites with a known content language are in English, against 6.1% in Spanish, 5.9% in German and 4.5% in French (October 2026). Many non-English markets have fewer pages competing for the same intent.

#Step 2: Choose a URL structure

Google's multi-regional sites documentation compares four options:

For most businesses, subdirectories win: every link to any language version strengthens the same domain, and there's one site to maintain. ccTLDs make sense for big brands with a local team, budget and link building per country. Answer four questions to see which fits you.

Whichever you choose, Google says to give each language version its own URL rather than switching content by cookie or browser setting.

#Step 3: Localize keyword research

Translating your keyword list is the most common localization mistake. Search vocabulary varies even between countries that share a language:

A process that works:

1. Start from intent, not words. List the problems and products your English keywords represent.
2. Have a native speaker brainstorm the terms they'd type for each one, including slang, abbreviations and anglicisms people use.
3. Check volumes in the right database. In Google Keyword Planner, set both the location and the language; in Ahrefs or Semrush, switch to the country database. Our guide to finding keyword search volume covers the free methods.
4. Look at the local results page. Search with &gl=de&hl=de added to a Google search URL to see roughly what a German user sees. If the top results are forums, local brands or a different content type, plan for that.
5. Expect a smaller, different long tail. Volumes are lower than in English, which usually means lower difficulty too.

The keyword research tutorial covers the rest of the process, which works the same way in any language.

#Step 4: Localize every page element

Once you know the keywords, localize more than the body text. Each item below is something Google or the visitor reads:

Google's guidance warns against pages where only the navigation is translated and the main content stays in another language. Each page should use one language for both content and navigation.

#Step 5: Implement hreflang correctly

Hreflang tells Google which URL to show to which language or region. Google's hreflang documentation sets out the rules:

• Use one of three methods: <link> tags in the HTML head, HTTP headers (for PDFs), or the XML sitemap (easiest at scale). Pick one. Some platforms need an extension for this; Magento, for example, has no built-in hreflang setting.
• Codes are an ISO 639-1 language, optionally followed by an ISO 3166-1 Alpha-2 region: de, de-AT, en-GB, es-MX. A region alone is not allowed.
• Every version lists itself and every other version.
• Annotations must be reciprocal. If page A points to page B but B doesn't point back, Google ignores the pair.
• Add x-default for the fallback page (usually a language selector or your main version).

A correct set for a page with US English, UK English and German versions, placed on all three pages:

<link rel="alternate" hreflang="en-US" href="https://example.com/en-us/running-shoes/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/trainers/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/laufschuhe/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en-us/running-shoes/" />

The mistakes we see most often:

• en-UK instead of en-GB. UK is not an ISO 3166-1 code, and Google ignores reserved codes like UK and EU.
• Missing return links, usually after someone adds a new language to some templates only.
• Hreflang pointing to redirected, noindexed or non-canonical URLs. Every URL in the set should return 200 and be self-canonical.
• Canonicalizing translations to the English page. Each language version should have a canonical pointing to itself. Google only treats localized versions as duplicates when the main content is untranslated.

Search Console no longer has an International Targeting report (Google retired it in 2022), so validate hreflang with a crawler such as Screaming Frog before and after launch. Add it to your technical SEO audit checklist.

#Don't auto-redirect by location

Redirecting visitors based on their IP address or browser language feels helpful and causes two problems. Users who want another version can't reach it, and Google often can't either: its documentation notes that Googlebot usually crawls from the US and sends no Accept-Language header, so it may never find your other versions. Show a banner suggesting the local version and let people choose.

Google's documentation also lists the signals it uses to understand which country a page is for: ccTLDs, hreflang, server location (a weak signal), local addresses and phone numbers, local language and currency, links from local sites, and Google Business Profile. It ignores locational meta tags such as geo.position and code-level language attributes such as lang, and works out the language from the visible content.

#Machine translation, AI and native content

Machine translation and AI writing are good enough to draft localized content, and Google doesn't ban them. What Google's spam policies do treat as scaled content abuse is generating many pages "through automated transformations like synonymizing, translating" where little value is added for users. Bulk-translating thousands of pages with nobody reviewing them is the risky pattern.

Two workflows hold up:

• Translate and adapt for content that must say exactly the same thing everywhere (product specs, legal pages, docs): machine translation, then a native reviewer who fixes terminology, examples and the keyword targets from step 3.
• Write natively per market for content meant to rank: research local keywords first, then write each article for that market instead of translating the English one.

Outrank works the second way. It researches keywords in the target language and writes the article in that language from the start, in 150+ languages. In the last 90 days, 11% of the 200,871 articles it wrote for customers were in a language other than English:

Danish agency Vækster, for example, uses Outrank to publish Danish-language content for its local service clients.

#How to measure SEO localization

Measure each market separately, against its own baseline:

• In Search Console, filter Performance by country and by page (/de/) to see impressions, clicks and average position per market. Comparing a new German folder to your US numbers tells you nothing.
• Track whether the right version ranks: if UK searchers get your US page, check the hreflang set and the canonicals.
• Watch indexing per language folder in the Page indexing report. A localized folder that stays "Crawled - currently not indexed" usually means thin or near-untranslated pages.
• Track conversions per market in your analytics, with currency set correctly.

Expect a new language folder to take months to build traction, as any new section of a site does. Folders on an established domain usually move faster than a new ccTLD, which is one more argument for subdirectories.

#FAQ

#What is SEO localization?

SEO localization is the process of adapting a website to rank in another language or country. It covers local keyword research, adapted content and metadata, translated URLs, local prices and contact details, and technical signals such as hreflang and a clear URL structure. It goes further than translation because it targets the words local searchers actually use.

#What is the difference between translation and localization in SEO?

Translation converts your existing text into another language, keywords included. Localization starts from what people in the target market search for, then adapts the content, examples, units, prices and metadata to them. A translated page often targets keywords nobody in that market types.

#Is SEO localization the same as local SEO?

No. SEO localization targets a language or country, for example ranking a German version of your site in Germany. Local SEO targets a city or area, mainly through Google Business Profile, local pages and citations. Businesses with physical locations in several countries usually need both.

#Should I use subdirectories, subdomains or ccTLDs for international SEO?

Subdirectories (example.com/de/) are the best default because they share your main domain's authority and are easy to maintain. ccTLDs (example.de) give the strongest country signal but need their own authority and budget per country. Google lists URL parameters as not recommended.

#Does hreflang affect rankings?

Hreflang doesn't raise rankings directly. It helps Google show the right language or regional version of a page to each searcher, which prevents the wrong version from ranking and improves clicks from that market. For it to work, every version must list itself and all others, and the annotations must be reciprocal.

#Is machine translation bad for SEO?

Not by itself. Google's spam policies target automated translation used to churn out many pages without adding value. Machine translation reviewed and adapted by a native speaker, with local keyword research, is a normal and accepted workflow.