01
Discover
Kickoff call, written brief, fixed quote.
Service · 05
Multilingual Content at Scale
Publish in 5 languages. Read like a local.
The problem
You launched in one language. Half your market doesn't speak it.
- 01
Machine translation reads as translation. Buyers can tell within a paragraph; the bounce-rate spike is real and measurable.
- 02
A native-speaker review pass per article costs more than the article itself, kills your unit economics, and bottlenecks on the reviewers' calendars.
- 03
Per-locale SEO is its own discipline, hreflang, canonical, locale-aware sitemaps. Get one wrong and Google deduplicates your translations.
What you get
Deliverables
- 01
Source-language editorial workflow
- 02
Translation pipeline with humanization pass
- 03
Per-locale SEO (hreflang, canonical, search-console submission)
How we work
The process, start to ship.
02
Build
Weekly demos. Source on your GitHub.
03
Ship
Deploy, document, train.
The tech
Built on what works.
- Claude
- Ollama
- Python
- Astro Content Collections
- PostgreSQL
- Cloudflare
- Search Console API
Related work
See it in production
Frequently asked
Questions
How many languages?
Currently shipping in EN, RO, FR, AR. DE on request after a paid native proofread.
How long does setup take?
3–6 weeks to migrate a single-language site to multilingual + set up the translation pipeline.
What do I need to prepare?
Existing content (or a content plan), target locales, and any glossary or style guide you already have.
Ready to brief a multilingual content at scale project?
30-minute discovery call. No pitch deck. We talk about what you're shipping, what's in the way, and whether I can help. If yes, you get a fixed quote within a week.