A multilingual website is a single digital experience designed to work across languages, markets and search environments. It needs more than translated pages. The navigation, URLs, forms, product information, legal content, search strategy and publishing workflow must all support each target market.
A plugin or language switcher can expose another language, but it cannot decide what customers search for, which claims need adaptation or whether the translated journey still works. Successful multilingual website creation starts with market and content decisions, then uses technology to deliver them reliably.
Start with markets, not a list of languages
A language does not define one market. English content for the UK may require different spelling, terminology, delivery information and commercial proof from English used in the US. French for France is not automatically suitable for Belgium or Canada. Spanish content may need substantial adaptation between Spain and Latin American markets.
Before adding languages, define:
- the countries the website will actively serve;
- the products or services available in each market;
- local pricing, delivery, payment and support conditions;
- the level of localisation each market justifies;
- who approves terminology and regulated claims;
- how frequently the source content changes.
This market-content matrix prevents a common failure: translating the whole source website even though parts of the offer are unavailable or irrelevant abroad.
Design a multilingual information architecture
Each language needs a clear, crawlable URL structure. Subdirectories such as /en/ or country-specific domains can both work when implemented consistently. Search engines need stable URLs, self-referencing canonicals and accurate hreflang relationships. Users need a visible language selector that takes them to the corresponding page, rather than sending them back to the homepage.
Navigation should be built from real translated destinations. If a page has no equivalent, the interface should not invent one. Breadcrumbs, filters, internal search, related content and footer links also need market-aware behaviour.
A multilingual architecture should specify:
- which pages exist in every language;
- which pages are market-specific;
- URL, canonical and hreflang rules;
- fallback behaviour when a translation is unavailable;
- indexation rules for search, taxonomy and archive pages;
- redirects for retired or consolidated content.
These decisions belong in the website plan before large-scale translation begins.
Choose a CMS workflow that fits the content
WordPress and WPML are common, but multilingual websites also run on Shopify, WooCommerce, PrestaShop, Magento or Adobe Commerce, BigCommerce and custom CMS platforms. The right workflow depends on content volume, update frequency, integrations and governance.
For a small corporate site, editing translations directly in the CMS may be manageable. A large ecommerce operation often needs structured exports, translation memory, terminology, product information management and automated hand-offs. XLIFF, CSV, XML, API or connector-based workflows can reduce copying and preserve formatting, but each requires testing.
The CMS should make it clear:
- which source version is authoritative;
- whether a translation is complete, outdated or awaiting review;
- who can edit each language;
- how updates are detected and assigned;
- how reusable strings and global components are managed;
- how metadata, ALT text and structured data are localised.
Our website and CMS localisation service covers these workflows across WordPress/WPML and other platforms.
Localise the complete user journey
The homepage and main service pages are only part of the experience. Forms, validation messages, cookie controls, search results, empty states, downloadable files, emails and confirmation screens often remain in the source language after a superficial migration.
For ecommerce, the scope expands to product attributes, variants, filters, size guidance, checkout, delivery, returns and customer-service content. A target-language landing page that leads to an untranslated form or checkout damages trust at the point of conversion.
A practical inventory should cover visible content and interface strings, including content loaded by plugins, scripts or third-party tools. It should also identify images containing text and documents linked from the website.
Research search demand in every target market
Translating a source keyword rarely produces the best target-market query. Search behaviour changes with terminology, product maturity and local competition. The same concept may be searched as translation, localisation, transcreation or multilingual content depending on the audience and task.
Multilingual SEO/GEO research should shape page ownership, H1s, titles, descriptions, headings, body copy and internal links. It should also separate commercial landing pages from supporting articles so that several URLs do not compete for the same intent.
For each market, map:
- the primary commercial query for each page;
- secondary terms and relevant entities;
- questions that deserve FAQs or supporting content;
- local competitors and SERP formats;
- links between articles, cases and service pages;
- content gaps that the source website does not cover.
AI search increases the need for explicit, well-supported content. Pages should explain scope, process, limitations and evidence clearly enough to be understood and cited. This is the focus of our multilingual SEO/GEO content service.
Use AI with a defined Product Truth and human controls
AI can accelerate repetitive translation, classification and product-content production. It should operate within a controlled system. The model needs reliable source facts, approved terminology, tone guidance, locale rules and instructions about what it may not infer.
Risk determines the level of human review. High-volume, low-risk catalogue fields may use automation plus sampling. Brand claims, regulated content, legal pages and high-value conversion journeys need stronger human control. The workflow should record which content was generated, reviewed and approved.
Machine translation or generative AI should not be treated as a choice between full automation and fully manual work. The useful question is which combination produces reliable content at the required scale and risk level.
Write for EN-UK readers when the market is Britain
A text can be grammatically correct and still sound imported. EN-UK localisation involves spelling, punctuation, vocabulary, units, dates and commercial rhythm. Terms such as localisation, catalogue, programme and optimised are visible signals, but naturalness goes further.
Calls to action, reassurance, examples and proof need to match how British buyers assess a supplier. Unchecked US language or literal Spanish syntax weakens authority, particularly on professional-service pages.
Native editorial review should therefore evaluate intent and tone, not only correctness.
Test the website in context
Bilingual files do not reveal every problem. In-context QA should check desktop and mobile layouts, navigation, language switching, forms, consent tools, search, pagination, downloads and interactive states.
The release checklist should include:
- one clear H1 per indexable page;
- localised titles and meta descriptions;
- correct canonicals, hreflang and HTML language attributes;
- same-language internal links;
- descriptive image ALT text where appropriate;
- no truncated text or horizontal overflow;
- localised labels for screen readers;
- working forms and confirmation messages;
- valid schema and market-appropriate contact details.
Regression testing matters. A shared template change made for one language can damage another, so representative source and target pages should be retested after each release.
Plan for continuous localisation
A multilingual website is not finished at launch. New campaigns, product ranges, legal changes and CMS updates create a continuous content flow. Without ownership and update rules, target-language pages become outdated while the source keeps moving.
Define a publishing model: what triggers translation, who approves it, the expected turnaround, and how urgent updates are handled. Maintain translation memories, glossaries, locale instructions and reusable prompts as controlled assets. Review search performance by market rather than judging all languages through aggregate traffic.
A quarterly content audit can identify orphaned pages, missing translations, weak internal links, outdated claims and new search opportunities.
Build the multilingual website around real operations
The strongest multilingual websites connect market strategy, content, technology and QA. They do not promise an international experience that fulfilment, support or governance cannot deliver.
Ontranslation localises websites across CMS platforms and combines professional linguists, SEO/GEO research, controlled AI workflows and in-context review. If you are planning a migration or repairing an inherited multilingual setup, tell us which markets, platforms and content types are involved. We will map the scope and the risks before production.

