Multilingual checklist
This page is for project leads, language owners and administrators who add a language or a market. Copy it into your project tracker and tick it off; each item links to the page that explains it. It assumes the decisions on Multilingual planning are taken.
Contents
- Decisions
- Setup
- Translation
- Formats, prices and legal texts
- Right to left
- Search engines and links
- Launch
- After launch
Decisions
- To do: The market, the language and its locale code are written down (Languages and locales).
- To do: The support level of the language is known, and it is decided whether editors work in it or in English.
- To do: The address scheme is chosen: path, host or both (Addresses per language).
- To do: Fallback and untranslated content are decided per siteaccess (What visitors see when a translation is missing).
- To do: Translators, approvers and a language owner are named.
- To do: The number of content languages in use stays well below the limit of 62 (Languages, section 11).
Setup
- To do: The content language is added under Setup > Languages.
- To do: A siteaccess for the language exists with
Locale,SiteLanguageList[]and site name (Step by step: adding a second language). - To do: It is registered, matched and listed with its sister siteaccesses.
- To do: Shared folders, users and media are marked always available.
- To do: Translator roles are limited by language (and by subtree where needed).
- To do: Approval for the language is in place if wanted (Approval per language).
- To do: The design's own interface texts are translated.
Translation
- To do: The start page, menu folders and key pages are translated first.
- To do: Product pages, basket and checkout texts are translated for a store.
- To do: Machine-prepared drafts, if used, are reviewed by a reader of the language (Assisted translation with Exponential Intelligence).
- To do: Mail texts (order confirmation, registration, newsletter) exist in the language.
Formats, prices and legal texts
- To do: Dates, numbers and amounts look right on product pages, the basket and confirmation mail (Currencies, dates and formats).
- To do: The currency charged, prices per currency or exchange rates, and rounding are decided and tested.
- To do: VAT rules for the market are configured and confirmed by a tax adviser.
- To do: Terms, returns policy, privacy notice and imprint are translated and checked by someone qualified.
- To do: Shipping countries and costs for the market are set (Shipping and handling).
Right to left
Only if the language is written right to left (Right-to-left markets):
- To do: The page frame prints
dir="rtl"for the siteaccess. - To do: Stylesheets use logical properties; icons along the line are flipped.
- To do: Mixed text and forms were checked by a native reader, also at phone width.
- To do: The left-to-right sites are unchanged.
Search engines and links
- To do: The language switcher links each page to the same page in the other languages (The language switcher).
- To do:
hreflangalternates are built in the pagelayout, if wanted (Telling search engines). - To do: The language has its own sitemap entries (Sitemaps).
- To do: Feeds of the language point to its own address (Feeds and syndication).
- To do: Cross-brand links stay in the visitor's language where possible (Links between your sites).
Launch
- To do: Caches cleared after the last settings change (INI and content; Velocity's response cache when Velocity serves the site).
- To do: Every address of the language answers over HTTPS.
- To do: A test order, sign-up or contact form works in the language.
- To do: The other languages show exactly what they showed before.
After launch
- To do: Setup > Languages is checked monthly for languages with few objects or no siteaccess.
- To do: Changed source pages have their translations updated (Keeping translations up to date).
- To do: Search queries and contact requests in the language are reviewed for missing content.
- To do: Removing a translation is only done by people who know it cannot be undone.
Related pages
- Selling in several languages and markets
- Multi-brand checklist
- Planning multisite and multilingual projects: checklists
- Building a multilingual site: checklist
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.