Skip to main content
Auerbach International
7 min readBy Auerbach InternationalBlogWebsite Localization

Website Localization Checklist: Six Steps Before Launch

Team reviewing a laptop for a website localization checklist.

Use this website localization checklist to plan a multilingual launch: choose markets, sort content, define scope, check the technical setup, arrange review and test the result. Translation carries meaning into another language; localization also adapts the site to a market’s conventions and requirements. These six steps help your team record the decisions and checks needed before launch. Auerbach International’s website translation and localization services can support the project.

Quick Summary

  • Translation carries your meaning into another language. Localization also adapts formats, currency, images, cultural adaptation and legal details to a specific market.
  • Decide market by market, not language by language: the same language can need different adaptations in different countries, such as Spanish for Mexico vs. for Argentina.
  • Sort every content type into one of three groups: translate as is, localize, or leave out of the first launch.
  • Give each language version a distinct URL and ask your web team to implement reciprocal hreflang annotations for equivalent pages.
  • Plan the review workflow, a terminology list and a style guide before translation starts, not after launch.

What is the difference between localization and translation?

The World Wide Web Consortium (W3C) defines localization as the “adaptation” of a product, application or document content to meet the language, cultural and other requirements of a specific target market, called a locale. It adds that people often think of localization as translating the interface and documentation only, when it is often more complex, and it lists number and date formats, currency, symbols and legal requirements among the factors that change (W3C).

Translation is one part of that work. A page can be translated accurately and still feel wrong to a reader if its prices, dates, forms or contact details follow another market’s conventions.

The words are also used loosely. Auerbach’s own article, Localization... What Do You Really Mean?, notes that “localization” has different meanings for different people, so ask any vendor what it means by the word before you compare quotes. For a longer comparison of the two, see our guide to website translation services vs. localization.

Step 1: Website localization checklist: choose your markets

Start with the market, because a language and a market are not the same thing. Answer these questions before you order anything:

  • Which countries or regions do you want to reach first, and why?
  • Which languages do your customers, partners or applicants use in those places?
  • Do you need one language version for several countries, or a separate version for each? If you don’t know, please ask us.
  • Which markets have legal, tax or payment requirements that change what the site must say?
  • Which market comes second, so you can design the site to grow into it?

Write the answers down as a short list of locales, such as language plus country. That list drives every later step.

Step 2: Sort your content: translate, localize or leave out

Go through the site page by page and place each content type in one of three groups. The table gives a starting point. Your own markets and legal advice for each market decide the final answer.

Content typeOften enough to translateUsually needs localization or review
Service and product descriptionsPlain descriptions of what you offerUnits, sizes, model names and claims that differ by market
Prices and checkoutNot enough on its ownCurrency, taxes, payment methods and delivery terms
Dates, numbers and addressesNot enough on its ownDate and number formats, address and phone formats
Marketing copy and slogansRarely enoughIdioms, humor and references that do not carry across
Legal, privacy and policy pagesNot enough on its ownRequirements that differ by country; have them reviewed for each market
Forms and contact detailsLabels and instructionsLocal phone numbers, required fields and error messages
Images, video and downloadsCaptions and alt textText inside images, subtitles, and culturally specific visuals

Auerbach’s website translation and localization page lists the same kinds of changes: dates, numbers and formats; text direction, colors and imagery; references and expressions; prices and currencies; keywords and meta tags; and dynamic content and content management systems. Use that list to check you have not missed a category.

Three groups of paper layout cards with navy and pale blue blocks on a desk.

Step 3: Decide how much of the site to cover

You do not have to launch everything at once. Auerbach describes three common scopes, and the choice depends on your audience, timeline and budget:

  1. Complete website: every page and supporting content, including downloads and blog posts.
  2. Key pages only: the homepage, contact page and the main product or service pages, with more added over time.
  3. Executive summary: a short translated overview or landing page that introduces your organization in a new market. Since this is a short file, you can probably afford to do it in many languages vs. a Complete or Key Pages version into one or two.

