Multilingual Websites and International SEO Basics
On this page
Translating your site is not the same as making it international-ready
A business expanding into a second language or a new country often starts by running its existing pages through a translation tool and publishing the result. That gets you translated text, but it doesn't get you a site that Google understands as serving different audiences correctly — and it doesn't get you content that actually reads naturally to someone in that market. International SEO is a structural and technical problem as much as a translation one.
Decide your URL structure first
Before writing a word of translated content, decide how you'll structure URLs for different languages or regions. There are three common approaches, each with trade-offs:
- Country-code top-level domains (ccTLDs) — separate domains like
yoursite.co.ukoryoursite.de. Gives the strongest signal to both users and Google about the target country, but means managing and building authority for multiple separate domains from scratch. - Subdomains —
uk.yoursite.com,de.yoursite.com. Easier to set up than separate domains, and can be geotargeted separately in Search Console, but generally builds authority somewhat independently of your main domain. - Subdirectories —
yoursite.com/uk/,yoursite.com/de/. The most common choice for small and mid-size businesses. Everything sits under one domain, so authority is shared across the whole site, and it's the simplest to maintain technically.
For most small businesses expanding to a second language rather than running a large multi-country operation, subdirectories are the practical choice — less infrastructure to maintain and no need to build separate domain authority from zero.
hreflang: telling Google which version goes where
hreflang is an HTML attribute that tells search engines which language and, optionally, which region a given page is intended for, and which other pages on your site are equivalent versions in other languages. Without it, Google has to guess which version of a page to show a searcher, and it's common for the wrong language version to outrank the right one in a given country's results, or for both versions to compete against each other.
A basic hreflang setup looks like this in the <head> of each page:
<link rel="alternate" hreflang="en-us" href="https://yoursite.com/us/" />
<link rel="alternate" hreflang="en-gb" href="https://yoursite.com/uk/" />
<link rel="alternate" hreflang="es" href="https://yoursite.com/es/" />
<link rel="alternate" hreflang="x-default" href="https://yoursite.com/" />
A few rules that trip people up:
- hreflang tags must be reciprocal. If your English page links to your Spanish page via hreflang, the Spanish page must link back to the English page the same way. A one-directional tag is often ignored.
- Use the correct language and region codes. Language codes are two-letter ISO codes (
en,es,fr); region codes are added after a hyphen when you need to target a specific country within a language (en-usvsen-gb). x-defaultspecifies the fallback page for visitors whose language/region doesn't match any of your specific versions.- Tags can go in the page
<head>, in the HTTP header (for non-HTML files), or in an XML sitemap — pick one method and be consistent rather than mixing approaches inconsistently across the site.
Translate content, don't just machine-translate it
Direct machine translation of an English page into another language usually produces text that's technically understandable but doesn't read naturally, and often misses how people in that market actually search. A German searcher and an English searcher looking for the same service frequently use different phrasing, different levels of formality, and sometimes different terminology entirely for the same concept.
Treat each language version as needing its own light keyword research, not a direct translation of your English target keywords. A phrase that works well in English might have an awkward or rarely-searched direct translation, while a slightly different phrasing is what people in that market actually type into Google.
This matters more for anything customer-facing than for boilerplate — your service descriptions, headlines, and calls to action deserve a native or fluent speaker's review even if the bulk of the translation is done with a tool as a starting point.
Don't forget the non-content basics
- Currency, date formats, and units should match the local convention, not just the language.
- Local contact information — a UK phone number and address if you're targeting UK customers, not just a translated version of your US contact page.
- Local trust signals — testimonials, certifications, or partnerships that are relevant to that market rather than only ones from your home market.
- Google Business Profile — if you have a physical or service presence in the new country, a properly set up profile there matters as much as the website itself. Our why Google Business Profile matters post covers the fundamentals, which apply per-country, not just to your primary market.
- Server location and hosting — page speed still matters internationally; a site hosted only in the US will generally load slower for visitors in the UK or Southeast Asia unless you're using a CDN to serve content from a location closer to them.
Set up Search Console properly for each market
If you're using subdirectories, you can set international targeting per section in Search Console's legacy International Targeting settings (where still available) or rely on hreflang plus locally relevant content signals. Submit a separate sitemap per language/region section so you can monitor indexing and performance for each market independently rather than lumping everything into one aggregate view where problems in one language can hide behind good performance in another.
Start small and expand deliberately
You don't need every page translated on day one. Start with your highest-value pages — homepage, core service pages, contact — properly translated and tagged, confirm they're indexing and performing correctly in Search Console, then expand to blog content and secondary pages once the structure is proven. Multilingual SEO done properly compounds over time, but done sloppily with machine-translated text and missing hreflang tags, it can actually create duplicate content confusion that hurts your existing single-language rankings rather than adding a new market on top of them.
Related service: Digital Marketing (SEO, Ads, Branding, Social Media)
Planning a new website?
Let's talk about how a fast, SEO-ready Next.js site can help your business grow.
Start Your Project