I read the language border first

A notebook, a train timetable, and three nearly identical customer questions were enough to make the problem visible. The French answer kept the coastal business local and precise. The Spanish answer widened it into a generic regional service. The English answer quietly made it sound like a tourism operator in a different place. Same business, same public facts, different language path. That small mismatch became the working scene.

I am from the French southwest, where a place name can carry several borders at once. It may sound Basque to one visitor, Catalan to another, Atlantic to a tour planner, or simply “France” to a customer writing in English from outside the country. Before this work, I edited multilingual service pages, compared translated business descriptions, reviewed tourism and commerce listings, checked cross-border category wording, and helped small operators explain what they do to readers outside their native language. Those habits still shape the work. I read slowly. I separate name, country, region, service, audience, and source path before I trust an answer.

Now I keep parallel answer cards for the same business in French, Spanish, and English. I mark the first sentence where the entity changes shape: in composite cases, a hotel near a named Atlantic town becomes a beach area, a French clinic with one translated service page becomes a general medical option, a guide on the French side of the Pyrenees becomes a Spanish mountain tour, or a cross-border shop loses the audience it actually serves. My stance is simple. Translation is not decoration when it changes commercial meaning. A business needs facts online, and it also needs bridge sentences that survive the crossing: plain language that tells an answer engine what the business is, where it is based, who it serves, and how foreign-language customers should understand it.