Multilingual Seo Url Structures: Choose Subdirectories, Subdomains or Country Domains for International Growth

Expanding into international search markets creates a structural decision that can affect rankings, crawl efficiency, reporting, localisation and conversion rates for years. You need to decide whether each language or market should live in a subdirectory, a subdomain or a country-code top-level domain, then make sure every version sends consistent signals to search engines and users.

The choice becomes more difficult when your site already has overlapping pages, translated content, regional offers and several teams publishing at once. That is where keyword cannibalisation, SEO keyword overlap and ranking dilution issues can quietly reduce performance.

A sound multilingual architecture gives each page a clear job. It helps search engines understand the intended audience, keeps international versions connected, and gives your team a manageable publishing system. The SEO Letters writing platform can support that process by researching keywords, mapping topical clusters and generating structured articles for different markets without forcing you into a copy-and-paste workflow.

Why multilingual SEO URL structures matter

A URL is only one part of international SEO, but it is an important part. The structure tells users and search engines how your site is organised, where a page belongs and, sometimes, which country or language it serves.

Compare these examples:

example.com/fr/seo-tools/
fr.example.com/seo-tools/
example.fr/seo-tools/

All three can support a French version of a site. They do not create identical operational conditions, though. Each approach affects authority distribution, technical maintenance, geo-targeting, link acquisition and the way you investigate ranking changes.

Your architecture should answer several practical questions:

Is the page translated for a language or localised for a country?
Will the same product, pricing and legal information apply in every market?
Do regional teams need publishing independence?
Can you build links to separate domains consistently?
Will each market require different keyword research and search intent mapping?
How will you prevent near-identical pages competing with one another?
Can your CMS handle hreflang, canonicals and regional redirects accurately?

There is no universal winner. The correct option depends on your commercial model, site authority, localisation depth and operational capacity.

The three main URL structures for international SEO

International sites usually choose one of three core structures. A fourth option, URL parameters, exists, but it is generally less suitable for long-term multilingual SEO because parameters are less readable and can complicate crawling, indexing and reporting.

Structure	Example	Main strength	Main weakness
Subdirectory	`example.com/de/`	Consolidates authority on one domain	Regional separation is less independent
Subdomain	`de.example.com/`	Allows technical and organisational separation	Authority and reporting can become fragmented
Country domain	`example.de/`	Strong local identity and country signal	Expensive to build, maintain and promote
URL parameter	`example.com/?lang=de`	Easy to add technically	Weak user experience and more complex indexing

The decision should not be based on URL appearance alone. You need to consider how the entire international search system will operate, including content production, internal linking, analytics, schema, redirects, local citations and editorial governance.

Subdirectories: the practical default for many businesses

A subdirectory places international content inside the main domain. Typical examples include:

example.com/fr/
example.com/es/
example.com/en-au/
example.com/de-de/

This is often the most manageable choice for businesses that want to build one broad domain while serving several languages or regions.

Advantages of subdirectories

Subdirectories can offer several operational benefits:

Existing domain authority can support new language sections.
Internal links remain relatively simple to manage.
Analytics and SEO reporting can be segmented by folder.
Hosting and technical maintenance are usually centralised.
New market sections can be launched without buying and developing new domains.
Content teams can work within one CMS and one publishing process.

This structure is particularly useful when your international pages share products, brand assets, design systems and technical infrastructure. A SaaS business selling the same platform across Europe might use /fr/, /de/ and /es/ while adapting terminology, examples, pricing and support content for each market.

Limitations of subdirectories

Subdirectories do not automatically solve localisation. A translated page can still fail if it uses the wrong local terminology, ignores regional search behaviour or offers the same content as another market page with only minor wording changes.

Potential issues include:

A global content team publishing translations without local keyword validation.
Language folders being treated as simple duplicates of the English site.
Country-specific pages being mixed with language-only pages.
Internal links pointing users to the wrong regional version.
Hreflang implementation becoming inconsistent as the site grows.
Regional teams having limited control over local content and campaigns.