A smaller first launch is fine if the pages that decide a purchase or an inquiry are covered completely. Our guide to making your website multilingual describes these options in more detail.

Step 4: Check the technical setup

Two technical questions can slow a project down, so raise them early with your web team.

Is the site ready for other languages and formats? The W3C describes internationalization as preparing a product or content for later adaptation across languages and cultures. Ask your web team to check support for different writing systems, text expansion and local formats before translation begins.

How will each language version be found? Ask your web team to use hreflang annotations to identify equivalent pages for different languages or regions. Google recommends these annotations to help it select an appropriate search result; Google may discover language versions without them. Each annotated page should reference itself and its alternate versions, with reciprocal links between paired pages. Choose HTML link elements, HTTP headers or an XML sitemap to maintain the annotations. An optional x-default annotation identifies a fallback for unmatched languages, such as a language selector page (Google Search Central). Hreflang does not operate the visitor’s language selector. Our multilingual SEO guide explains the wider search setup.

Step 5: Set up the review workflow

A good workflow is decided before the first page is translated. Settle these points in writing:

  • Who translates and who reviews: Auerbach’s pricing page describes a first drafter and a second reviewer with subject expertise. Confirm the human review steps included in your selected workflow.
  • A terminology list: one agreed term for each product, feature and legal concept, kept in a glossary.
  • A style guide: tone, formality, formatting and brand decisions. Our article on a multilingual style guide explains how the glossary and the style guide work together.
  • An owner: one person who answers questions from translators and keeps the guide current.
  • A review in context: a check of the pages on a staging site, not only in a spreadsheet.

If you are weighing AI-only translation against human review for part of the site, our AI vs. human translation comparison explains where each approach fits. If these steps seem overwhelming, don’t worry. We will handle them for you.

Step 6: Test before you launch

Test the translated site the way a visitor in the target market would use it. Check each of these before the launch date:

  • The language selector works from every page and returns to the equivalent page.
  • Every link, form and button works in each language, and error messages are translated.
  • Dates, numbers, currency and measurements appear in the local format.
  • Contact details, legal pages and payment options are correct for the market.
  • Text fits its space at desktop and phone widths, and right-to-left languages display correctly where relevant.
  • Hreflang annotations identify equivalent pages correctly; separately, the visitor’s language selector offers a sensible fallback when a language is unavailable.
  • A qualified native reader has checked the rendered staging pages in context, not only the source files; repeat a brief check on production after launch.

Again, we will verify these steps for you as part of the process.

Professional reviewing geometric page layouts on a laptop and tablet.

Frequently asked questions

What is the difference between localization and translation?

Translation converts text into another language. Localization adapts the content and the experience to a specific market, including formats, currency, images, cultural adaptation and legal requirements. The W3C describes localization as adaptation to the language, cultural and other requirements of a target market.

Is translation enough for a website?

Sometimes. Plain descriptions of a service can often be translated and checked. Prices, checkout, legal pages, forms and marketing copy usually need more, because the formats and requirements differ by market. Sort your content using Step 2.

What is internationalization?

Internationalization is the design and development work that makes a product or website easy to localize later. It includes handling other writing systems, longer or shorter text and local formats. The W3C notes that it does not necessarily include translating the content.

Do I need a separate URL for each language?

Plan a distinct URL for each language version so visitors can open and share it directly. Ask your web team to identify equivalent pages with hreflang annotations and check the platform’s language selector before translation starts.

Which pages should I translate first?

Start with the pages that decide a purchase or an inquiry: the homepage, your main service or product pages and the contact page. Add the rest in later phases. Auerbach describes this as the Key Pages approach.

Ready to Expand Your Global Reach?

Send your site address, the markets you have in mind and your deadline to receive a free translation quote, or call (415) 592-0042 to talk through your project. Request a free translation quote.

Sources

Ready to Expand Your Global Reach?

Contact us for a free consultation or quote — precision language services in 120+ languages.

Call UsGet a Quote