Get the architecture right, not just the translation.
Going global means one business with a separate, correctly signposted front door for each market, whether that's two countries or ten.
By the Boltly team, Melbourne · Updated
We get the domain structure and hreflang right, then localise properly, so each market can rank instead of competing with itself. That means the wrong country's page stops showing up, regional versions stop cancelling each other out, and every market gets content written for how it searches.
What international SEO really is
International SEO is setting up a site so the right version ranks in each country or language you target. It is less about translation and more about architecture: telling search engines which pages serve which market through the right domain structure and hreflang, then localising each one. Whether you call it international, multi-region or multilingual SEO, the principle is the same.
Structure first
The right domain structure and hreflang decided before content, so each market is signposted correctly from the start.
Localised, not translated
Content adapted to how each market actually searches and buys, not a word-for-word swap that ranks for nothing.
Focused rollout
A few priority markets done properly beats flags in ten countries and rankings in none.
The mistake that sinks most global rollouts is treating it as a translation job. A business runs its site through a translation plugin, publishes a dozen language versions, and waits for traffic that never comes. The pages target phrases nobody in those markets searches, and search engines can't tell which version belongs to whom. Picture one company with a separate front door for each market: the sign above each door in that market's language, the address registered so the right customers arrive. Sort the address out first. The sign comes second.
A separate front door per market.
Each market you enter needs its own version of the site, correctly signposted so search engines send the right customers to the right door. Get that signposting right and each market ranks on its own; get it wrong and your pages compete against each other or show the wrong country entirely.
This is where most of the technical work lives. The domain structure decides where each market's pages sit, and hreflang tells search engines which version is meant for whom, so a shopper in London lands on the UK page with UK pricing rather than the Australian one. When it's wrong, you get the usual symptoms: the wrong page ranking in a market, versions treated as duplicates, and ranking strength quietly split three ways instead of concentrated where it should be.
ccTLD, subfolder or subdomain?
The domain structure is the first and most consequential choice, and the hardest to change later. Each option trades local signal against authority and effort.
Country domains (ccTLD)
The strongest local signal, but each market is a separate site, splitting your authority and costing more to run and maintain.
Strong signal, high effortSubfolders
All markets share one strong domain, so authority stays concentrated and it is the easiest to manage. The right choice for most businesses.
Best for mostSubdomains
Sit between the two on signal and authority, and are rarely the best option. Occasionally justified by technical or hosting constraints.
Rarely the pickWe labour this decision because it is hard to reverse. Migrating from country domains to subfolders, or the other way, means re-mapping every URL, redoing hreflang and riding out months of ranking instability while search engines relearn the site: the expensive clean-up good technical SEO exists to prevent. We make the call on three inputs: how many markets you're entering, how much domain authority you have to protect, and what you can resource. Testing one or two markets? Subfolders, because your existing authority works for every market at once. Running a large multi-region operation that can staff separate sites? Country domains can be worth the weight. Either way it should match the scale you operate at.
en-au → /au/ en-gb → /uk/ en-us → /us/
x-default → /au/
hreflang fails as a whole cluster.
hreflang is the tag that tells search engines which version of a page serves which language and region. It is unforgiving: every version has to reference every other version, including itself, so it works as a complete set rather than page by page.
- Every version references every other, with a self-reference on each page.
- Correct language and region codes, so en-GB and en-US are not confused.
- An x-default for searchers who match no specific market.
Your US page keeps showing up in Google Australia. Three usual causes.
An Australian searcher lands on US prices in US dollars, or a UK buyer sees your Australian shipping page. It's the most common sign that an international setup is fighting itself, and it nearly always traces back to one of these three faults.
The hreflang codes aren't ones Google accepts
Google only supports ISO 639-1 language codes and ISO 3166-1 region codes. The classic slip is writing the United Kingdom as "UK"; the code is GB. Google also ignores a pair of tags unless each page points back to the other, so a missing return link quietly cancels the set.
hreflang="en-UK"
hreflang="en-GB"
Every version's canonical points at one "main" site
A canonical tag tells Google which URL is the real one. When the Australian, UK and US pages all name the US page as canonical, you've told Google the other two are copies, and it has little reason to show them anywhere. Each regional version you want ranked should name itself as canonical and list its siblings in hreflang.
/au/page → canonical /au/page
/uk/page → canonical /uk/page
Visitors are redirected by where they seem to be
Automatic redirects based on a visitor's IP address or browser language feel helpful, but Google's guidance on multi-regional sites says to avoid them: they can stop people, and Google's crawler, from reaching the other versions at all. Show a clear country switcher instead, and let the hreflang set do the routing in search results.
Better: a banner that says "Looks like you're in the UK. Go to the UK site?"
Sources: Google Search Central, "Tell Google about localized versions of your page" (updated 21 September 2026) and "Managing multi-regional and multilingual sites" (updated 10 December 2025), both read 5 October 2026.
Translation swaps words. Localisation wins.
A translation plugin turns your English into other languages. It does not make you rank, because it targets the literal translation of your phrases rather than the terms that market actually searches. Localisation adapts the content to how people there search, buy and speak, and a plugin can't do that for you.
Translation
- Targets literal phrase translations
- Misses local search terms
- Wrong spelling, currency, units
- Present, but not competing
Localisation
- Targets terms locals actually search
- Local spelling, currency and units
- Examples and trust signals that fit
- Written to rank in that market
You don't have to cross a language barrier to need localisation. Australia, the UK and the US spell differently, use different words for the same thing (a ute, a pickup, a pick-up truck) and quote different currencies, so one identical page reused across all three limits how well any of them rank. Localising covers the search terms locals use, the spelling and units they expect, the currency and contact details that build trust, and examples that feel local rather than imported.
Everything a market entry actually needs.
A proper rollout covers six jobs per market, handled in order so nothing is bolted on after launch.
Domain architecture
The structure picked for your market count and authority, so signals sit where they should.
hreflang & signals
Complete, correct hreflang clusters plus the geo and language signals search engines rely on.
Localised content
Key pages localised for how each market searches, planned as part of the structure.
Per-market keywords
Keyword research for each target market, because they search differently even in one language.
Local authority
Building relevance and links within each market, since you start fresh in every new country.
Monitoring per market
Tracking rankings and issues country by country, so a problem in one market is caught fast.
Going global means starting SEO again in each new country. Your Australian authority doesn't fully carry across, so each market needs its own localised content, relevance and links, and the fundamentals behind our content and on-page SEO apply market by market. That's why we push for one or two priority markets first, proven, then expanded from a working template. Ten countries at a tenth of the effort each usually means none of them rank.
From architecture to a market that ranks.
A clear path that fixes the structure before the content, prioritises the markets most likely to pay back, and proves the template before scaling. You approve the architecture before anything is built.
Market & setup audit
We confirm your priority markets and audit any existing international setup, so we know what to build and what to fix.
Architecture plan
We choose the domain structure and design the hreflang, and plan the localised content each market needs. You approve it before we build.
Build & localise
We implement the structure and hreflang, and localise the key pages for how each market actually searches, not word-for-word.
Prove one market
We focus on the first priority market, build its authority and prove the template works before expanding to the next.
Expand & monitor
We roll out to further markets from the proven template and monitor rankings country by country, catching issues early.
Judge us on the plumbing.
These are three common starting points and what we'd do first in each, not client results. International SEO is won or lost in the technical setup, so that's what each plan leads with.
Map every country version, make each one point back to the others, and use full URLs so Google can pair them correctly.
Checked by: the right country page showing in each marketOpen one new market in a subfolder, research how people there search, and localise the key pages before adding a second.
Checked by: impressions and enquiries from that countryMove scattered country domains into subfolders with page-by-page 301 redirects, then watch each market's pages through the move.
Checked by: redirected pages indexed at their new URLsYou can tell a real international SEO agency from a plugin reseller by the questions they ask first. If the conversation opens with how many languages you want and how quickly, be careful. If it opens with which markets have demand for you, how much domain authority you have to protect and how your current structure is set up, you're talking to someone who sees the architecture problem. Judge any international SEO services on the boring parts: a correctly built hreflang cluster and a sensible domain structure, not a world map with pins in it. Ask them to walk you through the hreflang for one page across all your markets before you commit.
International SEO, answered.
International SEO is setting up a website so the right version ranks in each country or language you target. It is less about translation and more about architecture: telling search engines which pages serve which market through the right domain structure and hreflang, then localising the content for each one.
Hreflang is a tag that tells search engines which version of a page is meant for which language or region, so a UK searcher sees the UK page and an Australian searcher sees the Australian one. It matters because without it, search engines can show the wrong version, treat your market pages as duplicates, or split their ranking strength. Hreflang also fails as a whole cluster: every page has to reference every other version, including itself, so one mistake can break the set. Getting it right is the single most technical part of international SEO.
Each has trade-offs. Country domains like .co.uk send the strongest local signal but split your authority across separate sites and cost more to run. Subfolders such as /uk/ keep all your authority on one strong domain and are the easiest to manage, which suits most businesses. Subdomains sit in between and are rarely the best choice. The right one depends on how many markets you are entering, how much authority you already have and your resources.
Localise. Translation swaps words from one language to another; localisation adapts the content to how a market actually searches, buys and speaks, including spelling, currency, examples, units, and the specific terms people use. A word-for-word translation often targets phrases nobody in that market searches for. Localised content ranks because it matches how that market searches.
Usually fewer than businesses first want to. Each market needs its own localised content, its own authority and its own maintenance, so spreading thin across many markets at once tends to mean none of them get enough to rank. We generally recommend entering one or two priority markets properly, proving the architecture and the results, then expanding from a working template.
Yes, to compete properly. At minimum each market needs correctly localised versions of your key pages, and ideally content that reflects what that market actually searches for, which is not always the same as your home market. Even within one language, the UK, the US and Australia search differently and use different terms, so reusing identical content limits how well you rank. We plan localised content per market as part of the architecture.
Setting up the architecture, the domain structure and hreflang, happens up front, but building authority and rankings in a new market takes time, much like SEO in your home market. You are effectively starting fresh in each new country, so the first market usually takes several months to gain traction, with later markets often faster once the template is proven. Treat it as a market-entry investment measured in months, and start with the market most likely to pay back.
It depends on how many markets you are entering and how much localised content and technical work each needs, so we quote against a plan rather than a flat rate. Setting up the architecture for one or two markets costs far less than a large multi-region rollout with heavy localisation. We scope the work to your priority markets and budget, show you the plan and the price before starting, and there is no lock-in. See our pricing page for how our plans are structured and we will tailor one to your rollout.
The big three we see are: relying on a translation plugin and hoping, which produces thin, poorly localised pages; getting hreflang wrong, so search engines show the wrong version or treat pages as duplicates; and choosing the wrong domain structure, then having to unpick it later. All three come from treating international SEO as a translation task rather than an architecture task.
Usually one of three things. The hreflang codes are invalid (en-UK instead of en-GB) or missing their return links, so Google ignores them. Or every regional page's canonical tag points at one main version, which tells Google the others are copies. A third cause is redirecting visitors by IP address, which can stop Google reaching the other versions at all. Start with one page from each market and read its canonical and hreflang tags. That finds most cases in minutes.
Yes. Plenty of businesses have already gone global with a translation plugin or a rushed structure and are not ranking in their target markets, or are seeing the wrong pages appear. We audit the existing setup, find where hreflang, domain structure or localisation is failing, and fix it in the right order so you recover the markets you are losing. It is usually a plumbing fix rather than a start-over, and we'll tell you when a rebuild is the better call.
We start with your target markets and your current setup, then plan the architecture: the domain structure, the hreflang, and the localised content each market needs. You see the plan before anything is built, so the structure is right from the start rather than fixed later. Then we implement, prioritising the markets most likely to pay back, and report on rankings market by market.
Open the right door in every market.
Tell us your target markets and your current setup, and we will plan the architecture, the domain structure, the hreflang and the localised content, for you to approve before anything is built. A focused rollout that ranks, with no lock-in.