Translating your website is the obvious first step into a new market, and it is where many companies stop. Then the translated pages attract almost no visitors, and nobody can explain why. International SEO is the work that fills that gap: making sure search engines understand which country and language each page serves, and that the content matches how local customers actually search. This guide explains what translation leaves out and what to put in place before you expand.
Why is translation not enough for international SEO?
Translation converts your existing words into another language. Search visibility depends on something different: whether your page matches the words people type, satisfies what they want to find and is technically clear to search engines.
A faithful translation can fail on all three counts. The translated term may be correct but rarely searched. The page may answer a question that buyers in that country do not ask. And without the right technical signals, search engines may show the wrong language version, or treat your versions as duplicates of one another.
How do you research keywords for each market?
Keyword research must be repeated for every market, in the local language, by someone who knows it natively. Translating your English keyword list does not work, for several reasons:
- Different words for the same thing. The literal translation is often not the term people use. Many markets adopt English terms for technology and business, while others prefer a local word.
- Regional variation within a language. Spanish in Spain and in Mexico, French in France and in Canada, and German in Germany and in Switzerland differ in vocabulary, spelling and formality.
- Different search behaviour. Demand for a product, the questions asked about it and the season in which it peaks all vary by country.
- Different search engines. Google leads in most markets but not in all of them, and the alternatives have their own rules.
The output should be a keyword map per market: which phrase each page targets, and which pages need to be created or dropped for that audience.
Which URL structure is best for a multilingual website?
Each language or country version needs its own distinct URL. There are three standard structures.
- Country-code domains, such as a .fr or .de address. These send the strongest country signal and are trusted by local users, but each domain builds authority separately and adds cost and administration.
- Subdirectories on one domain, such as /fr/ and /de/. All versions share the authority of a single domain, and the site is simpler to maintain. For most growing companies this is the practical choice.
- Subdomains, such as fr.example.com. These are easy to host separately but tend to share less authority with the main site than subdirectories do.
Whichever you choose, avoid two common mistakes. Do not use URL parameters or cookies to switch language on the same address, because search engines need a separate URL to index each version. And decide early whether you are targeting languages or countries: a single Spanish version serves all Spanish speakers, while separate versions for Spain and Mexico allow different pricing, vocabulary and offers.
What is hreflang and how do you implement it correctly?
Hreflang is an annotation that tells search engines which language and, optionally, which country a page is intended for, and where its alternative versions are. It helps the right version appear for the right user, and prevents similar pages in the same language from competing with one another.
It is also one of the most frequently broken elements on international sites. Check these points:
- Each page lists every alternative version, including itself.
- Annotations are reciprocal: if the English page references the French page, the French page must reference the English one.
- Codes are valid: a language code, optionally followed by a country code. A country code on its own is not valid.
- An x-default value identifies the fallback page for users who match no listed version.
- Hreflang URLs are the canonical, indexable addresses, not redirected or blocked ones.
How to localise content beyond the words
Localisation means adapting the whole page to the expectations of the market. Review each of the following:
- Titles and meta descriptions, rewritten around the local keyword rather than translated.
- Currency, units, date formats and phone numbers.
- Payment and delivery options that local buyers expect.
- Legal content: terms, returns, privacy and consent requirements differ by jurisdiction.
- Examples, case studies and testimonials relevant to that country.
- Images and their alt text, including any text embedded in graphics.
- Tone. Formal and informal address carries real weight in languages such as German and French.
- Forms and customer support. If a visitor enquires in their language, someone must be able to reply in it.
Machine translation can be a reasonable starting point for large volumes of content, provided a native speaker edits the result. Publishing unreviewed machine output on your key commercial pages risks both rankings and credibility.
Which technical mistakes harm international rankings?
The most damaging mistake is forcing visitors to a version based on their IP address or browser language. Search engine crawlers mostly visit from a small number of locations, so automatic redirects can stop them from ever seeing your other versions. Suggest the appropriate version with a banner instead, and let the user choose.
Other points to check: every language version should be linked from a visible language switcher, included in the XML sitemap and free of mixed-language content such as untranslated menus or footers. Hosting location matters far less than it once did, provided pages load quickly in the target country, which a content delivery network handles well.
Finally, authority is partly local. Links and mentions from websites in the target country, listings in relevant local directories and, where you have premises, a local business profile all help a new market version establish itself.
Frequently asked
Do we need a separate domain for each country?
No. Subdirectories on a single domain work well for most organisations and are simpler to manage. Separate country domains make sense when you have a real local presence, the resources to maintain each site, or a market where local domains are strongly preferred.
Is machine translation bad for SEO?
Not in itself. What matters is whether the resulting page is accurate, natural and useful. Machine translation reviewed and corrected by a native speaker can perform well. Unedited output tends to read poorly and miss the terms local users search for.
Will translated pages count as duplicate content?
Pages in different languages are not treated as duplicates. Pages in the same language aimed at different countries can overlap heavily, and correct hreflang annotations tell search engines which version belongs to which audience.
Should we launch every language at once?
Usually not. Start with the market where you have the clearest demand and the ability to serve customers properly, learn from it, then extend. A complete, well-localised version in one language outperforms thin versions in five.
If you are planning to enter new markets and want your visibility built on solid foundations, see our digital marketing service.
