A website in Trieste: three languages, but only the ones that exist

A business site in Trieste has to declare which languages it exists in, and do it with real addresses. Two machine-translated versions nobody checked are worse than one version written properly.

Trieste has 198,417 residents on the 2023 figure, in the Provincia di Trieste, Friuli-Venezia Giulia: read from Wikidata Q546 on 1 November 2026. It is a small province in a border region: the audience that can read the page does not stop at the municipal boundary.

The pages, and which language they need

The table does not say "translate everything": it says what is worth translating and what is not. A badly translated services page costs you the trust of the reader, while a privacy notice in Italian only is normal and nobody complains. The practical rule: translate what a customer needs in order to buy, not what fills the menu.

hreflang: only between versions that exist

hreflang tells Google that two addresses are the same page in different languages. It only works when both pages really exist and link to each other: a tag pointing at a missing translation is a mistake you pay for in indexing. If the English version is machine output nobody read, better not to publish it. The indexing basics are in get the site indexed by Google.

• One address per language, with the language in the path: no cookies that swap the page behind your back.
• Reciprocal hreflang between the pairs, plus x-default on the main version.
• No automatic IP redirect: whoever wants to read in Italian must be able to.
• A language switch in the header, with each language written out in full.
• One phone number, with the languages spoken stated beside it.

One form, three languages

The contact form does not multiply per language: only the field labels change. Name, email or phone, message, and a box for the preferred language are enough. If replies arrive in three languages, whoever answers must know before opening the message, not after. The contact page is also where multilingual sites break most often, because nobody re-reads the translated labels.

curl -s "https://ui.eneawork.it/api/blocks/category/contact?limit=200" | jq '.category.count, (.blocks | length)'

Blocks from the catalogue

Three records worth opening now. Contact 1 from Efferd UI is the single-column form, the one that holds long labels without breaking. Contact Sections 01 from Creative Tim is the two-column variant, with room for a map beside the fields. The contact category holds the alternatives, useful when the form has to sit next to opening hours.

The limitation to state up front

The catalogue holds React and Tailwind components: no multilingual routing, no translation system, no automatic hreflang check. Block labels are in English and must be rewritten in the language of the page, one by one. On WordPress these blocks do not install as they are: they work as a structural reference. Previews are free, the full code sits in the Pro part.

Cost and timing

The national 2026 ranges: a landing page 400–1,200 euro, a five to ten page showcase site 1,500–4,000 euro, a structured company site 4,000–10,000 euro. Extra languages are billed separately, like content: no city has different prices. Yearly maintenance for a small CMS site sits between 300 and 1,200 euro, the domain between 10 and 20 euro a year. The full picture is in what a website costs.

For the minimum structure read what a company website needs, for the base choice WordPress, Wix or React components, for copy that reads naturally in translation copy-paste or headless.