International SEO pays off when you can actually sell, deliver and support in a new market, not just because a country shows up in your analytics. For most companies the right setup is subfolders on the main domain, hreflang tags that pass validation, keywords researched natively in each language, and a rollout that adds one market at a time in step with sales.
When international SEO is worth the investment
Localized pages are a multiplier on a market decision, not a substitute for one. The signals that justify the work:
- Existing demand. Search Console already shows impressions and clicks from the country for your core terms, even without localized pages.
- A commercial plan. Sales, partners or paid media are already active there, or the go-to-market plan names it as a priority.
- Ability to transact. You can price in local currency, take local payment methods, ship or contract there, and answer support in the language.
- Different search behavior. Buyers there search in another language, use different terms or see different competitors, so your current pages don’t match.
Reasons that don’t: “the market is big,” a competitor launched there, or a plan to translate the site before anyone can invoice in that currency. For English-speaking markets, if pricing, spelling, shipping and legal terms match, one English version usually serves them all.
If the market hasn’t been chosen and sized yet, do that first with the go-to-market strategy template. The SEO plan follows from it.
ccTLDs vs subfolders vs subdomains
Each international version needs its own URL. Never swap content on one URL by IP or cookie: Google crawls mostly from US IP addresses and may never see the other versions.
| Factor | ccTLD (example.de) | Subfolder (example.com/de/) | Subdomain (de.example.com) |
|---|---|---|---|
| Geo signal | Strongest; tied to one country | Set through hreflang and content | Set through hreflang and content |
| Authority | Starts from zero on each domain | Shares the main domain’s | Shared in principle; in my experience slower to benefit |
| Cost to run | Highest: separate domains, links and upkeep | Lowest: one site, one CMS | Medium: often separate setup |
| Best for | Large companies with local teams and budget per country | Most companies entering one to five markets | Markets that need separate infrastructure or platforms |
My default is subfolders. They inherit the authority you’ve built, keep one codebase and one analytics setup, and let you launch a market with ten pages instead of a whole site. ccTLDs make sense when local trust clearly favors a local domain and you can fund each as its own SEO program.
Then decide what the folder represents:
- Language folders (
/de/,/es/) when only the language changes and the offer is the same across countries. - Country folders (
/uk/,/de/,/mx/) when pricing, currency, shipping or legal terms differ by country. - Language-country folders (
/de-ch/,/fr-ch/) when one country needs several languages.
hreflang: how it works and the common errors
hreflang tells search engines that a set of URLs are the same page for different languages or regions, so they can show each searcher the right one. It doesn’t boost rankings. It keeps the wrong version out of the wrong market and lets near-identical pages, like US and UK English, coexist.
Each value is a language code (ISO 639-1, such as de) with an optional region code (ISO 3166-1 alpha-2, such as de-AT). x-default names the fallback for searchers who match no listed version. A pricing page available in three versions would carry:
<link rel="alternate" hreflang="en-us" href="https://example.com/pricing/" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/pricing/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/preise/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/pricing/" />The same block, listing every version including itself, goes on all three pages. Place it in the HTML head, in HTTP headers (useful for PDFs) or in the XML sitemap (easier on large sites), using one method per set of pages. If your platform generates hreflang, audit the output anyway: it follows your settings, mistakes included.
The errors I find most often
| Error | What happens | Fix |
|---|---|---|
| Missing return links (A points to B, B doesn’t point to A) | The pair is ignored | Every version lists every other version |
| No self-reference | Breaks Google’s guidance; clusters are harder to confirm | Each page includes itself |
Invalid codes (en-UK, region-only gb, codes for groups like Europe or Latin America) | Tag ignored | en-GB; language always first; use language-only codes for multi-country audiences |
| Pointing to redirected, 404, noindex or non-canonical URLs | Tag likely ignored | Reference only final, indexable, canonical URLs |
| Every language version canonicalized to the English page | Localized pages dropped as duplicates | Each version gets a self-referencing canonical |
| Relative URLs | Tag may be ignored; Google expects absolute URLs | Use fully qualified URLs with protocol |
| Pages with no real equivalent forced into a cluster | Mismatched versions shown | Only annotate true equivalents |
Crawl the site with a tool that reports hreflang errors before launch and after every template change. These checks belong in the regular technical SEO audit, next to canonicals and indexing.
Translation vs localization
Translation converts words. Localization converts the offer, so a buyer in that market recognizes it as meant for them. Localize at least:
- Search terms: what people actually search, not the dictionary equivalent
- Commercial details: currency, prices, tax display, payment methods, shipping
- Proof: case studies, reviews and logos from the region
- Legal and trust: privacy terms, contract language, local contact details
- Formats: dates, units and spelling (US vs UK English counts)
- Metadata: titles, meta descriptions, alt text, URL slugs and schema values such as
priceCurrency
A workflow that scales: machine translation for the draft, a native editor working from that market’s keyword map, then a local salesperson or partner checking the offer details.
Tier the pages instead of translating everything. Fully localize the pages that sell: homepage, product or service pages, pricing, contact. Add a short list of high-intent content. Leave the rest unlaunched; hundreds of thin translated pages dilute a new market instead of building it.
Keyword research per market
Translating your keyword list is the most expensive shortcut in international SEO. The translated phrase is often not what people search, and the competitors and intent behind it can differ completely. Work through each market:
- Start from intents, not keywords. List the jobs your home-market pages serve, such as “compare tools,” “check pricing” or “solve a specific problem.”
- Have a native speaker describe each intent. In many markets, B2B buyers search English terms for software categories while consumers search in the local language. Only a local speaker catches that reliably.
- Pull data with the right settings. Set the keyword tool to the target country and language, and check live results there to see who ranks: local competitors, marketplaces or directories.
- Check the engine mix. Google leads in most markets, but Naver in South Korea, Baidu in China and Yandex in Russia change what optimization means.
- Map terms to localized pages. Flag gaps where the market needs a page your home site lacks, such as a comparison against a local competitor.
Rolling out one market at a time
Every market needs its own content, links and upkeep. Launch five at once and you get five half-finished sites that no one updates. Launch one, prove it, then add the next.
Time the SEO launch with the rest of the go-to-market motion. Organic search takes months to build, so localized pages should go live before or alongside sales outreach and paid media in that market, not after.
A typical sequence: plan (keyword map, structure, hreflang), launch the tier-one pages with internal links from the main site, build local signals through directories, partners, review sites and press, then expand where Search Console shows impressions without a matching page.
Before each market goes live:
- Folder structure and localized URL slugs agreed
- hreflang on every launched page, including
x-default, validated by a crawl - Self-referencing canonicals within each market
- Localized titles, descriptions and schema values
- New URLs in the XML sitemap
- No IP-based redirects; a language or country selector built with plain, crawlable links
- The market folder set up as its own Search Console property and reporting segment
- An owner named for updating localized pages when home-market pages change
Add the next market once the current one is indexed, gaining impressions, producing its first conversions, and staffed to stay current.
Measuring international performance
Measure by market, not just by country. A visitor from Germany may land on your US pages and an expat in Spain may prefer English, so country alone doesn’t show whether the setup works.
| Metric | Where to get it | What it tells you |
|---|---|---|
| Indexed pages per market | Search Console page indexing, per market property | Whether the launch is technically sound |
| Impressions and clicks by country | Search Console, filtered by country | Whether you’re reaching demand |
| Right-version share | Clicks from the target country landing in that market’s folder, divided by all clicks from that country | Whether hreflang and localization are working |
| Conversions per market | GA4, segmented by market folder | Whether the traffic includes buyers |
| Pipeline or revenue per market | CRM or store, with a market field set from the form or checkout page | Whether the market pays back |
Add each subfolder as a URL-prefix property in Search Console so every market gets its own performance and indexing reports. In GA4, set a content group from the URL path in your tag setup so every report can split by market.
Watch right-version share first. If searchers in the target country keep landing on home-market pages, check hreflang errors and whether the localized pages match local search terms. If traffic arrives but doesn’t convert, the problem is usually the offer: price, currency, proof or payment options.
Building this setup, from structure and hreflang to market-level reporting, is part of my technical SEO and content systems work.
Get it built
If you’re entering a new market and want the site structure, hreflang and localized pages right the first time, I’ll build them alongside the go-to-market plan. Start with a Growth Audit, $1,500 fixed and credited if we continue. See pricing or get in touch.