i18n as an Acquisition Channel: How 6 Languages Attracted 60% of Our Traffic
2,206 unique visitors. 41 days. And one realization that changed everything: 60% of our visitors don't speak French.
TAMSIV is a French app, built by a French developer, with marketing done mostly in French. Yet when I opened Google Analytics this week, France wasn't even half the traffic. Germany is our third-largest market. Spain is growing. Brazil is appearing.
All because one evening in February, I decided to translate the app and website into 6 languages before we even had users.
The decision: translate before you launch
Most indie hackers translate after. When they have traffic, when they've validated product-market fit, when they have the budget for a translator. i18n is "polish" — a nice-to-have you do later.
I did the opposite. In February 2026, two weeks before our first alpha release, I implemented next-intl on the website and an auto-translation system on the mobile app. French, English, German, Spanish, Italian, Portuguese. Six languages from day one.
The reasoning was straightforward: if someone lands on the Play Store searching for "voice task manager" in German, and the listing is English-only, they bounce. If the listing is in German, they click. Translation is friction reduction — and friction kills conversions.
The data: 41 days of traffic
Here are the raw numbers from Google Analytics, last week (1,142 unique visitors):
| Country | Flag | % of traffic |
|---|---|---|
| France | 🇫🇷 | ~40% |
| United States | 🇺🇸 | ~18% |
| Germany | 🇩🇪 | ~13% |
| Spain | 🇪🇸 | ~8% |
| Brazil | 🇧🇷 | ~5% |
| Italy | 🇮🇹 | ~4% |
| Others | 🌐 | ~12% |
The standout: Germany at 13%. I've never published a single post in German. Not a tweet, not a LinkedIn article, not a Reddit comment. Zero targeted marketing effort. Yet Germans keep coming — because the Play Store listing is in German, the website is in German, and Google sends them to pages in their language.
Where do these visitors come from?
Two main sources:
1. The localized Play Store. In March, I translated the Play Store listings into all 6 languages — title, short description, full description. Each language has its own optimized keywords. A German searching for "Sprachgesteuerte Aufgaben-App" finds TAMSIV. A Spaniard searching for "gestor de tareas por voz" does too.
2. The multilingual website indexed by Google. Every page on tamsiv.com exists in 6 distinct URLs: /fr/, /en/, /de/, /es/, /it/, /pt/. With correct hreflang tags and translated slugs, Google serves the right version to the right audience. A blog post in German ranks for German queries.
The traffic isn't viral. There was no breakout post. It's organic traffic — slow, steady, the kind that builds when every page on your site speaks your visitor's language.
The iOS surprise: 12 phantom clicks
TAMSIV is Android-only. No iOS version. Yet Google Analytics shows 12 clicks from iOS devices to the download page.
What does that mean? People land on the site from their iPhones, get interested enough to click "Download," and discover it's Android-only. That's 12 potential users lost — and a strong signal that iOS demand exists.
I don't have the resources for an iOS port yet. But those 12 clicks are now tucked away in the back of my mind, and when it's time to decide on the next big move, they'll carry weight.
What this changes going forward
The lesson from these 41 days is brutally simple: i18n isn't polish. It's an acquisition channel.
Every language you add opens a new market. No ad campaign needed, no local influencers, no budget. Just proper translations, clean URLs, and time for Google to index.
For a solo dev with zero marketing budget, this might be the best ROI available. The cost of translation (automated via OpenRouter + manual review) is nearly zero. The return — 60% of traffic — is disproportionate.
If you're building a product and hesitating to translate "because it's too early," reconsider. The data shows visitors are already out there, in other languages, searching for exactly what you've built. The only question is: can they find you?