A subdirectory can also make local identity less obvious. A user in Germany may trust example.de more quickly than example.com/de/, especially in sectors where local compliance, delivery and customer support matter.

When subdirectories are a strong fit

Choose subdirectories when:

You are entering several markets with limited SEO resources.
The same business entity serves most countries.
Your products and fulfilment are broadly consistent.
You want to concentrate authority on one domain.
You can manage translation and localisation centrally.
Your CMS supports robust hreflang and regional templates.
You need to launch market sections quickly and measure them in one property.

For many growing companies, this is the sensible starting point. It keeps the system contained while you learn which markets produce demand and revenue.

Subdomains: useful when markets need technical separation

A subdomain creates a distinct host under the main domain:

fr.example.com
de.example.com
au.example.com

Search engines can understand the relationship between a subdomain and the root domain, but you should still treat each subdomain as a largely separate SEO property in your planning and reporting.

Advantages of subdomains

Subdomains can work well when international teams or products need meaningful separation:

Different regional teams can manage their own publishing workflows.
Technical stacks can differ between markets.
Country-specific checkout or account systems can be isolated.
Large organisations can allocate budgets and performance targets by region.
Mergers, acquisitions or independent business units can retain operational autonomy.

For example, a global marketplace might use separate subdomains because each region has different inventory, payment methods, delivery systems and compliance requirements. In that case, the technical separation reflects a real business separation.

Risks of subdomains

The main concern is fragmentation. Links, content signals and authority may not support every subdomain as efficiently as they would support folders within a single domain.

Common risks include:

Each subdomain requiring its own content authority.
Separate reporting properties creating gaps in performance analysis.
Inconsistent navigation between language versions.
Regional teams producing overlapping pages.
Different technical standards across markets.
Slow implementation of fixes because ownership is divided.
Weak internal linking between the main site and regional sections.

Subdomains can also increase the likelihood of duplicated or competing content. A global team may publish example.com/seo-guide/, while a regional team creates de.example.com/seo-guide/ without a clear language or market distinction. If both pages target the same audience, the problem is not simply translation. It is a site-wide SEO keyword overlap problem.

When subdomains make sense

Use subdomains when:

Markets operate with distinct products, teams or technical infrastructure.
A regional business needs publishing independence.
Local regulations or customer journeys differ significantly.
You can invest in separate authority building and technical monitoring.
The parent brand remains important to trust and recognition.
Your organisation has clear ownership for each subdomain.

Do not choose a subdomain merely because it looks international. It should solve a real operational problem.

Country-code domains: the strongest local signal with the highest cost

A country-code top-level domain, or ccTLD, uses a country-specific extension:

example.fr
example.de
example.es
example.com.au

This can send a clear country association to users and search engines. It may also support higher click-through rates when local trust and familiarity influence the purchase decision.

Benefits of country domains

Country domains can support:

Strong local market positioning.
Clear country relevance in search results.
Easier promotion through local partnerships and media.
Greater confidence for users looking for local services.
Independent regional branding and pricing.
Separate domain-level strategies for highly competitive markets.

A legal services firm, financial provider or national retailer may benefit from this structure because users often expect a local entity, local policies and local customer support.

Drawbacks of country domains

The cost is substantial. Each domain may need its own:

Link acquisition programme.
Technical SEO audits.
Content calendar.
Analytics configuration.
Brand protection process.
Cookie and privacy implementation.
Local editorial review.
Domain renewal and security management.

Country domains can also create duplicated investment. A strong page on example.com does not automatically transfer all of its authority to example.fr. You will need deliberate cross-domain linking, local mentions and market-specific content.

When country domains are appropriate

Consider ccTLDs when:

The business has a genuine local presence.
Products, prices and policies vary by country.
Local trust directly affects conversion rates.
You have a budget for independent SEO programmes.
Regional teams can create genuinely local content.
The target market is commercially important enough to justify the overhead.

