Kapta · 15/09/2026
The decision depends on the people you want to serve and your ability to keep both languages current. If you receive enquiries from residents and international visitors, map each audience's journey before translating the website.
Should every page be translated?
Start with pages needed to understand the offer and complete the main action: services, conditions, contact and booking or enquiry. An English sales page ending in an incomprehensible form leaves the journey incomplete.
Is an automatic translation button enough?
Automatic translation can help draft content, but service names, conditions and instructions need review. Check the entire experience, including emails and error messages. Define who updates both versions when a price or policy changes.
How should language addresses be organised?
Google recommends separate URLs for language versions and annotations identifying their relationship. Visitors should be able to open their preferred version directly. Google multilingual website guidance.
Which wording should the English version use?
Write for the customer's question rather than translating local expressions word for word. Explain location, access and services clearly. Someone planning an Algarve visit may need different context from a person already familiar with Albufeira.
How should I prepare the Kapta project?
Provide customer languages, existing content and an approver for each version. Choose a test journey in each language and verify that visitors can reach contact or booking with the same essential information.
