Multilingual SEO: A Guide for Businesses Targeting Global Markets
Table of Contents
Multilingual SEO is the process of optimising a website to rank in search engines across multiple languages and regions. For SMEs in Northern Ireland, Ireland, and the UK looking to reach customers beyond their home market, it covers everything from URL architecture and hreflang implementation to keyword research conducted in the target language rather than translated from English.
Getting this right requires more than running content through a translation tool. The technical decisions you make early on, which URL structure to use, how to signal language and region to search engines, and how to adapt keywords for local search behaviour, determine whether international visitors find your site or never see it at all.
What Is Multilingual SEO and Why Does It Matter for SMEs?
Multilingual SEO and international SEO are related but not the same thing. International SEO is the broader practice of making a site visible across different countries. Multilingual SEO specifically addresses sites serving audiences in more than one language, which may or may not involve different countries.
The Difference Between Translation and Localisation
Translation converts words from one language to another. Localisation adapts content so it reads as if it were written for that audience in the first place. A translated page may be accurate but feel foreign. A localised page uses the search terms, idioms, and reference points that a local user would actually type into Google.
The distinction matters for SEO because search engines rank pages based on relevance to a query. If your French page uses terms that French speakers do not search for, because they were translated from English rather than researched in French, the page will not rank, regardless of how technically sound the rest of the implementation is.
When Multilingual SEO Becomes Necessary
If your business sells to customers in more than one language region and you want organic search to be part of how you reach them, multilingual SEO is not optional. Businesses commonly trigger this need when expanding into Irish-speaking markets, EU countries post-Brexit, or any market where English is not the primary search language.
For web design and development projects involving international audiences, ProfileTree builds multilingual site architecture as part of the initial build specification, rather than retrofitting it later when structural changes are significantly more expensive.
Choosing Your URL Structure: ccTLDs, Subdirectories, and Subdomains
The URL structure you choose is one of the most consequential early decisions for a multilingual site. It affects how search engines attribute authority, how you manage content at scale, and long-term maintenance costs.
Subdirectories (example.com/fr/)
Subdirectories are the most practical choice for the majority of SMEs. All language versions sit under the same domain, which means any authority the root domain has accumulated benefits every language folder. There is no need to build separate domain authority from scratch for each language.
The trade-off is that subdirectories require clean internal URL management to avoid duplicate content, and hreflang implementation must be precise to prevent the wrong language version from appearing in search results.
Subdomains (fr.example.com)
Subdomains are treated by Google as separate entities from the root domain, so link equity does not automatically transfer. For most SMEs, building authority for a subdomain is effectively starting from zero in that language. Subdomains can make sense where a language version is a genuinely distinct product with its own team and link-building programme.
Country-Code Top-Level Domains (fr.example.com → example.fr)
ccTLDs provide the strongest geographic signal to search engines, but they come at a high cost. You are maintaining separate domains, separate authority-building efforts, and separate technical infrastructure for each market. This is rarely justified unless you are operating at enterprise scale with dedicated regional teams.
| Structure | Authority Transfer | Implementation Cost | Best For |
|---|---|---|---|
| Subdirectory (/fr/) | Full (inherits root domain authority) | Low | SMEs, most businesses expanding to 1-4 new languages |
| Subdomain (fr.) | Minimal (treated as separate by Google) | Medium | Distinct regional products with separate teams |
| ccTLD (.fr, .de, .ie) | None (entirely separate domain) | High | Enterprise businesses with regional operations |
“In my experience, using subdirectories for multilingual websites leads to a more centralised and stronger domain authority, which benefits SEO performance across all languages,” says Ciaran Connolly, founder of ProfileTree.
Implementing Hreflang Tags: Getting the Technical Foundation Right
Hreflang tags tell search engines which language and regional version of a page to show to a given user. Without them, Google may choose the wrong version or consolidate your language pages as duplicate content.
How Hreflang Tags Work
Each language version of a page must include an hreflang annotation pointing to every other language version of that same page, including itself. This creates what is called a return tag cluster. If Page A points to Page B but Page B does not point back to Page A, the cluster is broken, and search engines may ignore the annotations entirely.
A correctly implemented hreflang tag for a page targeting UK English looks like this:
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/page/" />
For a site targeting both Irish English and UK English, a common scenario for businesses operating across the island of Ireland and Great Britain, you would include both:
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/page/" />
<link rel="alternate" hreflang="en-IE" href="https://example.com/en-ie/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page/" />
The X-Default Tag
The x-default tag designates the fallback page for users whose language or region does not match any of your specific hreflang annotations. Always include it, pointing to your primary or most generic version of the page.
Common Hreflang Errors to Avoid
The most frequent mistake is incomplete return tag loops. Every page in the cluster must reference every other page. A second common error is mismatched URLs: using canonical URLs in some annotations and non-canonical versions in others. Google Search Console’s International Targeting report will flag both issues.
Multilingual Keyword Research: Beyond Direct Translation
Keyword research for multilingual SEO is not a translation exercise. The terms users search for in French, German, or Irish may have no direct equivalent to the English phrases you already rank for, and the search volumes can differ dramatically between regions that nominally share a language.
Why Translation Fails as a Keyword Strategy
Take a service like “web design Belfast.” A direct French translation would produce something no French speaker would type into Google. The relevant French query would reflect how that audience describes the problem they are trying to solve, using terms specific to their market and search habits.
This requires conducting keyword research from scratch in each target language, using tools set to the correct region and language, and ideally working with a native speaker to sense-check whether the terms reflect how real people talk about the topic.
Search Volume Variance Between Regions
Even within the same language, search volumes differ significantly by region. “SEO agency” behaves differently in the UK and Ireland, with distinct competitive landscapes and different commercial intent signals. Treating them as interchangeable is a common and costly assumption.
Localising Supporting Content Elements
Keyword localisation extends beyond body copy. Meta titles, meta descriptions, alt text, and schema markup all need to reflect local search vocabulary. Date formats, currency symbols, and measurement units also affect geographic relevance signals.
Targeting the UK, Ireland, and Northern Ireland: A Regional Spotlight
For businesses based in Northern Ireland, the UK, and Ireland, the multilingual and international SEO challenge is uniquely complex. No other part of the UK sits adjacent to a separate jurisdiction with a different currency, a different regulatory environment, and a different national language with its own search behaviour.
The en-GB and en-IE Distinction