If you are testing ten markets, launching ten country domains at once may create more management risk than growth. Start with a structure you can maintain properly.

Language targeting versus country targeting

One of the most common architecture mistakes is confusing language with country.

French is spoken in France, Belgium, Switzerland, Canada and several other markets. Spanish is used across Spain, Mexico, Colombia, Argentina and many more countries. A language folder alone does not tell search engines that the offer, pricing or legal terms are specific to one country.

Use a language-only structure when the page is broadly intended for speakers of that language:

example.com/fr/
example.com/es/

Use a language-and-country structure when the content is localised:

example.com/fr-fr/
example.com/fr-ca/
example.com/es-es/
example.com/es-mx/

The second format is more precise, but it creates more page variants and more governance work. Do not create country folders simply because a country exists in your expansion plan. Create them when there is a meaningful difference in search intent, product availability, pricing, spelling, regulations, shipping or customer support.

A practical targeting matrix

Business situation	Recommended pattern
One French page serves all French-speaking users	`/fr/`
Separate France and Canadian offers	`/fr-fr/` and `/fr-ca/`
One Spanish content hub with no local pricing	`/es/`
Different Spanish and Mexican products	`/es-es/` and `/es-mx/`
Local legal and financial services	Country domains or country-specific folders
International SaaS with one global product	Language subdirectories may be sufficient

Hreflang is essential, but it is not a substitute for architecture

Hreflang annotations help search engines identify alternative versions of a page for different languages or regions. They can be implemented in HTML, HTTP headers or XML sitemaps.

For example, a page might declare:

<link rel="alternate" hreflang="en-gb" href="https://example.com/en-gb/seo-audit/" />
<link rel="alternate" hreflang="fr-fr" href="https://example.com/fr-fr/audit-seo/" />
<link rel="alternate" hreflang="de-de" href="https://example.com/de-de/seo-audit/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/seo-audit/" />

Every alternate page should refer back to the others. These are reciprocal signals. If the French version points to the English page but the English page does not point back, the implementation may be ignored or weakened.

Hreflang checks for international sites

Run a regular audit covering:

Missing return tags.
Invalid language or country codes.
Hreflang URLs returning non-200 responses.
Canonical tags pointing to another language version.
Noindex directives on intended alternates.
Redirected hreflang URLs.
Pages listed in hreflang but absent from the XML sitemap.
Incorrect regional mappings.
Language versions that are not genuine alternatives.

A key point: hreflang helps with regional selection. It does not merge authority, remove duplicate content or decide which page should rank for a broad keyword.

Canonicals, redirects and language selectors

International SEO becomes unstable when canonical tags, redirects and language selectors work against one another.

A localised page should generally have a self-referencing canonical if it is indexable and intended to rank. The French page should not canonically point to the English page simply because the English page was published first.

Example of the correct relationship

English page canonicalises to itself.
French page canonicalises to itself.
German page canonicalises to itself.
Each version includes reciprocal hreflang annotations.
The language selector links directly to the equivalent version.
Internal links use the appropriate market URL.

Avoid automatic IP-based redirects wherever possible. They can prevent users and crawlers from accessing the correct version, particularly when a user is travelling or using a VPN. A visible language and country selector is usually safer.

Keyword cannibalisation in multilingual SEO

Keyword cannibalisation occurs when multiple pages on the same site appear to target the same query or the same underlying search intent. In international SEO, the issue can happen within one language, between translated pages, or across regional versions.

Consider this structure:

example.com/en/seo-copywriting/
example.com/en/blog/seo-copywriting-guide/
example.com/en/services/content-writing/
example.com/uk/seo-copywriting/
example.com/us/seo-copywriting/

These pages might all be valid, but if they target the same audience and offer the same information, Google may struggle to identify the preferred result. Traffic can move between pages, rankings can fluctuate, and link equity may be diluted.

