Translating your pages is only half the job. If search engines can't discover, understand and serve each language version, your international traffic stays flat no matter how good the words are. Here's the checklist we run for every Tonguewise launch.
1. One URL per language
Give every language its own crawlable address — subdirectories like /fr/ or /de/ work best for most teams. Query parameters and cookie-based switching hide content from crawlers and split your ranking signals.
2. Translate the slug, not just the page
A French visitor should see /tarifs, not /pricing-in-french. Translated slugs earn more clicks in local results and signal relevance to the search engine. Tonguewise generates them automatically and keeps the mapping stable across redesigns.
3. Wire up hreflang correctly
Hreflang tells Google which language each page serves so the right version ranks in the right country. It must be reciprocal, self-referencing and kept in sync — three things humans forget and software doesn't. Regenerate annotations on every publish, not once a year.
4. Localize titles and meta descriptions
Direct translations of English keywords rarely match what locals actually search. Research search terms per market, then adapt titles and descriptions — character limits differ by language, and truncation kills click-through.
5. Keep language versions equally fast
Translated pages must meet the same Core Web Vitals as the original. Client-side translation widgets often add seconds of delay; server-rendered language versions keep every market fast and crawlable.
The pattern is simple: automate the technical layer so your team spends its energy on the words and the keyword research that actually move rankings. Set it up once, and every new page you publish arrives SEO-ready in all languages.