Resources

International SEO guide for UK businesses

A step-by-step guide for UK businesses selling into other countries or languages: whether you need separate versions, which URL structure to choose, how to set up hreflang without the usual errors and what to localise first.

International SEO is the work of making sure that, when your business sells into more than one country or language, each market sees the right version of your site in its own search results. For a UK business that usually means an Irish customer lands on a page priced in euros, an American buyer sees dollars and US delivery terms, and a German speaker gets German copy rather than an English page they have to puzzle through.

This guide sets out how I would plan it, in order: deciding whether you need it at all, checking demand, choosing a URL structure, setting up hreflang, localising the pages and measuring each market separately. It is written for UK firms expanding abroad, not for overseas businesses targeting the UK. If the term is new to you, my glossary entry on international SEO gives the short version.

Do you need international SEO at all?

Plenty of UK businesses that take overseas orders do not need separate country versions. If you sell the same thing, in English, at one price, and the overseas sales arrive without any effort, a single well-built site is usually enough. Adding country versions creates more pages to maintain, more places for errors and, done badly, versions that compete with each other.

You probably do need it when one or more of these is true:

  • Prices, currency, tax or delivery terms differ by country, and showing the wrong ones loses the sale.
  • You want to rank in a market where people search in another language.
  • Your product range, regulation or legal terms differ between countries, so one page cannot honestly serve both.
  • You have staff, premises or a distributor in another country and customers there need local contact details.

If none of these applies, put the effort into the UK site instead. You can add a market later; unpicking a rushed international set-up is far more work than building it properly once.

Step 1: Check there is demand in each market

Before any structure decision, confirm that people in the target country search for what you sell, and find out how they phrase it. Translating your UK keyword list does not do this. A term that is standard in Britain may be rare elsewhere, and the words a German or French buyer actually types are often not the dictionary translation.

English-speaking markets catch people out too. Americans say pants for trousers, vacation for holiday and cell phone for mobile; Irish searchers share most British vocabulary but not all of it. Keyword research done separately for each market, ideally checked by a native speaker, tells you which pages each version needs and whether the market is worth the cost of entry.

Write down, per country, the handful of searches that would bring you profitable customers and who already ranks for them. If the results are dominated by local firms with local addresses and you have no presence there, that is useful to know before you build anything.

Step 2: Choose a URL structure

There are four common ways to separate country or language versions. Each sends a different strength of signal and carries a different running cost.

StructureExampleStrengthsDrawbacks
Country-code domainsexample.co.uk, example.ie, example.deThe clearest signal of which country a site is for; trusted by local buyersEach domain builds its authority separately; more hosting, renewals and admin; some registries have eligibility rules
Subfolders on one domainexample.com/uk/, example.com/ie/One domain, so links and authority are shared; cheapest to runWeaker country signal than a country domain; needs hreflang done well
Subdomainsuk.example.com, ie.example.comCan be hosted separately if a local team runs each versionOften treated more like separate sites, without the local trust of a country domain
URL parametersexample.com/?country=ieQuick to bolt onHard for search engines and people to tell apart; I would not use it

For most UK small and mid-sized businesses I recommend subfolders on a generic domain such as a .com, because everything you earn in links and reputation helps every market at once. Country domains make sense when you will run each market seriously and local trust in the domain matters to buyers.

UK-specific points on domains

  • A .co.uk domain tells Google the site is aimed at the UK. That is ideal for a UK-only business and a handicap if you want one site to rank worldwide. A generic top-level domain such as .com has no country attached.
  • Google treats some country-code domains, such as .io, .ai and .co, as generic because so many businesses use them without any link to the country. Check Google’s guidance on multi-regional sites before relying on one as a country signal.
  • Since the UK left the EU, businesses established only in the UK can no longer register .eu domains, and Irish .ie domains require a demonstrable connection to Ireland. Confirm eligibility with the registry before planning around either.

If you are moving an existing UK site into a new structure, for example from example.co.uk to example.com/uk/, treat it as a migration: map every old URL to its new home and redirect it. That is a separate project with its own risks, covered in my website migration SEO service.

Step 3: Set up hreflang so each market gets the right version

Hreflang is an annotation that tells search engines which pages are equivalent versions of each other and which language and country each one serves. It does not lift rankings by itself. What it does is swap in the right version: an Irish searcher who would have seen your UK page sees your Irish page instead.

Each value is a language code, optionally followed by a country code. A few you are likely to need:

ValueMeaning
en-GBEnglish, for the United Kingdom
en-IEEnglish, for Ireland
en-USEnglish, for the United States
enEnglish, for any country not listed separately
de-DEGerman, for Germany
x-defaultThe fallback for everyone else, often a country or language selector

You can add the annotations in the page head, in HTTP headers (useful for PDFs) or in the XML sitemap. Pick one method per site. The sitemap is often easiest to keep accurate on large sites because it can be generated from one list of equivalent pages.

