If you sell into more than one country, you have two separate decisions to make: whether you need more than one language, and whether you need more than one region. They are not the same thing. Australian and British English need different pages but not different translations.
Pick the URL structure first
Everything else follows from this, and changing it later means a migration.
| Pattern | Example | Best for |
|---|---|---|
| Subdirectory | site.com/au/ |
Most businesses. One domain, one pool of authority |
| Subdomain | au.site.com |
Separate teams or infrastructure per market |
| Country domain | site.com.au |
Strong local signal, and the most work to run |
For nearly everyone, subdirectories win. Your domain keeps all its authority in one place, you manage one certificate and one deployment, and adding a third market is a folder rather than a project.
Country domains make sense when local trust really matters, such as finance or healthcare, and when you have people in each market to run them.
Get hreflang right
hreflang tells search engines which version to show which visitor. It is simple and almost everyone gets it slightly wrong.
- Every version must list every other version, including itself.
- The references must be reciprocal. If the AU page points to the UK page, the UK page must point back.
- Use
x-defaultfor the page someone lands on when nothing matches. - Use the right codes:
en-AU,en-GB,fr-CA. Language first, region second.
Get it wrong and Google quietly picks for you, which usually means one market’s pages outrank the other’s in both.
Translation is the smallest part
The engineering is the easy half. What takes the time is everything attached to the words.
- Currency and tax. Prices shown in the local currency, with the local expectation about whether tax is included.
- Dates and numbers. 06/07 is two different days depending on where you are reading.
- Addresses and phone numbers. Local formats, and a local number if you can.
- Legal pages. Privacy and consumer law differ by market.
- Images. Photographs of a city your audience recognises beat generic stock.
Do not auto-translate your main content
Machine translation is fine for a first draft and poor as a finished product. Clumsy translation reads as carelessness in exactly the market you are trying to win. Translate the pages that matter, and leave the rest in one language rather than publishing bad versions of everything.
Start smaller than you think
Most businesses do not need every page in every market. Translate the pages that drive revenue: the homepage, the two or three services that sell, pricing, contact. Leave the blog in one language until the market is proven.
A site built on Astro handles this well because each market’s pages are pre-built, so there is no runtime cost to supporting four of them.
If you are planning a second market, send us your current analytics and we will tell you what we would build first.