Multilingual landing pages: the growth playbook for international acquisition (2026)
Organic search is language-specific. A user in Lyon searching for your product in French will not find your English landing page — even if you rank number one in English. This guide covers URL structure, hreflang, what to translate first, and how to scale to 10+ languages without a dedicated content team.
Why landing pages need to be multilingual
Search engines rank content per language. Your English landing page competes only in English-language search results. A French user searching logiciel de traduction or a German user searching Website übersetzen is finding a different set of results entirely — and your site is invisible to both unless you have French and German pages.
The business case is straightforward: CSA Research found that 72% of consumers prefer to read product information in their native language, and 40% will not buy from sites in other languages at all. For SaaS products and e-commerce, that conversion gap is not theoretical — it shows up directly in trial start rates and purchase completion across markets.
Multilingual landing pages are the mechanism that turns international organic traffic from invisible to capturable.
The content problem at scale
The obvious objection: writing landing pages in 10 languages means 10× the content work, or expensive agency translation costs. Most teams start with English only, add Spanish when it becomes obviously necessary, and stop there. The remaining 8 languages stay on the backlog indefinitely.
The cost of not going further is real but invisible: it appears as organic traffic that goes to competitors, not as a line item on a budget. Each language you do not cover is a market where you do not appear in search results regardless of how strong your English SEO is.
The practical solution is a tiered approach: automatic translation handles the structural content that stays consistent across languages, while the small amount of copy that genuinely drives conversions gets human attention. That division gets most of the benefit for a fraction of the cost.
URL structure: subdirectory vs subdomain vs ccTLD
The choice of URL structure affects how search engines consolidate authority across your language versions and how complex the infrastructure becomes.
Subdirectory — /fr/pricing
All language versions live under the same domain. Domain authority accumulates in one place: backlinks to your English pages also benefit your French pages. This is Google's recommended approach for most products, and the easiest to implement — no DNS configuration, no separate property in Google Search Console.
Subdomain — fr.example.com/pricing
Treated by Google as a separate entity from the main domain (with some shared authority). Useful when the marketing site and the app are on different stacks and you need to deploy them independently — e.g., a Next.js marketing site and a separate SaaS dashboard that is also served in French.
ccTLD — example.fr/pricing
Country-code top-level domains send the strongest geo-targeting signal, but split domain authority across separate properties and require registering and maintaining each domain. Practical only for large organisations with strong brand presence in specific markets.
Recommendation for most products: subdirectory (/fr/, /de/, /es/). It consolidates domain authority, is the simplest to set up, and matches Google's own guidance.
hreflang: the signal that tells Google which page to rank
Without hreflang tags, Google sees your French page as duplicate content of your English page and may suppress it. hreflang is the <link> tag in the <head>that declares: “this is the French version of this page, and these are the other language versions.”
A correct implementation on your French pricing page looks like this:
<link rel="alternate" hreflang="en" href="https://example.com/pricing" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/pricing" />
<link rel="alternate" hreflang="de" href="https://example.com/de/pricing" />
<link rel="alternate" hreflang="x-default" href="https://example.com/pricing" />Common mistakes that break hreflang:
- →Missing self-referential tag. Every page must include a hreflang tag pointing to itself. The French page must include
hreflang="fr"pointing at its own URL, not just the other language versions. - →Missing
x-default. Thex-defaultvalue tells Google which page to show when no language match is found. Always include it, pointing at your primary (usually English) version. - →Mismatched canonical. The canonical URL on each language page must match the URL in the hreflang tag for that language — not the English canonical.
Translating key conversion elements
Not all copy on a landing page has equal conversion weight. Prioritising translation effort by impact means the highest-leverage elements get the most attention.
Headline and hero copy
The highest-impact element on the page. Even a 10% lift in comprehension from seeing the headline in a native language affects whether visitors scroll at all. This is where human review pays off most.
CTA button text
“Start free” in English; “Commencer gratuitement” in French. Button text is short, high-visibility, and directly linked to click-through.
Social proof and testimonials
Testimonials from recognisable names in the local market outperform translated testimonials from foreign companies. Where possible, source local proof points; where not, translate carefully.
Feature descriptions and FAQs
Structural content that explains the product. Automatic translation handles this well — the content is factual and consistent, not dependent on local idiom.
Elements to not translate: brand name, product names defined in your glossary, proper nouns (company names, person names in testimonials). Keep these consistent across all language versions.
How to scale to 10+ languages without a content team
The hybrid model: automatic translation for structural content, human review for the copy that most directly drives conversion decisions.
- →Automatic for everything structural. Navigation, footer, feature lists, pricing tables, FAQ answers, form labels — this content is factual, repetitive across languages, and well-served by automatic translation. Add these languages in minutes, not months.
- →Human review for the headline and hero section only. One short copywriting session per language, focused exclusively on the above-the-fold text. This is where native speakers can add the idiom and tone that automatic translation averages out.
- →Start with high-traffic markets first. Check your analytics for where non-English visitors already come from. Those markets will show ROI fastest and justify expanding to additional languages.
This approach gets approximately 80% of the benefit — ranking and converting in each language — with approximately 20% of the effort of full human translation for every page.
Measuring multilingual performance
The metrics that matter are simple; the challenge is segmenting them by language.
Organic traffic by locale
Segment organic sessions by the /fr/, /de/, /es/ URL prefixes in your analytics tool. Watch for growth 4-12 weeks after launching each language as Google indexes and ranks the new pages.
Conversion rate per language
A language with high traffic but low conversion rate is a signal that the hero section needs human attention for that locale. A language converting well validates that automatic translation is sufficient for that market.
Search Console impressions by country
Google Search Console shows impressions and clicks broken down by country. Countries generating impressions without matching traffic suggest a mismatch between the language served and what searchers expect.
Frequently asked questions
- Do I need separate pages per language, or can JavaScript translation work for SEO?
- You need separate, crawlable URLs per language for dependable multilingual SEO. General Lingvit runtime translation does not create language-prefixed indexable URLs at launch, so use your platform's locale routing for that requirement.
- How long before Google indexes multilingual pages?
- New language pages typically appear in Google's index within 2-4 weeks for sites that already have crawl budget and domain authority. Ranking for competitive keywords in a new language takes longer — typically 2-4 months for an established domain, similar to ranking for a new English page. Submitting an updated sitemap that includes the new language URLs speeds up discovery.
- Should I translate my ads too?
- Yes, for paid campaigns targeting non-English markets, matching ad copy language to landing page language is important for Quality Score and conversion rate. A French ad leading to an English landing page creates a jarring experience that hurts both metrics. Translate the ad and the landing page together when launching a market.
Related guides
Launch multilingual landing pages
Add runtime translation to supported landing pages, and use your platform's locale routing and hreflang implementation when search indexing is required.