If your website only speaks one language, your revenue does too.
The internet is global by default. Your website probably is not.
Updated October 2026: expanded with what we learned shipping Cool Web Tool in ten languages, a technical checklist, and links to Google's own guidance.
What Localisation Actually Means
Translation changes the words. Localisation changes the experience. A German visitor should see prices in euros, dates in the order they expect, examples that make sense in their market, and terms that match local law.
- Language adaptation
- Cultural tone adjustment
- Local currencies
- Local date and number formats
- Regional search behaviour
- Legal and compliance differences
- Payment preferences
Interface Localisation and Search Localisation Are Different Projects
We learned this on our own product. The Cool Web Tool app runs in ten locales: US and UK English, German, Spanish, French, Italian, Japanese, Brazilian Portuguese, Russian and Turkish. A cookie remembers which one you picked.
That works well for people who are already using the product. It does almost nothing for search.
Google recommends a separate URL for each language version. Its documentation also notes that Googlebot usually crawls from the United States without asking for a particular language. So if the language depends on a cookie, Google mostly sees one version of each page.
Our marketing pages have one URL each today, and our hreflang tags say exactly that: one English page, also marked as the default. We chose that on purpose. A translated interface helps the users you already have. Translated pages that rank in each market are a separate and bigger project, with their own URLs, keyword research and upkeep.
If you are planning localisation, decide early which of the two you are building.
Why Localisation Matters for SEO
People search in their own language, and the same product often has different names in different markets. Even within English, spelling splits demand: this post says "localisation", while most US searchers type "localization". We keep separate US and UK English text in our own product for that reason.
- Different spelling across regions
- Different keywords for the same product
- Different intent in different markets
- Regional search engine preferences
Before you translate anything, open Google Search Console and filter performance by country. Impressions from a country where you have no local page are a sign of existing demand. Research keywords in each language separately. Translating your English keyword list rarely gives you the terms people actually use.
Technical SEO Checklist for Multilingual Sites
- One URL per language. Subfolders such as
/de/are the simplest to run. Do not rely on cookies or browser settings alone. - Hreflang on every version. Each page lists all its language versions, including itself. Every link must be returned by the page it points to, and an
x-defaultentry tells search engines which version to show everyone else. - A canonical tag for each language. Each translation points its canonical tag at itself. If you point every translation at the English page, you are asking Google to ignore the translations.
- Translate the visible page. Google says it works out a page's language from its visible content, not from the
langattribute or the URL. A translated menu around English body text is still an English page. - Translated titles and meta descriptions. They are the first text a searcher sees.
- No forced redirects by location. Suggest a language, but let people and crawlers reach every version.
- Local structured data. Use the right currency in product and offer markup.
- Language versions in the sitemap. List every version so crawlers can find them all.
Our site audit checks the hreflang part of this list. It flags missing return links, a missing x-default and duplicate entries, because those are the mistakes that quietly make hreflang useless.
AI Visibility and Localisation
More people now ask ChatGPT, Gemini, Perplexity, Claude or Grok instead of typing a query into a search box, and they ask in their own language. When the only page that explains your product is in English, an answer in Italian has two options. It can translate your page on the fly, or it can cite a local competitor who already wrote in Italian.
We have not seen a published study that measures this cleanly, so treat it as reasoning rather than proof. It is still worth testing. Ask the assistants your customers use the questions they would ask, in each language you sell in, and see which sites they mention and cite.
Where the Revenue Comes From
Traffic is only the first step. The revenue comes from what happens after someone arrives: whether prices make sense in their currency, whether checkout offers a payment method they trust, and whether support answers in their language.
Ignoring non-English markets leaks revenue in places no single report shows. You can measure it if you look:
- Search Console impressions and clicks by country
- Analytics sessions by browser language
- Sign-up and checkout completion by country
- The language of incoming support tickets
When Should a Startup Localise?
- You have product-market fit in one market
- You see international organic traffic
- You receive support tickets from non-English users
- Competitors are expanding regionally
And when to wait: if you cannot keep a language up to date, do not launch it yet. A translation that is six months behind the English page makes the whole brand look neglected. Start with one market where you already see demand, do it properly, then add the next.
How to Keep Translations From Going Stale
Most localisation fails slowly. Someone updates the English copy, and the other languages fall behind one string at a time.
Our fix is boring and it works. US English is the source of truth for every piece of interface text. An automated test fails the build if any other locale is missing a key that US English has. No release goes out with a half-translated screen.
You do not need our setup to copy the idea. Pick one source language, keep translations in the same repository as the code, and make a missing translation block a release in the same way a failing test would.
Final Thought
Localisation is not design polish. It is distribution strategy. If you want to grow globally, speak globally, and give every language a page that search engines and AI assistants can actually read.
Sources: Google Search Central, Managing multi-regional and multilingual sites, Tell Google about localized versions of your page and How Google crawls locale-adaptive pages.
