Website Translation and SEO: How to Translate a Website Without Losing Search Visibility
Website translation can expand organic search visibility into new languages and markets, but only if the linguistic and technical SEO work are coordinated. Keywords should be researched in the target language, localized pages need crawlable URLs, internal links must point to the right language version, and hreflang, canonicals and indexing signals must be implemented correctly. This guide explains a practical workflow for translating a website while protecting existing SEO signals.
Audit the source website before translating anything
The existing website already has a structure: URLs, internal links, page topics, rankings, backlinks, metadata and conversion paths. Record that structure before creating another language version.
Indexable URLs
Identify the pages that are currently indexable and worth localizing.
Search performance
Record important source-language queries, landing pages and organic traffic patterns.
Internal links
Map the important links between commercial, category and informational pages.
Technical signals
Review canonicals, sitemap inclusion, robots directives and existing language annotations.
Decide which pages should actually be localized
A multilingual rollout does not have to reproduce every low-value page immediately. The first phase can focus on the pages with the strongest commercial or search opportunity in the target market.
Priority pages often include core services, product categories, high-value landing pages, conversion pages and guides that support the same topic cluster.
Research keywords in the target language and market
The source-language keyword is not automatically the correct target-language keyword. Search volume, terminology and user intent can differ substantially between markets.
Primary query
Identify the main phrase that best matches the localized page’s purpose.
Supporting queries
Build related terminology around the actual topic rather than repeating one phrase unnaturally.
Search intent
Confirm whether users are looking for information, comparison, a service, a product or another result type.
Use separate URLs for separate language versions
Google recommends using different URLs for different language versions instead of relying only on cookies or browser-language settings to swap the content of one URL.
Separate URLs give users and search engines stable destinations for each language version and make internal linking, hreflang and performance tracking easier to manage.
Translate and localize titles, headings and metadata
The translated body copy should not be the only localized element. SEO titles, H1s, headings and meta descriptions should align with the target-language keyword and page intent.
Metadata should be written naturally for the target market rather than copied word for word from the source-language page.
Connect equivalent language pages with hreflang
Hreflang helps Google understand that different URLs are localized versions of the same content and which language or regional version may be appropriate for a user.
Self-reference
Each page in a hreflang set should list itself as well as the relevant alternate versions.
Reciprocal links
Language versions should point back to each other so the relationship can be processed correctly.
Correct codes
Use valid language codes and, where needed, valid language-region combinations such as en-GB.
x-default
Consider x-default for a fallback or language-selector page when no specific language or region matches.
Keep canonical signals consistent with the localized URL
Canonical tags are used primarily to indicate a preferred URL among duplicate or very similar pages. Fully translated pages are distinct language versions and should not automatically point their canonical to the source-language page.
Google recommends a self-referential canonical on canonical pages and, when hreflang is used, a canonical in the same language where possible.
Rebuild internal linking in the target language
Localized pages should link to other relevant pages in the same language wherever a corresponding version exists. Sending users back into the source-language site unnecessarily weakens the localized journey.
The internal-link structure should preserve important relationships between service pages, category pages, guides and conversion pages.
Do not force automatic language redirects
Google advises against automatically redirecting users from one language version to another based only on an assumed language preference. Automatic redirects can prevent users and search engines from accessing all versions of the site.
A visible language switcher gives users control while allowing each language URL to remain directly accessible.
Keep pages accessible
Each language URL should be reachable directly.
Use a language switcher
Let users select the version they want instead of forcing a redirect.
Link equivalent pages
When possible, the switcher should lead to the corresponding page rather than always returning to the homepage.
Check indexing before and after launch
- Localized URL returns HTTP 200.
- Page is not accidentally marked noindex.
- Robots.txt does not prevent required crawling.
- Canonical points to the intended localized URL.
- Hreflang annotations are reciprocal and use valid codes.
- Localized URL is included in the appropriate sitemap.
- Main content is genuinely translated rather than only the template.
- Internal links point to the intended localized URLs.
- Old URLs redirect correctly if URLs were changed.
- Search Console can discover and inspect the localized pages.
Preserve SEO signals when existing URLs must change
If an existing page is being moved to a new URL as part of the multilingual rebuild, map the old URL to its most relevant new destination and implement a direct redirect.
Update internal links so they point directly to the final URL instead of relying on redirects throughout the site.
Website translation and SEO launch checklist
- Priority source pages have been mapped to target-language pages.
- Target-language keyword research is complete.
- Search intent matches the localized page purpose.
- SEO titles, H1s and metadata have been localized.
- Each language version has its own stable URL.
- Canonical URLs are correct and consistent.
- Hreflang sets are reciprocal and complete for the intended versions.
- Internal links point to the correct language pages.
- Navigation, breadcrumbs and CTA links have been localized.
- Language switcher links work correctly.
- Important localized URLs are included in the sitemap.
- No priority page is accidentally blocked or marked noindex.
- Redirects are in place for any retired URLs.
- The localized site has been reviewed on desktop and mobile.
- Search performance will be monitored after launch.
Measure the localized site as a new search market
The target-language version should not be judged only by whether its text matches the source. Measure whether it is being discovered, clicked and used by the intended audience.
Impressions
Track whether localized pages are appearing for relevant target-language queries.
Clicks
Monitor organic visits to the localized landing pages.
Queries
Review whether the actual search terms match the intended topic and market.
Conversions
Track enquiries, purchases or other business outcomes separately for the localized experience.
Website translation SEO mistakes to avoid
Literal keyword translation
Search demand and terminology can differ dramatically between markets.
Wrong canonical
Pointing every localized page back to the source language can undermine the intended localized URL structure.
Broken hreflang
Missing reciprocal links or invalid language-region codes can prevent the annotations from working as intended.
Source-language internal links
A localized page should not unnecessarily send users back into another language version.
Website, SEO and localization services
Continue reading
Technical guidance should follow current search-engine documentation
Search-engine documentation changes over time. The technical recommendations in this guide should be rechecked during major multilingual migrations.
Website Translation and SEO — Frequently Asked Questions
Can translating a website hurt SEO?
It can if the migration or localization is implemented poorly. Common risks include changing URLs without redirects, losing internal links, using the wrong canonicals, failing to connect language versions with hreflang, translating keywords literally and accidentally blocking localized pages from indexing.
Should SEO keywords be translated directly?
Usually not. Keyword research should be performed in the target language and market because search behaviour, terminology and intent can differ significantly between languages.
Should every language version have a separate URL?
Google recommends using different URLs for different language versions rather than changing the language only through cookies or browser settings. Separate URLs make crawling, indexing and hreflang implementation easier to manage.
What is hreflang used for?
Hreflang tells Google that different URLs are localized versions of the same content. Each relevant language version should reference itself and the corresponding alternate versions, and reciprocal links are important.
Should translated pages canonicalize to the original language page?
Not by default. Fully translated pages are distinct language versions. Their canonical setup should preserve the correct indexable localized URL, while hreflang connects equivalent language or regional versions. Canonicalization is mainly used for duplicate or very similar URLs.
Can SEO rankings be guaranteed after website translation?
No. A careful localization process can preserve important SEO signals and improve relevance for the target market, but rankings also depend on competition, technical SEO, links, authority, content quality, algorithm changes and other factors.
Planning a multilingual website launch?
Send the website URL, target language, target market and priority pages. We can review the translation scope, keyword requirements, localization needs and page mapping before preparing a quote.