Bilingual Business Website: When It's Worth It and How to Run It

Adding an English version to your website often sounds like the natural move for a business that wants to look professional. But a bilingual website is more than a language toggle. Every page, price, and announcement has to exist, and stay accurate, in two versions. This article helps you decide whether your business really needs one, and if so, how to build it so it doesn't become a burden.

When a bilingual website is worth it

The key question is simple: are there important customers or partners who'd rather read in English? These situations usually point to yes:

• You serve foreign tourists, expatriates, or international families living in Indonesia.
• You sell to buyers abroad or are exploring export.
• The partners, investors, or institutions you're approaching are based overseas.
• Your services can be delivered remotely to clients in other countries.

On the other hand, if nearly all your customers live in the same city and speak Indonesian, your energy may be better spent improving your Indonesian content, adding articles, or speeding up the site. A second version that rarely gets updated can actually make you look less professional.

Real bilingual, not an auto-translate button

Automatic translation widgets are cheap, but the results are often stiff, can get product terms wrong, and usually aren't picked up well by search engines. A proper bilingual website has these traits:

• Each language has its own address, such as Indonesian pages at the main address and English pages under /en.
• The text is written or edited by someone who knows both the language and the product, even if a machine helped with the first draft.
• Visitors can switch language at any point and land on the matching page.
• The site doesn't force a language switch based on location alone, because many foreigners in Indonesia still want English, and the reverse is true too.

Hreflang: telling Google which version is for whom

Hreflang is a marker in a page's code or in the sitemap that tells Google two pages carry the same content in different languages. With hreflang in place, Google can show the Indonesian version to people searching in Indonesian, and the English version to people searching in English. Without it, the two versions may be treated as competing with each other, or one of them may barely show up.

You don't need to set this up yourself, but it's worth asking your developer: does every page have a language counterpart marked with hreflang, and does the sitemap list both versions?

One source of truth for prices and key information

The most common problem on bilingual sites is information drifting out of sync. Prices have gone up on the Indonesian pages, but the English pages still show the old ones. A schedule has changed in one language but not the other. The fix is to separate data from text.

Prices, schedules, contact details, and product lists should live in one place and be read by both language versions, so you only change them once. Text that genuinely needs translating, such as descriptions and headings, sits in separate files per language that share the same keys, making it easy to spot any sentence that hasn't been translated yet.

A real example: Numekara's bilingual website

Numekara is our own education business, and its website runs in both Indonesian and English. Some of the decisions behind it:

• Every page exists in both languages, with the English version under /en.
• The sitemap includes hreflang, alongside structured data and an RSS feed.
• Programme prices are read from a single scheduled file, not retyped on every page in every language.
• Interface text is kept in separate message files for Indonesian and English.
• Ad tracking only starts after the visitor gives consent, in both language versions.

As a result, a price change happens once and applies to both languages straight away. Nobody has to hunt down every page that mentions the figure.

The extra work that comes with it

Before deciding, factor in the routine work it creates. Every new article has to be written twice. Every promotion needs an announcement in both languages. Forms, confirmation messages, automated emails, and the privacy policy all need a second version too. Agree early on who owns the English version and how long a gap is acceptable between the Indonesian and English versions going live. Without that agreement, the second language tends to fall behind.

Next steps

Start by listing the English-speaking readers you genuinely serve and the pages that matter most to them. If the list is short, you can begin with a few core pages in English and add more as the need grows. Whatever you do, design the structure from day one so prices and key data are only ever changed in one place.