07 / Web Localization
We help implement language versions of websites, landing pages and WordPress sites. We combine content preparation with graphic, navigation and responsive layout adaptation.
Your team provides approved translations and market guidelines. We support the technical implementation of website localization and consistency checks across language versions.
Scope of support / Web Localization
Website localization covers visible content, menus, forms, graphics and metadata. We agree which elements require translation and how they will be returned to the CMS.
We create an inventory of pages, blocks and messages for localization, including navigation, buttons, forms, image alt text and SEO titles and descriptions. We agree how content will be handed over to your language team.
In WordPress, we work with tools including Polylang: linking equivalent pages, configuring language menus and implementing approved content. We also localize fields, blocks and messages within the agreed scope. For other CMS platforms, we adapt the approach to the site structure.
We adapt illustrations, banners and screenshots containing text. Where source files are unavailable, we assess whether editable graphics can be reconstructed. We export assets according to website requirements and image optimization settings.
We check longer headings, buttons, menus and forms on desktop, tablet and mobile. We adapt layouts within the agreed scope to keep language versions readable and free from overflow.
We implement approved titles, meta descriptions, headings and alt text. We map equivalent pages and help configure canonical and hreflang references for available versions according to the site architecture.
We check language menus, links, switching between equivalent pages and agreed form scenarios. We verify content completeness and language labeling and refer linguistic queries for approval.
How we work together
We adapt the scope to your project. Your team makes linguistic and subject-matter decisions, while KeboDesign handles the agreed production and technical checks.
Hover, focus or click to highlight the selected team’s responsibilities.
You provide the website URL or a copy, languages, page list and deployment requirements.
We assess CMS structure and content scope and agree the localization approach, cost, schedule and working environment.
Your team translates the text and approves content and SEO metadata.
We can create a working copy, extract the content for translation and map it to CMS fields. We implement approved content on the copy before transferring it to the target website.
You confirm approved content, brand guidelines and any market-specific differences.
We insert text and graphics, configure the agreed language navigation and adapt layouts.
Your reviewer checks the content in the website context and approves linguistic feedback.
We test links, responsiveness and agreed form scenarios and implement approved corrections.
You approve the version and separately agree publication timing and scope.
After approval, we transfer localized content and assets from staging to the target site within the agreed scope. We check language associations, links and forms and deliver the QA results.
Consistent language versions
Someone viewing a particular service should reach its language equivalent rather than always being sent to the home page. We therefore agree a page mapping and an approach for content without a translation.
In WordPress, we configure these associations using tools such as Polylang. Localization also covers menus, form labels, messages and metadata. We can copy a site, prepare the required content for translation, implement language versions and transfer agreed changes to the target site after approval.
Deliverables / Web Localization
We agree formats and the final delivery scope in the brief. Your team receives approved deliverables with a clear handover.
Content and graphics implemented in the agreed CMS or test environment, with layouts adapted to the target language.
WordPress / CMS · text · graphicsAn inventory of language equivalents and implemented titles, descriptions and navigation elements to support future updates.
Page map · metadata · languagesA record of responsive layout, link and agreed functionality tests, highlighting matters requiring a client decision.
Desktop · tablet · mobile · QAMaterials for a quote
For an initial quote, the website URL, target languages and representative content are usually enough. After quote approval, we agree the required CMS access and, if copying or migrating the site, hosting and file access. We can prepare a staging copy, localize selected content and transfer approved materials to the target website. Transfer scope and publication timing are agreed before deployment.
Questions / Web Localization
Yes. We work with WordPress and tools such as Polylang to implement approved translations of pages, menus and other agreed elements. We analyze the theme, blocks and plugins to select a workflow and correctly link language equivalents.
Your language team handles translation and content approval. We prepare materials, implement approved text and check the technical and visual aspects of localization.
We can implement approved titles, meta descriptions, headings, alt text and language associations. Target-market keywords and content need to be agreed with the client’s team.
Yes, according to an agreed set of views and scenarios. We focus on text readability, menus, buttons, forms and overflow after translation.
We agree language-switching behavior and publication scope for that content. A page map helps identify missing equivalents and avoid unintended redirects.
They do not have to. We can create a website copy, prepare and localize selected content there and transfer agreed changes to the target site after approval. Access, migration scope, material protection and publication timing are agreed after the quote.
Contact / Web Localization
Send a sample or a link to your materials. We will define requirements, delivery formats and the information needed for a quote.
Go to the contact page ↗