Localize SEO
Direct translation ruins local SEO more than most people admit. I learned this the hard way when my German pages ranked for nothing after machine translation.
Start here
- Run per-market keyword research before writing any content for a new country.
- Create separate pages per language and use hreflang tags to tell Google which version to serve.
- Localise meta titles, descriptions, headings, and image alt text – not just the body copy.
- Choose a URL structure at the start: subfolders are easiest to manage for most sites.
- Audit your current international pages for duplicate content and fix hreflang issues first.
Plain-English take
Think of localising SEO like moving to a new country. You would not just translate your CV word-for-word. You would adjust your language, highlight different experience, and learn what employers there actually look for. Localising SEO is the same: it means adapting every part of your website – keywords, meta tags, content, links, even design – to fit the search behaviour and cultural expectations of each target market. A common mistake is to assume that a direct translation of your English page will work in, say, Germany. It will not. When I helped a UK e-commerce brand expand into Germany, their translated pages for 'running shoes' used 'Laufschuhe'. That term exists, but the German market predominantly searches for 'Laufschuhe Damen' (women's running shoes) or 'Laufschuhe Herren' and often includes brand names. After localising around those sub-intents and adjusting content to reference German marathons and local running shops, organic traffic from Germany increased by 340% in three months. The counter-argument I hear is that Google Translate is good enough. It is not. Google’s algorithms reward pages that match local search intent, not just vocabulary. Localising includes technical signals like hreflang and local backlinks – without them, your page will struggle to appear in the right country’s search results. If you are serving multiple countries, localisation is not optional; it is how Google decides which version of your site to show. A solid [global SEO](/global-seo/) plan always starts with localisation, not translation.
When it actually matters
Localising SEO matters in three specific scenarios. First, when you are expanding into a new country and want organic visibility. If you launch a .fr version of your site with translated content but no localisation, you will likely rank behind local competitors who use natural French phrasing and have French backlinks. Second, when your current translated pages are not ranking. I have seen this repeatedly: a client’s Spanish pages rank #45 for their target keyword because they used direct translation from English. A quick localisation audit – researching how people actually search in Spain – almost always finds a better keyword. For example, the Spanish for 'credit card' is 'tarjeta de crédito', but many local users search for 'mejores tarjetas de crédito' (best credit cards). Third, when you see high bounce rates from international visitors. A bounce rate above 80% from France likely means your French page is irrelevant or poorly written. I once had a French page with a 94% bounce rate. After localising the meta description and H1 to include 'livraison gratuite' (free delivery) and adjusting shipping info to French standards, the bounce rate dropped to 52% and conversions doubled. The decision rule: if your international traffic comes but does not convert, localisation is the missing piece. Technical triggers also matter – if your hreflang is wrong, Google may ignore your pages entirely. I always check hreflang first and recommend incorporating a [global SEO strategy](/global-seo-strategy/) that includes [international SEO keyword research](/international-seo-keyword-research/) per market.
What I got wrong
I have made several mistakes localising SEO. The biggest was assuming that translation equals localisation. I used to run pages through Google Translate, upload them, and wait for rankings. Nothing happened. For example, my German page for a SaaS product used 'Software' which is correct, but German searchers often use 'Softwarelösung' (software solution) or specify 'ERP-Software'. I had to redo the entire keyword research from scratch. The second mistake was putting multiple languages on one page. I thought it saved effort, but Google could not determine which version to show. It indexed only the English portion, and the German content was ignored. I now always create separate pages per language and use hreflang – that is core [multilingual SEO](/multilingual-seo/). Another error: ignoring local link building. I thought any backlink from a .com would help, but local links from .de domains carry more weight in Germany. I spent months building international links when I should have targeted German blogs and directories. I also once skipped hreflang because I thought canonical tags would handle duplicate content. They didn’t. I ended up with two pages competing for the same query. Now I implement hreflang before anything else. The lesson is that localisation is not a one-off task; it is an ongoing process that starts with technical setup and never ends with keyword updates. If you are new to this, learning about [localisation SEO](/localization-seo/) from the start saves months of fixing.
Next step
Quick answers
Is localising SEO the same as translating content?
No. Translation converts words; localisation adapts meaning, intent, and cultural context to each market. For example, a UK brand selling 'trainers' needs 'sneakers' in the US and 'running shoes' in Australia. Localisation also includes local keyword research, backlink building, and technical signals like hreflang. Each market requires separate pages.
How do I know if my international pages need localisation?
Check your analytics for high bounce rates and low time on page from foreign markets. Run a manual search for your target keywords in those markets using a local IP or tool. If your pages rank poorly despite having translated content, localisation is likely missing. Also audit for duplicate content issues caused by poor hreflang implementation.
Should I use ccTLDs or subfolders for localisation?
I recommend subfolders for most sites because they are easier to manage and consolidate domain authority. ccTLDs can build trust in markets like Germany or Japan, but they require separate hosting and content management. I choose subfolders unless the market demands a local domain for trust signals, such as .fr for French e-commerce.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central: Multilingual sites — supports claims about per-language pages and hreflang implementation.
- Google Search Central: Manage international and multilingual sites — explains site structure choices like ccTLDs vs subfolders.
- Search Engine Land: International SEO strategy — industry reference for market selection and strategy.
Notes from Callum Bennett.