The errors that stop hreflang working

  1. Using UK instead of GB. The country code for the United Kingdom is GB, so en-uk is not a valid value and is ignored. It is an easy slip on British sites, because UK is what most people naturally type.
  2. Missing return links. If the UK page names the Irish page as its equivalent, the Irish page must name the UK page back. One-way annotations can be disregarded.
  3. No self-reference. Every page in a set should list itself as well as its alternatives.
  4. Pointing at the wrong URLs. Every URL in a set should return a 200 status, be indexable and be its own canonical. Annotations pointing at redirects, noindexed pages or pages whose canonical tag names a different URL send conflicting instructions.
  5. Canonicalising every version to the UK page. This tells Google the other versions are copies to drop, which undoes the whole set-up. Each version should carry a canonical pointing to itself.

Google’s own documentation on telling Google about localised versions of a page is the reference to check against. Hreflang errors are easy to make at scale and hard to spot by eye, so any technical SEO review of a multi-country site should crawl and check every set.

Step 4: Localise more than the words

A German page that is a careful translation of the UK page but still shows sterling prices, UK delivery times and a London phone number will convert poorly however well it ranks. Work through these in roughly this order, because the first items are the ones that lose sales:

  1. Prices, currency and tax. Show the local currency, and make clear whether import duties or local VAT are included. Since Brexit, EU buyers can face charges on delivery from the UK, and an unexpected bill at the door can lead to refused parcels and poor reviews.
  2. Delivery and returns. Realistic delivery times, costs and a returns process that works from that country.
  3. Contact details and trading information. Local or international phone formats, opening hours in the local time zone and the legal information each market expects.
  4. Language and terminology. Native-quality copy using the words that market searches for, with spelling to match: American English for US pages, British for UK and Irish ones.
  5. Proof and examples. Payment methods, standards and references that mean something locally.
  6. Privacy and cookie notices. The rules differ between the UK, the EU and US states; each version should reflect where its visitors are.

Same-language versions, such as UK and Irish English, can share most of their copy. That is not a duplicate content problem as long as hreflang connects them, but the prices, delivery details and contact information must genuinely differ, otherwise there is no reason for the second version to exist.

Step 5: Strengthen the signals beyond hreflang

Hreflang chooses between versions you already have. Whether a version earns a place in that country’s results at all depends on the same things as any SEO: useful pages, sound technical foundations and a reputation in that market.

  • Local links and mentions. Links from trade bodies, publications and partners in the target country tell search engines you are active there.
  • Language in the visible content. Google works out a page’s language from what people can read, not from the code. Keep navigation, buttons and footers in the page’s language too.
  • No automatic redirects by location. Sending visitors to a version based on their IP address can stop search engines, which mostly crawl from US addresses, ever reaching your other versions. Suggest the right version with a banner and let people choose.
  • Real local presence where it exists. A Google Business Profile is for premises or staff that genuinely serve customers in that country, not for a market you only ship to.

Step 6: Measure each market on its own

A single traffic total hides whether a new market is working. In Google Search Console, filter the performance report by country, and with subfolders you can add each folder as its own property so every market has its own data. In GA4, report on the country dimension and set up conversions that make sense locally, such as orders in euros or enquiries from an Irish form.

Give each market a few months of data before judging it, and compare it against the demand you recorded in step 1, not against the UK site’s figures.

Common mistakes when UK businesses expand abroad

  • Country pages for markets you cannot serve. Thin pages that swap a country name into the same text are a poor experience and can be treated as doorway pages. Only build versions for places you deliver to and support.
  • Keeping a .co.uk for a worldwide business. If you genuinely want one site to rank everywhere, a UK domain works against you.
  • Launching every market at once. Start with one, usually the closest in language and logistics, which for most UK firms is Ireland. Get the process right, then repeat it.

Next steps

Write down which markets you serve today, what differs for each and what you would need to change on the site. That list decides your structure more reliably than any rule of thumb. If you want help with the planning and hreflang itself, my international SEO service for UK businesses covers both. If you would like a second opinion on how your current site handles overseas visitors, request a free SEO audit and I will tell you what I would fix first.

Updated

Frequently asked questions

Do I need hreflang if my site is only in British English?

No. Hreflang only does something when two or more versions of a page exist for different languages or countries. A single UK site with no alternatives gains nothing from it, and tags pointing back at the same page are just one more thing to maintain. Set the page's language attribute correctly and leave hreflang until a second version exists.

Can one English version serve several countries?

Yes. If your offer is the same across most English-speaking countries, one version tagged with the language code alone (en) can cover them, alongside specific versions such as en-GB and en-IE where prices or terms differ. Build a country version only where something on the page genuinely has to change.

Can I use AI or machine translation for other language versions?

As a first draft, yes. Before publishing, have a native speaker who knows your sector review the copy and check it uses the words customers in that country actually search for. Pages that read as automated tend to convert poorly even when they rank.

Does it matter which country my website is hosted in?

Very little. Google's guidance on multi-regional sites treats server location as a weak hint compared with the URL structure, hreflang and the content itself, and a content delivery network serves pages from near each visitor anyway. Choose hosting on speed and reliability rather than on where the server sits.

Ready to talk about your project?

A straight answer about what would move the numbers, and a written proposal if we are a fit.