Your multilingual website: built by someone who actually speaks the languages.

The languages your customers speak, not as many as possible. A restaurant with many Italian guests needs its menu online in Italian too, a supplier with customers in France is better off with French. If your customers are purely German-speaking, you may not need a second language at all. I tell you that too, in the free first consultation.

That depends on how many languages and pages need translating. Multilingual sites are part of the Business package, which starts at 900 €. After the first consultation you get a written quote, and that price stands. For context: professional translators charge around 0.12 to 0.30 € per word according to itportal24.de (as of September 2026). I translate German, Italian and English myself, with no outside agency, and that is included in the quoted price.

As a rough draft, yes. I use those tools too. But you should not publish the result unchecked: Google's spam policies list automated translation as one of the techniques used to mass-produce pages without added value. In 2025 Google clarified that what counts is the value for the reader, no matter which tool did the translating. So have someone who really speaks the language proofread it. For Italian and English, I take care of that.

No. A subfolder on your existing domain is enough, like my /it/. It inherits the strength of your main domain, and you do not pay for a second domain or a second hosting plan. Separate country domains like .it or .fr only make sense once you want to appear in that country as a provider in its own right.

hreflang is a note in the code that tells Google which language versions of a page belong together. Each version points to itself and to all the others, plus a default version for everyone else. That way an Italian-speaking visitor lands directly on your Italian page. Without hreflang the website still works, but Google has to guess. I set the tags on every multilingual project.

Depends on the provider, and that is exactly the problem. Check three things first: Does each language get its own URL? Is hreflang set correctly? And will you be updating content once afterwards, or twice? Often the second language in a builder is a complete copy of the site that you have to keep up to date by hand. Send me the link to your site and I will take a look and tell you what works there and what does not.

Not automatically. An Italian language version starts by reaching people in Germany who search in Italian. For your site to be found in Italy itself, it would have to compete there against Italian providers, and that is a separate project with its own visibility work. I never promise rankings, here or there. One thing is certain: whoever finds your site can actually read it.

Italian and English, yes, I do those myself: I speak both fluently. I speak Arabic in conversation, but I only translate website copy into Italian and English. For any other language I need the finished text from you or your translator. I then build the technical part for every language: its own URL, the language switcher and hreflang.

Yes, and that is often the most sensible way. The German site goes online first, and the second language is added as soon as you need it. I set up the technology from the start so a new language version slots in without rebuilding the existing site. My own website went the same way: German first, /it/ and /en/ came later.

You make small changes like opening hours or prices yourself, in every language version. I show you how at the handover, it takes a few minutes. For new copy you send me the German version, and I handle the translation into Italian or English and build it in, on request or as part of maintenance. I deliberately do not build in automatic translation that quietly publishes mistakes.