JournalGuide
Guide / RC JOURNAL

Should your small-business website add a third language?

Look for a real customer need, test a complete path in the proposed language, and plan who will keep it accurate before expanding the site.

Layered paper web pages connected by red thread to a small storefront, representing different language versions of one website

A customer asks whether your service information is available in a language your website does not yet support. Another employee says they could translate the home page quickly. Should you add that language across the site?

Add a language when it helps a defined group of customers complete a real task and you can maintain the whole path. A translated welcome message alone may create more confusion if the service details, form, confirmation, and follow-up remain inaccessible. If the evidence is thin, keep the current site clear and offer a reliable way to ask for help while you learn more.

Canada’s population is linguistically diverse, but a national figure cannot choose a language for your business. In the 2021 Census, 12.7% of people in Canada spoke a language other than English or French predominantly at home. That is a measure of home language among census respondents, not a measure of online language preference, your local market, or demand for a particular translation. Some people who use another language at home also use English or French comfortably. Treat the census as a reason to ask better questions, not as a sales forecast.

Find the customer task before choosing the language

Start with the customer journey. Is the person trying to understand eligibility for a service, compare options, book a visit, read a policy, or ask a question? Name the task and every step from the first page to the response they receive. The answer may be a complete translated journey, a clearer existing page, a staffed contact route, or no site change yet.

Collect signals you can actually interpret: requests to staff, languages used in incoming inquiries, feedback about confusing pages, and the parts of the site where people ask for clarification. Ask permission before recording personal details and summarize only what the decision needs. A visitor’s browser language or an automated translation event is weaker evidence of what that person wants from your business. Do not infer language preference from someone’s name or appearance.

For a local service business, check whether the proposed language is relevant in the area and among the customers the service can actually reach. Census data can describe a community, but it cannot tell you that those residents are prospective customers or that they need your website in the language spoken at home. Ask customer-facing staff what they can support accurately after a visitor submits a form. A page that invites an inquiry in a language nobody can answer creates a broken promise.

Compare three sensible levels of support

Keep the existing languages and improve the contact route. If requests are rare or unclear, make the existing information easier to scan and explain how someone can ask for language assistance. This has less translation and review work. Its limit is that a visitor still may not be able to evaluate the service independently.

Translate one complete task. If a recurring need is clear, choose the service page and the connected instructions, form labels, error messages, confirmation, and response process. This is a useful pilot because a customer can finish one journey. Label links that lead to untranslated content so the switch is not a surprise.

Maintain a broader language version. This can make sense when several important tasks require it and someone owns ongoing translation. It also multiplies review work for prices, availability, policies, forms, support content, and seasonal changes. A new language is a continuing publishing commitment, not a one-time file delivery.

The decision is not a competition for the largest possible language menu. A small, accurate section may help more than a full site that falls out of date. Set a review owner and a way to catch changes in the source material before publishing the translated version.

Make the translated path usable

Give each translated page a stable URL and a visible language link. Google’s guidance for multilingual sites recommends separate URLs for language versions and links that let people switch themselves. It cautions that automatic redirects based on a guessed language can prevent visitors and crawlers from reaching a version. Connect equivalent pages rather than sending every switch to a language home page.

Use the language’s own name and script in the switch. The W3C’s internationalization guidance recommends visible navigation to localized pages and names written in the target language. Test the layout with the actual translated text: words may grow, break at different points, or need right-to-left direction. Check the phone layout, navigation, forms, error states, and messages as well as the article or service page.

Ask a qualified speaker to review meaning, tone, and task instructions in context. Machine translation can provide a working draft, but service boundaries, eligibility, safety information, prices, and next steps need human review. Keep a record of what was translated and when the source changed so you can spot stale versions. A language label should describe the content a visitor will actually find; it should not promise full support where only one page exists.

For corresponding pages, use language-aware metadata and reciprocal alternate links when they are genuine equivalents. Google’s localized-page documentation explains how these signals point searchers to a suitable version. They help describe pages; they do not guarantee rankings or traffic. Keep a clear title and description in each language, and check that the page itself, not just its metadata, is translated.

Keep French obligations separate from an optional additional language

If your business operates in Québec, decide the French version first. The Office québécois de la langue française explains that a Québec business’s website may offer other languages, while content concerning products or services offered in Québec must remain available in French. The applicable details depend on the business and content. Adding another language does not replace a complete, usable French path for the Québec audience. For a specific compliance decision, confirm the current official guidance for your situation.

Our guide to planning an English and French website covers the basic journey and page-pair work. The additional-language decision uses the same discipline, with a separate question about whether the customer need and ongoing support are there.

Make a decision you can revisit

Write down the task, the evidence for the language, who will answer inquiries, which pages and messages are in scope, and who approves updates. Set a review point after the path has been in use. Ask staff whether the new content answered the questions it was meant to answer, and look for corrections or abandoned handoffs. Do not treat raw page views as proof that people understood the information or became customers.

If the need is still uncertain, publish no new language yet and improve the current paths. If a complete pilot is feasible, start there and expand only after the business can maintain it. Professional help is useful when page structure, forms, search metadata, accessibility, and translation handoffs need to work together. For a website project, tell Red Comet about your audience, preferred languages, and the task visitors need to complete so the scope can be discussed before development.

Sources

WHAT COMES NEXT

Have a project in mind?

Explore what we make and how we can help shape your next idea.

Explore our services