Selling into several countries without duplicating yourself
International SEO is structuring a site to serve several countries or languages. The two decisions that matter most are the URL architecture — subfolders, subdomains or separate domains — and hreflang, which tells search engines which version belongs to which audience. The failure mode is duplication rather than absence.
The instinct when expanding into a new market is to copy the site and change the country name. It produces several pages competing for the same queries with the same content, none of which is clearly the right answer for anyone. International SEO is mostly the discipline of making each version genuinely different enough to deserve separate existence.
Three faults recur. Country versions are near-identical, so search engines pick one and largely ignore the rest. hreflang is missing, one-directional or pointing at redirecting URLs, so the versions that do exist are not connected. And currency, terminology and examples are left unchanged, so a UK visitor reads American spelling and dollar prices and concludes the company does not operate there.
When this work makes sense
Questions worth asking any supplier
Will each country version carry genuinely different content, or the same content relocated? The second is duplication.
Subfolder, subdomain or separate domain? Subfolders concentrate authority; separate domains fragment it and need independent building.
Is hreflang reciprocal? A one-way declaration is frequently ignored.
Are you targeting countries or languages? They are different axes and conflating them creates unservable combinations.
Does each market have someone who knows it? Localisation written from a desk in another country reads like it.
Deliverables
URL architecture recommendation with the trade-offs stated rather than asserted
hreflang implementation, reciprocal and validated in the rendered output
Per-market content differentiation — currency, terminology, examples, regulation, audience
Country-specific keyword research, since terms differ beyond spelling
Canonical discipline so country versions never canonicalise to each other
Search Console configuration per market
A similarity check across market versions before publication
Built with
Process
Every international build runs a similarity check between market versions before anything is published. We compare each country's page against its counterparts and reject pairs that are substantially the same text with the country swapped. It is the same test this site applies to its own country pages, and it is the difference between four pages that each rank in their market and four pages that collectively rank nowhere.
The standard nine stages — discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement, continuous improvement — apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Subfolders, subdomains, or country domains
Subfolders (/uk/, /uae/)
Fits: Most businesses — authority concentrates on one domain and setup is simplest
Limits: Weaker geographic signal than a ccTLD; all markets share one domain's reputation
Subdomains (uk.example.com)
Fits: Cases where markets need separate technical infrastructure
Limits: Authority is partially separated, with the complexity of domains and few of the benefits
Country domains (example.co.uk)
Fits: Established businesses with the resources to build each market independently
Limits: Each domain starts from nothing; fragments your authority across several properties
Case studies
This site is itself built on the architecture described here: four country trees with reciprocal hreflang and a 35% similarity cap enforced between market versions at build time. The structure is inspectable rather than asserted.
MBGDesk operates from 4 offices — India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
Should we use a .co.uk or a subfolder?
A subfolder for most businesses. A ccTLD gives a stronger local signal and starts with no accumulated authority at all — you are building a new site's reputation from zero. Unless you have the resources to run each market as its own property, the subfolder concentrates what you already have.
Do we need to translate everything?
Translation and localisation are different things. Translation gives you the same content in another language. Localisation changes the examples, currency, regulation and terminology so it reads as though written for that market. Translated-only pages frequently rank for nothing because the keywords were never researched in the target language.
What is hreflang and do we need it?
It tells search engines which version of a page belongs to which language or country audience. You need it once you have equivalent pages in more than one market. It must be reciprocal — every version listing every other, including itself — or it is commonly ignored.
Our US and UK pages are competing with each other.
That is the classic symptom of duplication without hreflang, or duplication that hreflang cannot rescue because the pages are genuinely the same. Differentiating the content is the fix; hreflang alone will not resolve two identical pages.
How different do country pages have to be?
Different enough that you could not produce one by find-and-replacing the country name on the other. In practice that means market-specific facts: regulation, payment methods, competitive landscape, local platforms, seasonal patterns.
Can one page target several countries?
It can, using an x-default or a global version, and it is a reasonable starting point before you have market-specific content. It will underperform against competitors who have built for each market individually.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.