Start with evidence of demand
Look at enquiries, customer conversations and search queries, then ask which language a buyer uses to describe the service and discuss a quote. A Spanish-only site can be sufficient for a local Spanish-speaking audience. English plus Spanish may help a business serving residents from several countries. A Swedish page is useful when the company can actually answer Swedish enquiries.
Example: A Torrevieja property-maintenance team handles English-speaking owners and Spanish-speaking local partners. Separate English and Spanish service pages can explain different contact expectations. Translating the hero alone leaves the quote form, confirmation message and follow-up in the wrong language.
Translate the complete customer path
Prioritise the services people buy, coverage, proof, FAQs, contact details, forms and confirmation text. Have a fluent person review trade terminology and promises. Use language-specific URLs and clear navigation; connect equivalent pages correctly. Do not translate a claim about qualifications, service areas or response times if it is not true for that audience.
Each language creates maintenance work. Prices, opening hours and coverage can drift if one version is updated and another is forgotten. Start with one complete buying path, test it, then add the next language when your team can keep it current. Do not assume machine translation alone gives reliable technical or legal wording.
See the website's page and support scope and how content and approvals are handled. For a language plan based on your customers, book a short discussion.