The client runs an advertising campaign for several markets at once. They need one landing page, but in different languages — with correct URLs, translations, and forms for each audience. This can be done on Tilda, but there are nuances.
URL Structure
For a multilingual landing page, it's best to use folders: - mysite.com/ru/ — Russian version - mysite.com/en/ — English version - mysite.com/de/ — German version
This allows you to direct ad traffic to a specific language version using UTM tags and the campaign's target URL. Analytics in GA4 are immediately separated by language via the URL path.
If you use separate domains for different markets — that's also a viable option, but managing multiple domains is more expensive. For a landing page, this is usually overkill.
Translation: What to Translate and What to Leave Untouched
A landing page has elements that need to be translated: - Heading and subheading (H1, H2) - Product or service description - List of benefits - Buttons and CTAs - Form: field labels, placeholder texts, submit button text, message after submission
What to adapt, not just translate: - H1 heading — should contain a search query in the target audience's language, not a literal translation of the Russian keyword - Examples and cases — it's better to use references familiar to the audience (for Germans — German companies, not Russian ones) - Prices — in local currency, not just in rubles
SEO for Each Language Version
Each language version of the landing page is a separate page in the Google index. Each requires: - A unique title and meta description in the version's language - hreflang attributes that link the versions together - Open Graph tags for social networks
Without hreflang, Google might show the wrong version in search: a user from Germany found the landing page but landed on the Russian version.
Form on the landing page
This is the most important part. The form is the final point of the landing page. If it's not translated or doesn't work correctly, all efforts to translate the rest of the content are meaningless.
On Tilda, forms are fully translated via proxy: labels, placeholder texts, submit button, successful submission message. Dynamic validation messages too. It's important to check this separately before launch — fill out and submit a test application from each language version.
How to Launch Quickly
This is important for advertising campaigns with tight deadlines. A multilingual landing page via proxy is launched without changes in Tilda — connection via DNS, language selection, translation settings. The basic version can be set up in a day, and translations can be refined after the campaign starts — this is convenient when the deadline was yesterday.
Pre-launch Checklist
- Each language version opens with the correct URL
- Title and meta description translated for each version
- hreflang attributes configured
- Form submits from each language version
- Post-submission message translated
- Buttons and CTAs translated and adapted (not literally)
- Language switcher works and leads to the correct version
- Analytics configured — traffic by language is separated in GA4
Frequently Asked Questions
Do I need to create a separate Tilda project for each language?
No. Proxy translation creates language versions without duplicating the project. You work in one Tilda project, and language versions are automatically generated at the proxy level.
How to set up Google Ads for a specific language version?
Use a URL with a folder as the landing page: mysite.com/de/ for a German audience. Google Ads supports targeting by URL and browser language.
What to do if hreflang is configured incorrectly?
Google Search Console will show hreflang errors in the "International Targeting" section. Proxy solutions generate hreflang automatically — check that they are added to all pages of all versions.
How long does it take to launch a multilingual landing page?
With proxy translation — one day for connection, another day for checking and refining translations. The technical part is fast, most of the time is spent on editing translations for the target audience.