Google shows the wrong language to the wrong visitors
We set up hreflang (tags that tell search engines which language version to show to whom) and check them in Search Console, including after launch.
We build language versions with clean URLs, correct hreflang and market-aware translation, not word-for-word copies.
Quote and schedule after your brief

We set up hreflang (tags that tell search engines which language version to show to whom) and check them in Search Console, including after launch.
AI produces the first draft, then a native-speaking editor reviews key pages: home, services, pricing, checkout. We agree on your terminology first.
We build the language structure in from the start: /en/, /de/ folders or subdomains, a language switcher, translated menus and forms. A new language later is an addition, not a rebuild.
Forms connect to one CRM with a language tag, so your team sees at once which language to reply in.
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
Brochure site or landing page that needs one extra language
Company site with service pages and a blog, 2–3 languages
Online store with several languages and currencies
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
We review the current site, choose languages and URL scheme, and agree it with you before work starts.
AI drafts, an editor reviews. Developers build the language versions in parallel.
We check hreflang, forms, the switcher and speed, then submit sitemaps to Google.
We agree one measurable goal, for example leads from the new language. We review the numbers together and decide next steps.
For most companies subfolders (site.com/en/) are simpler and share authority with one domain. Subdomains or country domains (.de,.fr) make sense when you need a local presence or separate hosting. We recommend one after the audit.
Both. AI gives a fast, low-cost draft and a human editor reviews it. For critical copy you can order full native-speaker writing as a separate item.
We prepare a quote after reviewing your brief and requirements. A first stage can cover: up to 10 pages; URL structure and hreflang. Scope, payment and schedule are agreed before work starts.
Access to the site, hosting and domain, current copy, a glossary of terms and brand names that stay untranslated, and your target countries. All accounts stay yours.
Yes, with all three, using their native language features or plugins. Some site builders limit hreflang or URL control, and in that case we will tell you honestly if migrating is the better choice.
Payment terms are agreed with the quote before work starts. For a staged project, we describe the result and acceptance criteria for each stage. Support and third-party services are listed separately.
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.