International SEO is one of the most technically demanding areas of search optimisation, and one of the most frequently botched. We have reviewed sites that have been "doing international SEO" for years with duplicated content in every language, hreflang tags pointing to non-existent pages, and geo-targeting configured to the wrong country in Search Console.
Done correctly, international SEO multiplies your addressable market without multiplying your costs proportionally. Done incorrectly, it can fragment your domain authority, confuse Google about your target audience, and leave you ranking in no country effectively.
This guide covers the full picture — from deciding whether international SEO is worth pursuing, through the technical implementation of hreflang, to ongoing measurement of international performance.
Key Takeaways
- International SEO is only worth pursuing if you have genuine demand in the target market — validate this before building anything
- Your domain structure decision (ccTLD vs subdirectory vs subdomain) has long-term SEO implications and should be made deliberately
- Hreflang tags are the most frequently broken element of international SEO; they must form a complete, self-referencing set
- Translation is not localisation — adapted content that reflects local culture, pricing, and search behaviour always outperforms direct translation
- Google's Hreflang documentation is the canonical technical reference; treat it as such
- Ahrefs' hreflang guide offers practical implementation walkthroughs and common debugging techniques
- Google's international targeting documentation covers domain strategy and geo-targeting configuration in detail
- RnkRocket's site crawl identifies hreflang errors and canonical issues across your international pages
When to Go International (and When Not To)
The first question is not "how do we do international SEO?" It is "should we?"
International SEO requires significant investment: content creation or translation, technical implementation, ongoing monitoring, and potentially local link building. Before committing, validate demand.
Signs you have genuine international demand:
- GSC shows meaningful impressions and clicks from other countries or languages without any international optimisation
- Your analytics shows users from target countries converting at a reasonable rate
- Your competitors in the target market are successfully serving the same audience online
- You have operational capacity to serve international customers (shipping, customer support, legal compliance)
Signs you are not ready yet:
- International traffic is less than 5% of your current organic visits
- You cannot serve international customers due to logistics, regulation, or resourcing
- Your domestic market is not yet sufficiently captured
- You are planning to use machine translation without any human review
If demand is validated, proceed. If it is not, focus on your home market and reassess in six to twelve months.
Domain Strategy: ccTLDs vs Subdirectories vs Subdomains
This is the most consequential structural decision in international SEO. There is no universally right answer, but there is a right answer for each situation.
Country-Code Top-Level Domains (ccTLDs)
Example: `example.co.uk`, `example.de`, `example.fr`
Pros: Strongest geo-targeting signal. Users in France trust `.fr` domains more than `.com/fr/`. Easiest to target specific countries in GSC.
Cons: Each ccTLD is a separate domain. Domain authority does not transfer between them. Building authority on `example.co.uk` does nothing for `example.de`. Requires separate link building campaigns per domain. Maintenance overhead is multiplied.
Best for: Large businesses with resources to build authority independently in each market, or businesses where local trust signals are commercially critical (legal, finance, healthcare).
Subdirectories (Recommended for Most Businesses)
Example: `example.com/de/`, `example.com/fr/`, `example.com/es/`
Pros: All authority consolidates on the root domain. A link to `example.com/de/produkte/` contributes to the overall `example.com` domain authority. Easier to maintain as a single codebase. GSC geo-targeting is available per subdirectory.
Cons: Slightly weaker geo-targeting signal than ccTLDs. Requires disciplined URL architecture to keep language/country directories cleanly separated.
Best for: Most businesses — the authority consolidation benefit almost always outweighs the weaker geo signal. This is what Google recommends for most cases.
Subdomains
Example: `de.example.com`, `fr.example.com`
Pros: Easier to host on different servers in different regions if needed. Some CMS platforms handle subdomains more easily than subdirectories.
Cons: Google treats subdomains as separate sites from a crawling and indexing perspective, but domain authority is partially shared — you get the worst of both worlds compared to subdirectories (ccTLDs) and full authority consolidation (subdirectories). More complex to implement and maintain.
Best for: Rarely the first choice. Use if your technical platform cannot support subdirectories.
Our Recommendation
Unless you have resources to build independent authority in each market, use subdirectories. The consolidated authority benefit compounds over time and dramatically reduces the link building burden.
Domain Strategy Comparison
| Factor | ccTLD (e.g. example.de) | Subdirectory (e.g. example.com/de/) | Subdomain (e.g. de.example.com) |
|---|---|---|---|
| Geo-targeting signal | Strongest (automatic) | Strong (with GSC targeting) | Moderate |
| Domain authority | Separate per domain | Consolidated on root domain | Partially shared |
| Setup cost | High (domain registration per country) | Low (directory structure) | Low–Medium |
| Maintenance overhead | High (separate properties) | Low (single codebase) | Medium |
| Link building burden | Full campaign per domain | Consolidated — all links benefit root | Partially separate |
| Best for | Large enterprises, regulated industries | Most businesses (recommended default) | Platform limitations only |
Hreflang Implementation
Hreflang tags tell Google which version of a page to serve to users in different countries and language combinations. They are powerful when implemented correctly and actively harmful when broken.
The Basic Structure
Hreflang tags are placed in the `` of each page, or in your XML sitemap, or returned as HTTP headers. The HTML implementation looks like this:
```html
\`\`\`Critical rule: Every page in a hreflang set must reference every other page in the set. This means the German services page must include all four of the above tags plus its own self-reference. If any page in the set is missing tags, Google may ignore the entire set.
The x-default Tag
The `x-default` tag specifies the fallback page for users who do not match any other language/country combination. This is typically your main English (or default language) page. It is not optional — include it on every page in every hreflang set.
Language Codes vs Country Codes
Hreflang values combine language codes (ISO 639-1) with optional country codes (ISO 3166-1 alpha-2):
- `en` — English, any country
- `en-gb` — English, United Kingdom
- `en-us` — English, United States
- `de` — German, any German-speaking country
- `de-ch` — German, Switzerland
- `pt-br` — Portuguese, Brazil
- `pt-pt` — Portuguese, Portugal
Use country-specific codes when the content differs by country (different pricing, different regulations, different cultural references). Use language-only codes when the content is the same across all countries that speak that language.
Common Hreflang Mistakes
Mistake 1: Missing self-referencing tag Every page must include a hreflang tag pointing to itself. The French page must include ``.
Mistake 2: Pointing to redirecting or non-existent URLs Every URL in a hreflang set must return a 200 status code. Pointing hreflang tags to 301 redirects or 404 pages causes the entire set to be ignored.
Mistake 3: Inconsistent implementation If some pages implement hreflang in HTML `` and others in the sitemap, Google can get confused. Pick one method and use it consistently.
Mistake 4: Forgetting paginated pages If your products or blog posts use pagination (`/fr/produits/page/2/`), each paginated page needs its own hreflang tags pointing to the equivalent paginated pages in other languages.
Mistake 5: Using the wrong attribute It is `rel="alternate"`, not `rel="canonical"`. A canonical tag and hreflang tag are different things with different functions.
Content Localisation vs Translation
There is a critical difference between translation (converting words from one language to another) and localisation (adapting content to reflect the culture, norms, and search behaviour of the target market).
Translation alone will not win rankings. Here is why:
Search intent varies by market: A user in Germany searching for "best project management software" may have different intent and expectations than a user in the UK searching the same query. German users may prioritise data privacy features more heavily; UK users may be more price-sensitive. The content needs to reflect these differences.
Pricing and currency: Show local currency, not a converted price. £99/month should be €115/month on the German page, not "£99/month (approximately €115)."
Local references and case studies: A UK case study featuring a fictional "small business owner from Manchester" does not resonate with a user in Lyon. Create local examples, or at minimum use neutral examples that do not reference a specific location.
Date and number formats: DD/MM/YYYY in the UK, MM/DD/YYYY in the US, YYYY-MM-DD in some other markets. These details signal genuine localisation rather than lazy translation.
Cultural tone: Formal vs informal, direct vs indirect, the use of humour — all of these vary by market and language. French business writing is typically more formal than UK writing; German writing often more direct. A translator who understands these nuances is worth significantly more than one who produces literal translations.
For practical tips on creating content that serves both SEO and real users, the content strategy guide applies equally in international markets.
Geo-Targeting in Google Search Console
GSC allows you to set a target country for your site or specific subdirectories. This is a relevance signal — it tells Google which country you are primarily targeting with a given URL pattern.
For ccTLD domains (`.co.uk`, `.de`), geo-targeting is set automatically by the domain extension.
For subdirectory implementations, set geo-targeting per directory:
- In GSC, add your subdirectory as a separate property (`example.com/de/`)
- Go to Settings > International Targeting
- Set the target country to Germany
This is an explicit signal and one Google takes seriously. Subdirectory implementations without explicit geo-targeting still work, but adding this signal improves targeting accuracy.
Performance Report Filtering
Beyond the International Targeting setting, use GSC's Performance report with country filters to understand how your content performs in each target market. Filter by country to see which queries drive impressions and clicks from each region. This data reveals opportunities: if your English content already receives significant impressions from Germany (for English-language queries), that is a strong indicator that a German-language version of that content would perform well.
Compare CTR by country as well. A low CTR in a specific market, combined with decent impressions, often means your title tags and meta descriptions need localisation even if the content itself is in the right language. A title tag optimised for UK search behaviour may not resonate with US or Australian searchers despite being in the same language.
International Keyword Research
Do not translate your English keywords. Research keywords independently in each target market.
A keyword that is commercially significant in English may have low search volume in French, or may be dominated by local competitors with a different approach. Do your research as if you are starting from scratch in each market:
Step 1: Identify the core topics your business serves. These are universal.
Step 2: Use a keyword tool (Ahrefs, Semrush, or Google Keyword Planner) with the target country and language selected. Find how native speakers search for those topics.
Step 3: Validate intent. Search for the top-volume keywords in a browser set to the target country. Do the results match what you expect? Are commercial results or informational results ranking?
Step 4: Check the competitive landscape. Who is currently ranking? Are they local businesses, global brands, or affiliates? This tells you how hard the keyword is to break into.
Step 5: Prioritise keywords by volume × relevance × competitive opportunity, exactly as you would in your home market.
For a full keyword research methodology, see our keyword research masterclass.
Technical Considerations
CDN and Hosting Location
Google has stated that hosting location is a minor ranking signal. It is much weaker than geo-targeting settings and hreflang implementation, but using a CDN (Content Delivery Network) that serves content from nodes close to each target market improves actual page load time for those users — which does affect rankings via Core Web Vitals.
Cloudflare, Fastly, and similar CDN providers are effective at reducing Time to First Byte (TTFB) for international users. If your site is hosted in London and you are targeting users in Australia, TTFB for Australian users will be meaningfully higher without a CDN.
International Link Building
Building links from local websites in each target market is the highest-impact external signal for international ranking. A link from a German business directory or a German industry publication is a stronger geo-signal than a link from a UK site linking to your German pages.
Pursue local link building tactically:
- Local business directories in each market
- Local industry associations and trade bodies
- Local press and media outreach
- Partnerships with local businesses for mutually beneficial content
Crawl Budget for Large International Sites
If you have thousands of international pages (e-commerce with product catalogues in ten languages), Google's crawl budget becomes relevant. Ensure:
- Your XML sitemaps are per-language/country and submitted individually in GSC
- Non-canonical pages (translated thin content, paginated pages) are excluded from sitemaps
- Your site does not generate excessive URL variants through parameters or faceted navigation
For a deeper crawl health review, the technical SEO audit guide applies equally to international sites.
Measuring International SEO Success
Setting Up Per-Country Tracking in GSC
In Google Search Console, the Performance report allows you to filter by country. Use this to track:
- Impressions and clicks from each target country
- Average position for your primary keywords in each market
- CTR differences between markets (which often indicate title tag localisation opportunities)
Rank Tracking Per Market
Set up rank tracking for each target country separately, with locally relevant keyword sets. Rankings for `example.com/de/` when searched from Germany are different from rankings when searched from the UK. Track from the right location.
RnkRocket allows you to track rankings by location, so you can monitor German, French, and UK performance from a single dashboard. This is particularly useful for agencies managing international clients.
Traffic and Conversion Segmentation in GA4
In GA4, create audience segments for each target country. Track:
- Sessions per country
- Conversion rate per country
- Revenue per country (for e-commerce)
A lower conversion rate in a specific market often indicates a localisation issue rather than an SEO issue. If users are arriving but not converting, examine the local content, pricing, and user experience rather than ranking data.
Case Study: UK SaaS Expansion into DACH Markets
A UK-based project management SaaS company with 12,000 monthly organic sessions decided to target the DACH region (Germany, Austria, Switzerland) after GSC data showed 1,800 monthly impressions from German-language queries with no localised content.
Domain strategy: They chose subdirectories (`example.com/de/`) over ccTLDs to consolidate their existing DA 52 root domain authority. The development team created a `/de/` subdirectory with localised URL slugs (e.g. `/de/projektmanagement-software/` rather than a direct translation of the English URL).
Content localisation: Rather than machine-translating their 45 English pages, they prioritised 12 high-value pages — the homepage, four product pages, three comparison pages, and four blog posts targeting high-volume German keywords. A native German copywriter adapted the content, adjusting pricing to euros, replacing UK case studies with DACH-relevant examples, and rewriting CTAs to match the more formal tone typical of German B2B content.
Hreflang implementation: Each localised page received a complete hreflang set referencing both the English and German versions, with x-default pointing to the English page. They submitted a separate `/de/` sitemap to GSC and set geo-targeting to Germany.
Results over 6 months: The German subdirectory generated 2,400 monthly organic sessions by month 6. Three pages reached page 1 for competitive German keywords. The company acquired 14 backlinks from German tech blogs and directories through targeted outreach. Conversion rate on the German pages was 2.1% — lower than the 3.4% on English pages but sufficient to justify expansion into French and Spanish subdirectories in month 8.
Key lesson: Starting with 12 properly localised pages outperformed a competitor that had machine-translated all 80 of their pages. Quality localisation on fewer pages built authority faster than thin translated content spread across the full site.
When International SEO Is Not the Right Move
Not every business benefits from international expansion. Before committing resources, ask yourself these questions honestly:
Is there proven demand in the target market? Use Google Trends to compare search interest for your core topics across countries. If volume is negligible, the return on investment will not justify the content localisation effort. A UK-focused plumbing company has no reason to target the German market; a SaaS tool with global applicability does.
Can you actually serve international customers? If you cannot fulfil orders internationally, process payments in local currencies, or provide customer support in the target language, international SEO will drive traffic that cannot convert. Traffic without conversion is a vanity metric.
Do you have the budget for quality localisation? Machine translation is cheap but produces thin, low-quality content that Google's quality systems will filter. Professional localisation — adapting content, imagery, pricing, and cultural references — costs real money. A half-localised site can damage your brand in the target market more than having no presence at all.
Are you strong enough domestically? International expansion before domestic authority is established is a common strategic mistake. If you are not yet ranking well in your home market, the resources spent on internationalisation would almost certainly produce better returns if invested in strengthening your domestic SEO. Build authority at home first, then expand.
Is there a competitive advantage? Entering a market where strong local competitors already dominate requires a genuine differentiator — a unique product, lower pricing, better technology, or a service gap that local competitors are not filling. If you cannot articulate your advantage in the target market, reconsider.
Common International SEO Mistakes (Summary)
| Mistake | Impact | Fix |
|---|---|---|
| Machine-translated thin content | Duplicate content, poor UX | Human review of all translated content |
| Broken hreflang sets | Wrong pages shown to wrong users | Audit hreflang with Screaming Frog or RnkRocket |
| Missing x-default tag | Unmatched users sent to wrong version | Add x-default to every hreflang set |
| Using subdomains by default | Fragmented authority | Use subdirectories unless you have a clear reason not to |
| No geo-targeting in GSC | Weaker relevance signal | Set International Targeting per subdirectory |
| Translating keywords directly | Low-volume or wrong-intent keywords | Research keywords independently per market |
Frequently Asked Questions
Can one page rank in multiple countries?
Yes, but targeting multiple countries with a single page is less effective than having dedicated country pages. A single page with `hreflang="en"` will appear in all English-speaking countries, but will not be as precisely targeted as a page with `hreflang="en-gb"` for the UK market.
Do I need a separate sitemap for each language?
Not strictly required, but it is good practice to have per-language sitemaps submitted separately in GSC. This makes monitoring and crawl error diagnosis much easier.
How long does it take to rank in a new country?
Typically 3–6 months for a new subdirectory to start ranking meaningfully, assuming the content is localised properly and some in-market links are built. ccTLDs with no existing authority can take 6–12 months.
What if my platform does not support subdirectories?
Use subdomains as a fallback, not ccTLDs. The Shopify platform, for example, handles international stores via subdomains by default in some configurations. Imperfect implementation is better than none.
Is it worth translating my entire site or just the main pages?
Start with your highest-value pages: homepage, main service/product pages, and top 5–10 blog posts that address high-intent topics. Expand from there based on what is driving traffic and conversions.
Related Reading
- Technical SEO Audit Checklist — apply the same audit framework to your international pages
- Technical SEO Explained — foundations of how Google processes your site structure
- Content Strategy for Small Business — content creation principles that apply in every market
Take Your International SEO Further
Identifying hreflang errors across hundreds of pages manually is slow and error-prone. RnkRocket's site audit flags broken hreflang tags, missing canonicals, and crawl issues across your entire international site. Explore our pricing to get started.
