The standard way to localize a website is to drop in a widget that swaps the text in the browser. It's a two-line install and it looks like localization. Your Spanish page is right there — click the dropdown, the words change. The problem is that the words changing in your browser is not the same thing as a Spanish page existing.
One URL is one page
If every language lives at the same address, then as far as the rest of the internet is concerned you have one page, in one language. There's nothing for a search engine to index, nothing for someone in Madrid to link to, nothing to share, nothing to rank. You've built a translation that only exists for people who already found you in English — which is precisely the audience that didn't need it.
A language you can't be found in isn't a language you support.
The part everyone skips
Real localization means real URLs, one per language, each one indexable on its own. It means hreflang so search engines know the nineteen versions are the same page in different languages rather than nineteen duplicates competing with each other. It means each version declaring itself as the canonical one for its language — get that wrong and you can quietly tell Google that eighteen of your translations shouldn't be indexed at all.
And it means translating the metadata. This is the piece almost everyone forgets, and it's the one that matters most, because the title and description are the entire thing a searcher actually sees. We shipped translated pages with English titles for exactly one build, and the result was pages whose body was perfect Japanese and whose search listing was English. Localized site, untranslated storefront.
What's live
Both revenuearc.com and ArcPlanner now run in nineteen languages — Spanish, French, German, Italian, Brazilian Portuguese, Japanese, Korean, Simplified and Traditional Chinese, Russian, Arabic, Hindi, Turkish, Dutch, Polish, Vietnamese, Thai, and Indonesian, alongside English. Real URLs, real metadata, and Arabic renders genuinely right-to-left rather than as mirrored English.
Where we stopped
We didn't machine-translate everything and declare victory. Our legal pages stay in English on purpose — a translated contract implies a translated contract is enforceable, and ours isn't, so every language shows a notice saying so in that language rather than a translation pretending otherwise. Long-form writing stays English for now too. The system falls back per-string, so anything untranslated renders correct English instead of a broken key.
None of this is clever. It's just the unglamorous version of a thing most companies do the easy way and then wonder why the traffic never showed up. The widget was never the shortcut it looked like — it was just a way to feel localized without being found.
Notes from the build
How we think about media, software, and growth — a short email when we publish something worth your time. No spam, unsubscribe anytime.
Want this pointed at your growth?
No retainer, no risk. We only get paid when we grow your revenue.