Google treats en-GB and en-IE as distinct regional signals. A site targeting Northern Ireland and the Republic of Ireland simultaneously should use separate hreflang annotations for each, even though both are English-speaking markets. Localisation signals beyond language: price display, address format, phone number format, and domain all contribute to how Google determines geographic relevance.
A business serving both markets should have distinct pages for each, with locally relevant content. The impact of Brexit on digital marketing has made this distinction more operationally significant, particularly for e-commerce businesses managing separate tax and shipping rules.
Irish (Gaeilge) as a Search Language
For businesses targeting government-funded audiences or Gaeltacht communities, Irish-language content has genuine search value. Google indexes Irish-language content, and the language has its own ISO code (ga-IE) for hreflang purposes, making it a largely untapped opportunity.
Regulatory Considerations
Since Brexit, UK-based businesses targeting EU customers face different GDPR obligations from those operating solely within the EU. Cookie consent requirements may need to differ between UK and Irish pages, and bulky consent management implementations affect Core Web Vitals indirectly. Getting regulatory architecture right at the build stage is considerably cheaper than retrofitting it later.
Using AI for Translation Without Sacrificing SEO Quality
Current AI translation tools produce serviceable first drafts faster than human translation alone, but carry a risk practitioners call semantic drift: the translated text is technically accurate but uses terminology that does not match how people in that market actually search.
A Human-in-the-loop Workflow
Use an AI tool for the initial translation pass, then apply local keyword research to identify where the output has drifted from real search vocabulary. A native-speaking reviewer with SEO awareness edits for both cultural accuracy and keyword alignment before publication. This is meaningfully faster than full human translation and meaningfully more accurate than unreviewed machine output.
What AI translation cannot replace
Legal or compliance content, certified translations, and YMYL pages (health, finance, legal) require human expertise as the primary input. Google’s quality rater guidelines specifically flag unreviewed machine-translated YMYL content as a quality concern.
Taking the Next Step
Multilingual SEO rewards businesses that treat it as a technical and editorial discipline rather than a translation project. If you are building a site for multiple language markets or auditing an existing multilingual presence, the decisions around URL structure, hreflang implementation, and keyword research in each target language are worth getting right before content production begins. ProfileTree’s web design and development services include multilingual site architecture for clients with dual-market or international reach. Talk to the team to discuss your requirements.
FAQs
These are the questions businesses most commonly ask when starting multilingual SEO work.
What is the best URL structure for multilingual SEO?
Subdirectories (example.com/fr/) work best for most SMEs because they consolidate domain authority rather than splitting it across separate domains or subdomains.
Will Google penalise my site for AI-translated content?
Not if the content is accurate, useful, and human-reviewed. Unedited machine translation that produces low-quality or misleading content does carry a quality penalty.
How many hreflang tags are too many?
There is no hard limit, but large sites with hundreds of language variants should use sitemap-based hreflang rather than embedding tags on every page to avoid bloating <head> sections.
Do I need separate hosting in each target country?
No. A CDN distributes your content globally and satisfies Google’s page speed requirements without country-specific servers.
How do I handle SEO for UK English and Irish English on the same site?
Use en-GB and en-IE hreflang tags to separate the versions. Localise commercial signals (currency, address format, regulatory language) for each, even if the body content is largely shared.
Does a language switcher affect SEO?
Only if it uses forced redirects that prevent Googlebot from crawling all versions. A clean UI switcher that allows bots to access each language version without redirection does not harm SEO.