Types of international cannibalisation

1. Direct translation overlap

Two translated pages target the same local query because the business has not completed local keyword research. The wording differs, but the intent and market may be identical.

2. Country and language duplication

A site has both /fr/ and /fr-fr/, yet both pages target users in France. This creates a structural conflict.

3. Regional product overlap

The UK and Australian versions use different folders, but the products, pricing and copy are almost identical. If both pages attract the same English-language searches, they may compete.

4. Blog and service page overlap

A translated blog article targets the same commercial phrase as a regional service page. The blog earns links, while the service page is more valuable commercially, but the site has not clarified their roles.

5. Duplicate location pages

A company creates city pages in several languages with minimal local information. These pages may overlap with country pages and provide little distinct value.

How to complete a keyword cannibalisation audit

A keyword cannibalisation audit should combine rankings, URL structure, search intent and business value. Exporting keywords alone is not enough.

Step 1: Build a complete URL inventory

Collect:

Indexable URLs.
Language and country versions.
Canonical URLs.
Hreflang references.
Organic landing pages.
Target keywords.
Clicks, impressions and conversions.
Content type and funnel stage.
Last update date.
Market and language owner.

A spreadsheet can work for a smaller site. Larger sites will benefit from a crawl export combined with Search Console and analytics data.

Step 2: Group URLs by language, country and topic

Create clear labels for each page:

Field	Example
URL	`example.com/de/seo-agentur/`
Market	Germany
Language	German
Page type	Service
Primary topic	SEO agency
Search intent	Commercial
Organic clicks	1,850
Conversions	74
Hreflang group	SEO agency regional set

This makes hidden overlap easier to spot. Two URLs may look different in a crawl but belong to the same topical cluster and serve the same search intent.

Step 3: Compare query-level performance

In Google Search Console, compare pages receiving impressions for the same queries. Look for:

Several pages ranking between positions 5 and 30.
Frequent URL switching for one query.
A page ranking in the wrong language or country.
A blog page ranking above a money page.
Impressions spread thinly across near-identical URLs.
High impressions with poor click-through rates across several versions.

These patterns can indicate ranking dilution issues, though they should be interpreted alongside intent, page quality and SERP competition.

Step 4: Map search intent

For each overlapping URL, identify the dominant intent:

Informational.
Commercial investigation.
Transactional.
Navigational.
Local.
Support or post-purchase.

If two pages have the same language, market and intent, they may need consolidation. If they have different markets but identical intent, local evidence should determine whether both pages deserve to exist.

Step 5: Choose an action

Your options include:

Keep both pages and improve differentiation.
Merge pages into one stronger URL.
Redirect the weaker page.
Canonicalise only where duplication is genuine.
Rework one page for a different intent.
Move content into a local hub.
Add unique market evidence and commercial details.
Block low-value variants from indexing.

Do not redirect pages solely because one has fewer backlinks. A lower-authority page may have stronger conversion performance or better local relevance.

Search intent mapping for multilingual content

Translation should begin after search intent mapping, not before. A literal translation of a high-ranking English page may be linguistically correct but commercially wrong in another market.

For each target market, examine:

The words users actually search.
Whether the SERP favours guides, category pages, tools or services.
Local terminology and spelling.
Common questions and objections.
Competitor page formats.
Price and product expectations.
Trust signals used by local competitors.
Regulatory or cultural considerations.

A German market may prefer a more detailed technical guide for a phrase that produces shorter commercial pages in the UK. A Spanish query may have different wording in Spain and Mexico. The intent needs to be validated locally.

A repeatable search intent mapping framework

Collect local keyword variants: Use local search data, competitor pages and native-language research.
Cluster similar queries: Group by meaning, not just by shared words.
Review the SERP: Record the dominant page types and features.
Assign a page purpose: Decide whether the page informs, compares, sells or supports.
Map one primary URL: Avoid assigning the same intent to several pages.
Record secondary terms: Include related questions without creating unnecessary URLs.
Set a conversion goal: Link rankings to leads, sales, sign-ups or assisted conversions.

