International SEO strategy and services
International SEO strategy decides how a site serves different countries and languages: which markets to prioritise, whether to target languages or countries, which domain structure to use, and how far to localise content. These choices are expensive to reverse, so they deserve analysis before implementation.
By ROI SynthUpdated 11 min read
The problem this solves
Common options include country-code domains, subdirectories and subdomains. Each has trade-offs in signals, cost and operational complexity. The right choice depends on the business: a retailer with country-specific pricing and stock has different needs from a software company with one global product.
Businesses often translate a site and assume the job is done. But search behaviour, terminology, competitors, regulations and even product availability differ between markets, and machine-translated pages without local review can read poorly.
What the work includes
- Market prioritisation using demand and business data
- Language versus country targeting decision
- Domain structure recommendation with trade-offs
- Localisation requirements by market
- Hreflang and internationalisation technical plan
How the work is done
Assess markets
Estimate demand and competition for priority countries and languages.
Choose targeting
Decide where content genuinely differs by country, not just language.
Choose structure
Select the domain approach that fits budget, signals and operations.
Plan localisation
Define what must be adapted locally beyond translation.
When the business crosses borders before the website does

International SEO strategy decides how your website serves different countries and languages. The decisions are structural — which markets to target, whether to organise by language or country, which domain structure to use, how much to localise — and they are expensive to reverse. A business that launches five country sites on separate domains and later wants to consolidate faces a migration; one that translates everything into ten languages without demand faces years of maintenance.
On coded websites these choices show up in routing, middleware and content models. Frameworks like Next.js support internationalised routing well, but the framework does not decide your strategy. That has to come first, based on where your customers are and what each market needs.
- You sell or plan to sell in several countries, and the site serves one market.
- Your site detects location and redirects visitors automatically, and you are not sure what search engines see.
- You have country sites on different domains, built at different times, with inconsistent content.
- Translated pages exist but do not appear in search in their target markets.
- You are planning an international expansion and want the site structure right from the start.
Target languages, countries, or both?
The first decision is whether your markets differ by language, by country, or by both. A software company selling the same product worldwide may need only language versions: one Spanish site serves Spain, Mexico and Argentina. A retailer with different prices, delivery terms and regulations per country needs country versions, even where the language is shared: British and Irish customers both read English but pay in different currencies.
The answer can differ by section of the site. Product documentation might be by language while pricing and legal pages are by country. Making that explicit early prevents a structure that fights the business later.
| Your situation | Usually target | Example |
|---|---|---|
| Same offer everywhere; only language differs | Languages | /es/ serving all Spanish speakers |
| Prices, delivery or law differ by country | Countries | /en-gb/ and /en-ie/ with different prices |
| Both apply | Language-country combinations | /fr-fr/, /fr-ca/, /en-ca/ |
| One market abroad, small | Possibly none yet | Serve from the main site until demand is proven |
Subfolders, subdomains or separate domains

