Bilingual copy is not translation

"Your Spanish reads like Google Translate" is the most common sentence new clients say about their old site — even when a human translator produced it. The translator was not lazy. The problem is structural: somebody wrote English with a reader in mind, then someone else converted those words into Spanish, and conversion preserves the parts that should have died. The joke lands differently. The metaphor is foreign. The sentence rhythm still belongs to the first language. Readers may not name any of this; they just feel that the page was not written for them.

Drafting and translating are different jobs. Translation optimizes for fidelity to a source. Drafting optimizes for a reader. On a website, the reader always wins, because nobody sees your source text — they only see whether the Spanish feels like their language or like a costume. Dual drafting means one brief, two writers (or one bilingual writer with two clearly separated passes), and both versions written toward the same goal: make this offer obvious to this audience. When the English has a punchy five-word headline, the Spanish is allowed to need eight words, a different metaphor, or a completely different example. That is not drift. That is the job.

Spanish runs longer — plan for the geometry. Spanish typically needs 15 to 25 percent more characters than English for the same meaning. Buttons wrap, headlines break badly, and the beautiful hero layout collapses on a phone — in Spanish only, which is how bilingual sites embarrass themselves in front of exactly the market they built them for. The fix is upstream: design the layout with the longer language in the room, write headlines that survive expansion, and test every page in Spanish on a 360-pixel screen before launch, not after someone complains.

The tells of machine-shaped Spanish. You can hear when text was converted. Calques like "potencia tu negocio" (the translation of "power your business" nobody says out loud), stacked marketing abstractions ("soluciones integrales innovadoras"), formal register dropped into casual products, dates and number formats transplanted from the wrong country, and pronoun policy that changes sentence to sentence. Latin American Spanish is not one voice either: a Miami landing in tuteo and a Bogotá proposal in usted are both valid choices — the sin is choosing by accident. Pick a register, write it down, and keep it.

How we run the two-language pass. Both versions start from the same brief with the same promise and the same proof. Each is drafted for its reader, then checked against the other for completeness, not for sentence symmetry: same offer, same numbers, same call to action, same compliance lines — different music. A final QA pass compares the pair side by side for missing elements, placeholder leakage and format errors (we keep a checklist for exactly this, and it has caught more real bugs than any test suite). Machine tools are welcome as a first skim, never as the draft, and never as the last word.

What this means if you are buying copy. Ask any writer or agency one question: "who drafts each language?" If the answer is a pipeline where one language is primary and everything else flows from it, you are buying translation with extra steps. If the answer is that both languages get planned, drafted and reviewed as originals — even if one human does both passes — you are buying bilingual copy. In Miami and Bogotá, your readers can tell the difference in about four seconds. That is exactly how long you have.