SEO Letters can help organise this workflow by turning keyword research into topical clusters and article briefs. You can also use its scheduled campaigns to create market-specific content on a controlled cadence rather than asking several teams to publish overlapping translations.

Content consolidation strategy for multilingual sites

A content consolidation strategy is useful when your site has accumulated too many versions of similar pages. This often happens after acquisitions, international expansion or years of uncoordinated blogging.

Start by classifying pages into four groups:

Classification	Recommended action
Strong performance and unique intent	Retain and improve
Weak performance but valuable local purpose	Localise and strengthen
Duplicate intent with a stronger equivalent	Consolidate or redirect
Thin, outdated or unsupported page	Remove, redirect or noindex

Consolidation should preserve useful market signals. If a French page has local backlinks, references and customer stories, merging it into an English global page may remove precisely the relevance you need.

What to consolidate

Consider merging pages when they have:

The same language and country target.
The same primary intent.
Similar headings and content structure.
Overlapping keyword sets.
No meaningful product or legal difference.
Weak independent traffic and conversion data.
No unique local links or evidence.

What to preserve

Keep separate pages when they have:

Different currencies or pricing.
Different fulfilment or product availability.
Distinct local regulations.
Different customer segments.
Unique local case studies.
A clearly different SERP.
Separate commercial teams and conversion paths.

The aim is not to reduce URL count at any cost. It is to make every indexable URL defensible.

Internal linking across language and country versions

Internal linking tells users and crawlers how your international architecture fits together. It also helps distribute authority to important pages within each market.

Use a consistent linking model:

Global navigation links to the appropriate regional homepage.
Regional navigation links to local category and service pages.
Blog articles link to relevant local commercial pages.
Equivalent language pages link through the language selector.
Country-specific pages avoid sending users to a generic page when a local alternative exists.
Breadcrumbs reflect the local hierarchy.
XML sitemaps separate language or market groups where practical.

Do not automatically translate every internal anchor text literally. Anchor wording should match local search behaviour and natural language. A translated phrase may not be the phrase users use in the target market.

Internal linking audit questions

Does every important market page receive links from relevant local content?
Are links accidentally pointing to the default English version?
Do country pages link to one another without clear purpose?
Are orphaned translated pages present?
Does the blog link to service pages using commercially relevant local terminology?
Are old URLs still receiving internal links after consolidation?
Are navigation menus creating thousands of near-duplicate links?

Choosing between structures: a scoring rubric

Score each factor from 1 to 5, where 5 represents a strong reason to favour the structure.

Decision factor	Subdirectory	Subdomain	Country domain
Centralised authority	5	3	2
Local country identity	3	3	5
Technical independence	2	5	5
Lower maintenance cost	5	3	1
Regional team autonomy	2	5	5
Fast market testing	5	3	2
Local link-building potential	3	3	5
Simple reporting	5	3	2
Suitability for one global product	5	3	2
Suitability for fully local operations	3	4	5

The score is only a planning aid. Weight each factor based on your commercial model. If local compliance is critical, country identity may deserve twice the weight of maintenance cost.

Recommended decision process

Use this framework before making a migration or launch decision.

Step 1: Define the market model

Document:

Countries served.
Languages supported.
Legal entities.
Product differences.
Local pricing.
Customer support arrangements.
Delivery or fulfilment limits.
Regional marketing ownership.

Step 2: Separate language from country requirements

Decide whether you need:

One page per language.
One page per country.
Language-country combinations.
A global fallback page.
Local service area pages.

This prevents you from creating folders that have no genuine content or commercial purpose.

Step 3: Audit the existing site

Review:

Indexation.
Organic landing pages.
Keyword overlap.
Hreflang.
Canonicals.
Redirects.
Local backlinks.
Conversion paths.
Page templates.
Translation quality.