There are three common ways to structure an international site, each with real trade-offs. None is universally best; the right choice depends on your markets, your team and how independent each market needs to be.
Subfolders (example.com/de/)
One domain, one codebase, shared authority. Easiest to run on a coded site with internationalised routing. Usually our default recommendation.
Subdomains (de.example.com)
Some separation for hosting or teams, at the cost of more configuration. Useful when markets genuinely run on different infrastructure.
Country domains (example.de)
The strongest local signal and sometimes a trust advantage, but each domain builds authority separately and costs more to maintain.
Whatever the structure, avoid relying on automatic redirection by IP address or browser language. Search engine crawlers often come from one country, and automatic redirects can hide your other versions from them. Offer a clear, crawlable way to switch versions instead, and suggest a version to visitors without forcing it.
Translation is the start, not the end
A translated page that keeps the original's examples, prices, units, regulations and search terms often fails in its new market. People search differently in each country, even in the same language, and they expect local details: their currency, their payment methods, their delivery times, their legal references.
We plan localisation per market: which pages need full adaptation, which can be translated with light changes, and which can stay in the original language for now. Research is done in each market's language, ideally with a native speaker, so pages target the words people actually use. On a coded site, localised fields in the content model keep market-specific details — prices, legal notes, contact numbers — separate from shared copy.
Choosing where to start
Expanding into every market at once spreads effort thin. We prioritise markets using evidence: existing visits and enquiries from each country in your analytics, search demand for your services in each language, competition in each market, and your business's ability to serve customers there. A market where you already receive enquiries in English may justify localisation sooner than one with larger theoretical demand.
The result is a phased plan: one or two priority markets done properly first, measured, then expanded. That lets you learn what works before committing to the full set.
A hypothetical expansion plan
A hypothetical UK-based software company sells to small businesses and wants to grow in Germany, France and the United States. Its Next.js site is English only, and middleware redirects visitors by IP address.
The strategy keeps one domain with subfolders. The US gets a country version, since pricing, spelling and some features differ. Germany and France get language versions after research shows demand in their own terms. The IP redirect is replaced by a suggestion banner and a visible language switcher. Germany goes first because analytics shows existing German visitors and trial sign-ups. Key pages — homepage, pricing, three feature pages and the main comparison — are fully localised with a native reviewer. Hreflang is generated from the content model. France follows once Germany's results are measured.
How the strategy work runs
The strategy is delivered within the SEO offer, typically over the first one to two months, followed by phased implementation per market.
| When | What happens | What you see |
|---|---|---|
| Weeks 1–2 | Market evidence gathered; current routing and redirects reviewed | A market summary and technical findings |
| Weeks 3–4 | Targeting and structure decided; priority markets chosen | A written strategy with reasons for each choice |
| Month 2 | Routing, content model and hreflang implemented; first market localised | First market live and correctly annotated |
| Later months | First market measured; further markets in order | Market-by-market reports |
Measuring each market
Each market is reported separately: impressions and clicks from that country or language in Search Console, the version of each page shown to searchers there, visits and enquiries in analytics. We also check that the right version appears in the right market. If the UK page appears to US searchers, or the German page is missing from results in Germany, that points to a technical or content problem worth fixing before expanding further.
What we need from you
We need to know your commercial plans for each market — where you can actually serve, ship, support and bill — because the strategy must match the business. We also need access to analytics and Search Console, repository access for routing and content-model changes, and native-language reviewers for priority markets, whether in your team or from a translation partner.
Internationalised routing done well
Frameworks like Next.js provide tools for internationalised routing, but defaults are not strategy. A few implementation details decide whether search engines can find and correctly serve each version.
Every version has its own URL
Language or country versions live at distinct, crawlable addresses, never only behind a cookie or a script that swaps text.
No forced redirects
Middleware suggests a version based on location or browser language but does not force it, so crawlers and travellers can reach every version.
Localised metadata
Titles, descriptions and structured data are translated and localised along with the page, not left in the default language.
Generated alternates
Hreflang and canonical tags come from the same data that knows which versions exist.
Localised formats
Dates, currencies, numbers and units follow each market's conventions.
International mistakes that are expensive to undo
Because international structures are hard to change, early mistakes linger for years. These are the ones we see most.
- Launching many languages at once with thin translations, then struggling to maintain them all.
- Choosing separate country domains for markets too small to support their own authority.
- Redirecting visitors and crawlers by IP address, hiding versions from search engines.
- Translating keywords literally instead of researching how each market searches.
- Leaving prices, legal notes and contact details from the home market on localised pages.
- Forgetting that every new version needs its own Search Console view and reporting.
The deliverables, listed
The strategy is a written document with decisions and reasons, followed by implementation in your code.
- A market prioritisation with the evidence behind each choice.
- A targeting decision — languages, countries or both — per section of the site.
- A recommended URL structure with the trade-offs explained.
- A localisation plan stating which pages are adapted, translated or left as they are.
- Routing, content-model and annotation changes implemented for the first market.
Evidence of demand before you translate
Translating a site is a real commitment: every page you publish in a language is a page you must keep accurate in that language. Before committing, it is worth gathering evidence that the market wants what you offer. Your own analytics often hold the first signs — visits, sign-ups or enquiries from a country, even though the site is not in its language.
Search data in the target language adds a second view: how often people search for your services there, in their words, and what competes for those searches. Sales knowledge adds a third: whether you can price, deliver, support and bill in that market. Where all three point the same way, the case for localising is strong. Where they disagree, a smaller step — a single localised landing page, or English pages adapted for the market — can test demand at lower cost.
Localisation includes the boring parts
Localised pages must also meet local expectations that have nothing to do with search: currencies and tax display, consumer rights and returns language, privacy and cookie notices, business registration details, and contact routes customers in that country can use. Missing these can undermine trust, and in some markets they are legal requirements.
We flag these items in the localisation plan so they are owned by the right people in your business. We do not give legal advice; we make sure the website has a place for each requirement and that the content model can hold market-specific versions of it.
Keeping several languages accurate
The hidden cost of international sites is maintenance. Every price change, policy update or new feature has to reach every language version. Without a process, translations fall behind and visitors in some markets read outdated information, which damages trust and can mislead.
We design for maintenance from the start. Facts that change — prices, contact details, legal notes — live in structured fields rather than prose, so they update in every language at once. Prose that needs translating is tracked by source version, so when the original changes, the translations are flagged as needing review. A named owner for each market approves changes. On coded sites, a simple script can list pages whose source text changed after their translation was last updated.
This is also why we recommend starting with fewer languages done well. Each additional version multiplies maintenance; the plan should match your capacity to keep every version accurate.
Markets where Google is not the whole story
In most markets Google dominates search, but not everywhere, and not for every audience. Some countries have strong local search engines with their own webmaster tools and requirements, and some audiences search heavily inside marketplaces, maps or social platforms. Before committing to a market, we check which search engines and discovery channels people there actually use for your kind of service.
Where another search engine matters, we review its documentation for language targeting, indexing and verification, and set up its webmaster tools alongside Search Console. The fundamentals — crawlable pages, clear language signals, localised content — carry across, but the details and the reporting differ, and the strategy should say so plainly.
How international strategy connects to other work
The strategy is implemented technically through hreflang implementation, which tells search engines which version suits which audience. Research in each market draws on keyword and search intent research. Moving existing country sites into a new structure is a site migration, and multi-country businesses with physical locations also need multi-location SEO.
Which offer includes international SEO
International SEO strategy is delivered within the SEO offer, from $200 per month, or All-in-One SEO + AEO + GEO, from $300 per month. Each additional market or language adds research, content and technical work, which moves the scope above the starting figure and is agreed in writing before work begins.
A new multilingual site can be built with internationalised routing and localised content fields through the Next.js + TypeScript Website Build, from $1,000 one time, with the number of languages part of the agreed scope.
Questions about going international
What businesses ask before expanding their site abroad.
"Should we buy country domains now?"
Registering them to protect your brand can be sensible. Using them as separate sites is a separate decision.
"Can we just auto-translate everything?"
As a draft, perhaps. Pages meant to win customers need review by someone who knows the market.
"Will duplicate content hurt us in English-speaking markets?"
Country versions with real local differences and correct hreflang are expected, not penalised.
"How many languages should we launch with?"
As few as the evidence supports, done well. Expand once the first markets are measured.
Example deliverable
How progress is evaluated
- Visibility and traffic by market
- Correct regional URLs appearing in each market's results
- Conversion rates by market
Who this is for
- Businesses expanding abroad
- Sites with poorly performing translated sections
- Companies choosing a domain structure
Limits and honest caveats
Common questions
questions
What is international SEO strategy and services?
International SEO strategy decides how a site serves different countries and languages: which markets to prioritise, whether to target languages or countries, which domain structure to use, and how far to localise content. These choices are expensive to reverse, so they deserve analysis before implementation.
What does a international SEO strategy and services engagement include?
The work includes market prioritisation using demand and business data, language versus country targeting decision, domain structure recommendation with trade-offs, localisation requirements by market and hreflang and internationalisation technical plan.
What problems does international SEO strategy and services solve?
Businesses often translate a site and assume the job is done. But search behaviour, terminology, competitors, regulations and even product availability differ between markets, and machine-translated pages without local review can read poorly.
How is international SEO strategy and services carried out?
It runs in 4 stages: assess markets, choose targeting, choose structure and plan localisation. Estimate demand and competition for priority countries and languages.
Who is international SEO strategy and services a good fit for?
It suits businesses expanding abroad, sites with poorly performing translated sections and companies choosing a domain structure.
How do you measure the results of international SEO strategy and services?
Progress is measured with visibility and traffic by market, correct regional URLs appearing in each market's results and conversion rates by market.
What are the limits of international SEO strategy and services?
New market sections usually need time to build visibility. Localisation quality depends on local expertise.
Can ROI Synth carry out the international SEO strategy and services work, or only recommend it?
Implementation is included. Within the agreed scope we fix templates, metadata, internal links and redirects, and build the landing pages ourselves, on your existing platform or on a Next.js and TypeScript build when a rebuild is part of the project, starting with steps such as “Market prioritisation using demand and business data”. Every completed item is recorded with evidence in a weekly progress sheet.
How long does international SEO strategy and services take?
The 4 stages (assess markets, choose targeting, choose structure and plan localisation) fit the proposal's four weekly phases. When the agreed scope can be delivered in a month, the proposal commits to completing it in the first month, subject to timely access and approvals. Search engines then take weeks or months to re-evaluate the changes.
Is international SEO strategy and services guaranteed to bring more traffic or leads?
No. Rankings, traffic, leads and sales depend on search engines, competition and your market, so they are not guaranteed. What is committed is the agreed work, completed and evidenced, and measurement of visibility and traffic by market and correct regional URLs appearing in each market's results.
Sources and further reading
Where to go next
Browse all servicesMore services
Contact us about International SEO strategy and services
Tell us about your website and goals. We will say plainly whether this is the right offer, what it would include, and what it can and cannot achieve.
Discuss international SEO strategy and services for your business
Tell us about your website and goals. We will confirm whether this work is the right priority, what it would include and how it would be delivered.
