When planning another language version, use the complete enquiry journey as your measure: visitors need to get from the homepage through the service page to confirmation. An English homepage alone cannot provide that journey if form instructions, errors and the subsequent reply remain available only in German.
You can therefore base the translation scope on the services your team can actually handle in the additional language. That gives you an initial page list which includes the route to an enquiry.
Define the first complete language scope
You do not need to translate every historical article at once. Keeping the intended offers and their flows in a shared list makes it clear which content belongs to the first complete language version.
For each item, include titles, descriptions, image explanations, downloads and interactive states. An external scheduling tool may be part of the journey. Establish whether it supports the language and whether your team can handle the resulting information.
An English service page should not promise the same availability as the German one if the actual scope differs. Explain such differences and connect price and service statements to their responsible source.
Decide language and market separately
English does not automatically mean serving every English-speaking country. Establish the audiences and regions you intend to support and which details change. These might include currency, opening hours, delivery or the responsible contact.
Google distinguishes multilingual from multi-regional websites and recommends separate URLs for language versions. Define the actual language and business scope in the brief before configuring the technical mapping.
Let visitors choose their language and keep them on the equivalent content where possible. Sending someone from a service detail page to another language’s homepage unnecessarily resets their choice.
Connect translations to ongoing editing
A newly published German price statement can make the English version outdated even when nobody has edited that page for months. Having someone report source changes and someone check the translation makes that dependency manageable in everyday editing.
A working list can track the current source, translation and open facts for each item. Compare scope limits, quantities and enquiry status especially carefully. “Date requested” must not become “booking confirmed”.
Avoid independently copied business data where it can be maintained centrally. Translate the explanation, not customer identifiers, product IDs or addresses that must remain unchanged.
Complete the flow in each language
A run from arrival to completion shows whether each translated journey is complete: are the links understandable, does the right download open, and is the language retained after an error and when returning? A deliberately incomplete form submission also reveals messages that remain hidden after a successful submission.
The technical guide to hreflang return links complements this content review. It does not replace a fully translated journey.
The number of languages alone is not enough for a development quotation. Add the affected templates, forms, messages and external services to the page list. That gives a concrete scope to discuss for website and landing-page development.
