# Multi-language and multi-region websites | Plyo

> How to structure a site for more than one language or country, which URL pattern to pick, and the hreflang mistakes that quietly split your rankings.

Source: https://plyo.studio/blog/multi-language-and-multi-region-websites

1.  [Home](/)
2.  [Blog](/blog)
3.  Multi-language and multi-region websites

# Multi-language and multi-region websites

How to structure a site for more than one language or country, which URL pattern to pick, and the hreflang mistakes that quietly split your rankings.

Plyo Studio 16 November 2025 7 min read

On this page

[Pick the URL structure first](#pick-the-url-structure-first)[Get hreflang right](#get-hreflang-right)[Translation is the smallest part](#translation-is-the-smallest-part)[Start smaller than you think](#start-smaller-than-you-think) [Common questions](#common-questions)

Related service

[Astro websites](/services/astro)

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-default` for 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](/services/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.

## Keep reading.

[All posts](/blog)

-   [
    
    Engineering Image formats and sizes for a fast website 7 min read](/blog/image-formats-for-a-fast-website)
-   [
    
    Engineering Contact forms: stopping spam without losing enquiries 6 min read](/blog/contact-forms-stopping-spam)
-   [
    
    Engineering Headless CMS, explained without the jargon 6 min read](/blog/headless-cms-explained)

Updated 16 November 2025

FAQ

## Common questions

[Ask a question](/contact)

### Should I use a translation plugin?

Plugins that translate on the fly tend to produce pages search engines cannot index properly, and the quality is uneven. Pages built per language, with their own URLs, work better for both readers and search.

### Can I use the same content for Australia and the UK?

You can, but you should not use the same page. Give each market its own URL with local spelling, pricing and contact details, then connect them with hreflang.

### How do I know which markets are worth it?

Look at your analytics before you build anything. If 8% of traffic is already coming from a country you do not serve, that is a signal. If it is 0.3%, it is not.

About Plyo Studio

## Custom Astro websites. Built on Cloudflare.

Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.

Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.

[Start a project](/contact) [hello@plyo.studio](mailto:hello@plyo.studio) [About us](/about)

## Related pages

-   [Blog Read practical notes on designing, building and moving websites.](/blog)
-   [Astro websites Custom sites pre-built into lean HTML, for speed and search.](/services/astro)

Start a conversation

## Ready for a website that works harder?

[Start a project](/contact) [Free website audit](/audit)