Step 4: Model the future URL system

Draw the architecture before implementation. Include:

Homepage.
Language selector.
Country selector.
Category pages.
Product pages.
Blog and resource hubs.
Local service pages.
Legal and support sections.
XML sitemap groups.

Step 5: Create ownership rules

Assign responsibility for:

Keyword research.
Translation and native review.
Hreflang.
Internal linking.
Technical deployments.
Content refreshes.
Local outreach.
Cannibalisation monitoring.

Without ownership, the architecture will slowly degrade.

Step 6: Test before scaling

Launch one or two priority markets first. Track rankings, indexation, crawl patterns, conversions and user behaviour for several weeks. The data may suggest that a language-only structure is enough, or that a high-value market requires a more independent local experience.

How SEOLetters supports multilingual publishing

International SEO often fails between strategy and execution. The keyword research may be accurate, but the content is published late, internal links are missed and regional teams create similar articles without checking the existing site.

SEO Letters is designed for publishers, SEOs and business teams that need a repeatable content operation. It can support:

Keyword research with difficulty ratings.
Topical authority cluster planning.
Competitor and site-gap analysis.
Structured article generation with headings and internal links.
Brand-aware writing across multiple languages.
Product-aware content for affiliate and ecommerce publishing.
Schema and image recommendations.
Direct publishing to WordPress, Shopify and webhooks.
Performance monitoring for published content.
Content refresh campaigns for ageing pages.
Scheduled autonomous campaigns that research, write and publish on a defined cadence.

The multilingual capability covers 21 languages, although each market should still receive native review where terminology, regulation or persuasion matters. Software can accelerate the workflow. It does not remove the need for a clear architecture and accountable quality control.

A safer SEOLetters workflow for international content

Create a market brief: Define audience, country, language, offer and conversion goal.
Run local keyword research: Avoid copying the English keyword list without validation.
Build a topical cluster: Identify pillar pages, supporting articles and commercial targets.
Check existing URLs: Look for SEO keyword overlap and competing pages.
Generate the article: Set language, market, tone, product context and internal link rules.
Review localisation: Check terminology, examples, spelling, currency and claims.
Publish to the correct destination: Use the relevant folder, subdomain or domain.
Validate technical signals: Check canonical, hreflang, schema, links and indexability.
Measure business results: Track qualified traffic, conversions and assisted revenue.
Refresh on schedule: Update pages when rankings, products or market conditions change.

You can route different stages to Gemini, OpenAI or Claude using your own AI keys, which may help larger teams align model choice with cost, language quality or workflow requirements.

Measuring international SEO architecture performance

Do not judge a URL structure only by rankings. Architecture should support measurable business performance and stable publishing operations.

Track these KPIs by language, country and URL type:

KPI	Why it matters
Indexed valid pages	Shows whether intended content is discoverable
Impressions by market	Indicates search visibility
Click-through rate	Shows how titles and local relevance perform
Average position	Helps identify competitive movement
Organic conversions	Connects SEO to commercial outcomes
Assisted conversions	Captures research-stage influence
Revenue per market	Supports investment decisions
Crawl errors	Identifies technical barriers
Hreflang error rate	Measures international signal quality
Cannibalisation incidents	Shows whether page roles are clear
Content refresh uplift	Measures improvement from updates
Time to publish	Reveals operational efficiency

Benchmark markets against their own baseline rather than expecting every country to perform identically. Search demand, competition, brand awareness and purchasing behaviour vary considerably.

Warning signs that the architecture needs attention

Look for:

A country page ranking in the wrong market.
Several pages switching positions for the same query.
A rapid increase in indexed URLs without corresponding traffic.
High impressions but low engagement on translated content.
Hreflang errors appearing after every deployment.
Local pages receiving no internal links.
Strong backlinks pointing to redirected or obsolete URLs.
Traffic rising while qualified leads remain flat.
Blog pages outranking commercial pages for transactional terms.

