Which pages should you translate for an English customer journey?

Map the customer’s decision sequence

An accommodation visitor may need location, travel details, facilities and a booking route. A supplier’s customer may need product coverage, delivery areas and a quotation process. These are planning scenarios, not a compulsory page list for every industry. Identify the questions that matter to your own prospective customer.

For an initial release, prepare the chosen service, relevant real project or product information and contact step together. Let the homepage guide visitors through them. Do not present untranslated services as fully supported in English; explain the actual scope so the visitor can make an informed decision.

Localise functions as well as paragraphs

Navigation, form labels, validation messages, buttons and WhatsApp drafts belong to the translation scope. Changing a heading while leaving the customer controls in Turkish does not complete the experience. Telephone presentation, dates and coverage information should also be understandable from outside Türkiye.

Describe how English communication will work using options the business actually supports. Online meetings, email or WhatsApp should reflect the real process. Do not invent a guaranteed response time for visitors in another time zone. A realistic communication method is more helpful than an unsupported promise.

Keep the two versions consistent

Updating a Turkish service without updating its English counterpart creates conflicting information. Wording need not be identical, but deliverables, exclusions, contact details and actual project scope should agree. A simple page-pair record helps keep later edits consistent.

Each language needs a clear address and relevant switch link. Where a corresponding page exists, switching should take the visitor to that page rather than repeatedly restarting at the homepage. Check canonical and language signals on the live release. These support understandable content; they do not guarantee international enquiries or first-place rankings.

Test the complete English path

Approach the site as a first-time visitor. Find the service, read its scope, inspect an example and prepare a contact draft. Record untranslated errors, broken links or conflicting claims, then correct them. Apply the same standard to blog translations: retain the useful explanation instead of replacing it with a short summary.

• Homepage, service, real evidence and contact complete.
• Navigation, form messages and draft text in English.
• Language switching leads to the corresponding page.
• Scope and contact information consistent across languages.
• The full journey checked on desktop and phone.