Two languages. A complete route to an enquiry.
Selling in Italian and German in Bolzano means supporting the whole journey: clear services, equivalent terms, forms and error messages in the chosen language. A flag does not make an international department. We first define the audience, offer and action a visitor should be able to complete.
The content map records each page, search intent, language, source of facts and approver. Search terms differ: «Webdesign» and «realizzazione siti web» are not a word-for-word match. Images containing text, PDFs and shared link previews also need planning.
Google needs to recognise the right page, too.
One customer searches for “Webdesign Bozen”, another for “realizzazione siti web”. Word-for-word translation does not automatically match both needs. We plan separate pages and URLs, equivalent language links and consistent search signals. Switching language keeps customers on the topic they were reading.
Checks include delivered HTML and rendered content, crawlable links, the sitemap and Search Console. An accessible website is not automatically indexed; an indexed page does not automatically rank for «websites Bolzano». Visibility needs measurement after launch.
It is online. Who keeps both versions current?
Change the Italian price and forget the German version: a creative way to start your next dispute. Each language needs an owner and a review process. Updates, integrations and manageable maintenance determine whether a static site, CMS or WordPress makes sense.
For companies in Trento or Veneto serving German-speaking customers, a bilingual structure can make sense without an office in South Tyrol. Briefs and reviews happen online. Development, translation, language review, migration and recurring services have separate scopes.
The practical choice
| Situation | Worth considering |
|---|---|
| Local Italian and German customers | Complete IT/DE pages with equivalent offers and contact journeys. |
| International customers too | English with a defined role and complete content. |
| Frequent content changes | An owner and approval workflow for each language. |
| Replacing an existing website | Inventory current URLs, retain useful content and plan redirects. |
Where are you starting?
Recognise your situation? Start here. Scope and investment still need a review of your workflows, data and existing tools.
First step
Start with a page inventory and available search data before changing URLs or structure.
Before the quote
Tell us what needs to work
- Website objective and the enquiry it should produce.
- Required pages and languages, with a content approver for each.
- Domain, access and current website addresses.
- Actual functions: contact, catalogue, booking or sales.
- Who maintains the content after handover.
The quote separates initial development, content, external services and recurring costs. Access, source code, handover and support have a written scope.
Tell us what needs to work The development serviceUseful questions
Is automatic translation enough?
It can help produce a draft. The offer, terminology, conditions and operational messages need review. Content ownership and native-language review are agreed within the project.
Do I need a page for every city?
Only where it provides distinct content and a distinct service. Repeating the same page with a different city name does not help customers decide.
Do you guarantee a Google position?
No. We plan content and technical requirements, verify the release and measure progress. Google determines indexing and result order.