These signs do not always prove structural failure. They do suggest that a deeper audit is warranted.

Example: a SaaS company expanding into Europe

Imagine a UK-based SaaS company entering France, Germany and Spain. The software is largely the same, but pricing pages, support hours and legal documentation vary slightly.

A sensible first-stage architecture might be:

example.com/en-gb/
example.com/fr-fr/
example.com/de-de/
example.com/es-es/

The company could use subdirectories because it wants to consolidate authority and test demand without building four independent domains. Each market would have:

A local homepage.
A local product page.
A pricing page with local currency.
Market-specific case studies.
Translated support documentation.
Unique keyword clusters.
Reciprocal hreflang.
Self-referencing canonicals.

The French blog should not simply reproduce every English article. It should prioritise topics that have demand in France, then map each article to a distinct intent. A broad guide might support awareness, while a local comparison page supports commercial investigation.

If the German business later develops a separate legal entity, sales team and product catalogue, it could migrate to example.de. That move would require careful redirect mapping, backlink outreach and post-migration monitoring. Architecture can evolve, but each change carries risk.

Migration guidance: changing structures safely

A move from subdomains to subdirectories, or from a global domain to country domains, should be treated as a major SEO migration.

Before launch:

Crawl the existing site.
Export all organic landing pages.
Record rankings, clicks and conversions.
Map every old URL to a precise new URL.
Prepare one-to-one 301 redirects.
Update canonicals and hreflang.
Update XML sitemaps.
Review internal links.
Check structured data.
Confirm analytics and Search Console properties.
Prepare a rollback plan.

After launch:

Test redirect chains and loops.
Monitor index coverage daily at first.
Check the correct regional URLs in search results.
Review organic traffic by market.
Inspect priority URLs manually.
Track lost backlinks and recover important links.
Watch server logs for crawl behaviour.
Review rankings for commercial pages.
Investigate sudden URL switching.

Avoid combining an architecture migration with a redesign, CMS change, domain rebrand and large content deletion unless there is no practical alternative. Too many simultaneous changes make diagnosis much harder.

Common mistakes to avoid

Using subdomains for convenience

A subdomain may be easy for a development team but expensive for an SEO team. If the only reason is technical convenience, compare it against the long-term authority and reporting costs.

Creating a country domain without local evidence

A country extension does not make generic translated content local. Users may still see through weak localisation, and search engines may not reward pages that lack market relevance.

Treating translation as keyword research

Literal translation can miss the phrases users actually type. Local SERP research should inform titles, headings, product language and internal anchors.

Publishing every page in every language

A large international site can accumulate thousands of low-value pages. Translate content that supports demand, conversions or customer needs. Do not create URL volume for its own sake.

Ignoring keyword cannibalisation

Every new regional page should be checked against existing URLs. This is especially important when multiple teams publish independently.

Relying only on hreflang

Hreflang cannot repair poor content, incorrect canonicals, broken redirects or unclear page intent. It is one signal within a larger system.

Redirecting users automatically by IP

Automatic redirection can block access to alternative versions and create frustrating experiences. Use clear selectors and explain regional differences where necessary.

Key takeaway: choose the structure you can govern

Subdirectories are often the most efficient choice for centralised international growth and market testing. Subdomains can be appropriate when regions require technical or organisational independence. Country domains provide the clearest local identity, but they demand the strongest investment in content, links, technical SEO and local operations.

The architecture itself will not create international visibility. Your results will depend on accurate search intent mapping, useful localisation, consistent hreflang, logical internal linking and ongoing monitoring for keyword cannibalisation.

If you’re building a multilingual publishing operation, use SEO Letters to move from keyword discovery to structured, market-specific articles and scheduled content campaigns. Set the topic, language, publishing cadence and destination, then keep reviewing performance, consolidation opportunities and local search signals as the site develops. For more detailed workflow guidance or contact support, use the rightbar contact path.