01Why writing twice is not the same as translating once
A machine translation of an English page into Romanian reads as translated Romanian, and both readers and search engines notice the difference between that and copy actually written in the language. Doing it properly means every page gets written twice: the English version argues its case in English idiom, and the Romanian version argues the same case in Romanian idiom, which is a different sentence, not the same sentence in different words. That doubles the actual writing work behind every page, every product description and every legal notice on the site, which is exactly the part a 48-hour timeline, built around writing a business website once, was never sized for.
- A translated page reads as translated, both readers and search engines notice
- Each language gets its own idiom, which means writing twice, not translating once
- That doubling applies to every page, product description and legal notice on the site
02What actually gets scoped for a bilingual build
A bilingual timeline is not vague, it is scoped against the same variables as any project: how many pages, how much of the content is genuinely legal or regulatory language rather than marketing copy, and whether the two languages need separate SEO structure or can share one. On Noryse, a launch brand with bilingual editorial copy from day one, the two languages were part of the original brief rather than an add-on requested after the site was already built, which kept the writing and the launch on the same schedule instead of stretching it after the fact. Retrofitting a second language onto an already-live site is usually slower than building both in from the start.
- A bilingual timeline is scoped on page count, legal-language volume and SEO structure needs
- Noryse launched with bilingual copy built into the original brief, not added afterward
- Adding a second language to an already-live site is usually slower than building both from the start
A launch built bilingual from the first brief
Noryse launched with no name, no identity and no store yet, and the bilingual editorial copy was part of that brief from the start rather than a translation pass added after the design was finished. Building both languages into the same schedule, instead of writing English first and translating later, is what kept the launch on one timeline rather than two.
See the build: NoryseQuestions, answered
Can I launch in one language first and add the second later?
Yes, and it is often the faster path: launch the 48-hour version in one language, then scope the second language as its own project once the first is live.
Does PROOF48 ever machine-translate content?
No. Romanian is written in Romanian and English is written in English, each in its own idiom, because translated copy reads as translated and both readers and quality raters notice.
Where PROOF48 fits
A two-language site takes longer because every page gets written twice, not translated once, and that doubling applies to every page, product description and legal notice on the site. PROOF48's 48-hour window covers one language; a second language, like the bilingual copy built into Noryse from the start, gets its own scoped timeline.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.