What is bilingual website design, and who in Japan needs it?
Bilingual website design is planning, designing and building a site so that two languages each work as a complete site, rather than bolting a translation onto one version. In Japan the pair is almost always Japanese and English.
Two groups need it most. The first is Japanese companies reaching overseas buyers, partners, investors or job applicants: manufacturers, software firms, craft brands, universities and tourism operators. Their Japanese site already works, but the English pages are thin, out of date or produced by a browser translation button. The second group is foreign-owned businesses in Japan, such as international schools, law and accounting practices serving expatriates, real-estate brokers, clinics, recruitment firms and subsidiaries of overseas groups. They often start in English and then discover that Japanese customers, landlords, regulators and job seekers expect a proper Japanese version.
Both groups share the same problem. Each language has its own search behaviour, its own reading habits and its own expectations about how a trustworthy company site looks. A good bilingual website design respects both without letting either version become a second-class copy.
Japanese firm going global
Starts with a strong Japanese site; needs English pages that stand on their own for overseas search and sales conversations.
Foreign-owned firm in Japan
Starts in English; needs Japanese pages trusted by local customers, partners and candidates.
Subdirectory, subdomain or separate domain: which URL structure suits a bilingual website?
In bilingual website design for Japan, subdirectories on one domain (/ja/ and /en/) are the simplest and strongest choice. They are cheap to run, share one hosting setup and let both languages build authority on the same domain.
Google's guidance on managing multi-regional and multilingual sites lists the options side by side: country-code domains, subdomains, subdirectories and URL parameters. It describes subdirectories as easy to set up and low maintenance, and it marks URL parameters such as ?lang=en as not recommended. The same page says Google works out a page's language from its visible content, not from the URL or the lang attribute, which is why each language version needs genuinely translated text rather than a mix.
A subdomain (en.example.jp) makes sense when the English site runs on a different platform or is managed by a different team. A separate domain, such as a .jp for Japan and a .com for the world, makes sense when the two audiences are really two businesses with different products. Both cost more to maintain, and both split your link authority.
- Choose subdirectories when one team manages one site in two languages
- Choose a subdomain when the English site lives on a separate system
- Choose separate domains when the offer differs by market, not just by language
- Avoid ?lang= parameters and cookie-only switching
How does hreflang work on a Japanese and English bilingual website?
hreflang is a tag that tells Google which URLs are translations of each other, so a searcher in Osaka gets the Japanese page and a searcher in London gets the English one. On a bilingual website design, every page carries a small set of these tags.
Google's documentation on localized versions of your pages is precise about one rule that trips up many sites: each language version must list itself as well as all the other versions, and if the pages do not point to each other, the tags may be ignored. The same page explains the reserved x-default value for visitors whose language matches neither version, and it accepts three ways to publish the tags: in the HTML head, in HTTP headers or in the XML sitemap.
We generate hreflang from the CMS, never by hand. When an editor links the Japanese and English versions of a page, the tags appear on both automatically. When a page exists in only one language, no tag is output for the missing one, so Google never follows a link to an empty page. We then check the result in Search Console and with a crawler before launch.
- ja on Japanese pages, en on English pages, plus x-default pointing to your language chooser or main version
- Every tag set includes the page's own URL
- Tags only link pages that truly exist in both languages
- Canonical tags point to the same-language URL, never across languages
Japanese and Latin typography in bilingual website design
Good bilingual website design gives Japanese and English different type settings on the same site. Japanese characters are square, dense and wide; Latin letters are narrow with ascenders and descenders. One font size and one line height for both makes one of them look wrong.
We set type per language using the lang attribute. Japanese body text usually gets a slightly smaller size than English, a more generous line height and no letter-spacing tricks borrowed from Western headlines. Headings get their own scale because a six-character Japanese heading and a six-word English one take up very different widths.
Fonts are the next decision. A Japanese web font carries thousands of glyphs, so loading a full family can add megabytes to a page. We either subset the font to the characters your site uses, load it with a font-display setting that shows text immediately, or use the system font stack that Japanese phones and computers already have. Latin text gets its own font so English pages do not fall back to the Latin glyphs inside a Japanese font, which often look cramped.
Japanese body text
Readable size, line height around 1.7 to 1.9, no justified text on narrow screens, and a font with clear kanji at small sizes.
English body text
Shorter line height, comfortable line length of roughly 60 to 75 characters, and a Latin font chosen for your brand.
Mixed lines
Product names, numbers and acronyms inside Japanese sentences use the Latin font, sized to sit well with the kanji.
Why do Japanese headings break in odd places, and how do we fix it?
Browsers can break Japanese text between almost any two characters, so a heading can split in the middle of a word and leave one character alone on the last line. The fix is a mix of CSS rules, careful heading lengths and manual checks.
The W3C's Requirements for Japanese Text Layout, written by its Japanese Layout Task Force, documents the traditional rules: characters that must not start a line (such as closing brackets and small kana), characters that must not end one, and how to compose Japanese mixed with Western text. Modern browsers apply the basic line-breaking rules by default; the problems are mostly in headings, buttons and narrow cards.
MDN's reference for the CSS word-break property describes keep-all as stopping word breaks inside Chinese, Japanese and Korean text, and lists a newer auto-phrase value, still marked experimental, that uses language analysis to avoid breaking in the middle of natural phrases. We use these selectively on headings and add fallbacks, because a heading that never breaks can overflow on a small phone.
- Headings: phrase-aware breaking where supported, tested at 360 px width
- Buttons: short labels in both languages so neither wraps
- Navigation: widths set for the longer of the two labels
- Body text: browser defaults, which already follow the basic rules
Language switcher design: where to put it and how it should behave
In bilingual website design the switcher is small but decisive: put it in the top-right of the header on every page, label it with each language's own name (日本語 and English), and make it take the reader to the same page in the other language, not the home page.
Flags are a poor choice. A British or American flag says “country”, not “language”, and English speakers in Japan may be Australian, Indian or Filipino. Written language names are clearer, and a small globe icon beside them helps people who cannot read either word.
The switcher should never be automatic. Google's guidance advises against redirecting users to a language version based on what the site thinks their language is, because that can stop people and crawlers from reaching the other version. A foreign resident reading on a Japanese-language phone should still land on whichever page they clicked, then choose. If a page has no translation yet, the switcher says so and offers the nearest equivalent, rather than silently dropping the reader on the home page.
Desktop
Text links in the header, current language shown as active, second link always visible.
Mobile
Kept outside the hamburger menu so it is one tap away, with a large enough touch area.
Who writes the Japanese copy on a bilingual website, and how does the workflow run?
In our bilingual website design projects, you or your translator write or approve the Japanese copy, and we handle everything around it: page structure, loading, layout checks and publishing. We write and edit English ourselves; we do not produce native Japanese copy.
The workflow that works best starts with the language your team knows best. A Japanese manufacturer writes Japanese first, then a translator or bilingual staff member adapts it for overseas readers, and we edit the English for clarity and search terms. A foreign-owned clinic in Tokyo writes English first, then a translator produces Japanese, and a Japanese-speaking colleague checks tone.
To keep this orderly, each page in the CMS carries a status per language: draft, in translation, in review, approved. A page publishes in a language only when that language is approved. We supply a spreadsheet or export file for translators who prefer to work outside the CMS and import it back so nothing is copied and pasted by hand.
- Source language chosen per project, not assumed
- Translator receives page context and screenshots, not just loose strings
- Character limits noted for buttons, menus and headings
- Glossary of product names, job titles and legal terms kept for both languages
- Final Japanese read-through by someone on your side before launch
Should the English pages be a translation or written separately?
Adapt, do not mirror. In bilingual website design the two versions should cover the same offer, but each should be written for its reader, and some pages may exist in one language only.
Japanese company sites often open with a greeting from the president, a corporate philosophy and a detailed company outline table. Overseas readers usually want to know what you make, who uses it and how to contact a named person, in the first screen. English pages for a Japanese firm therefore often reorder sections and cut formal passages, while keeping the facts identical.
The reverse applies to foreign-owned firms. Japanese readers often look for company details, representative name, registered address, access directions from the nearest station and clear pricing or fee tables before they trust a business. A Japanese version that simply translates a breezy English page can look thin. We plan both page trees together at the start, marking which pages are shared, which differ and which exist only in one language.
How does a bilingual website rank in both Japanese and English search?
With bilingual website design, each language ranks on its own merits: its own keywords, its own titles and descriptions, its own internal links and its own backlinks. hreflang connects the pair, but it does not make a weak translation rank.
Keyword research has to happen in each language separately. Japanese searchers mix kanji, hiragana, katakana and Latin letters in queries, and the most common way to write a term is not always the one a dictionary gives. English searchers abroad use their own names for Japanese things. We research English terms ourselves and build the Japanese page structure around terms you, your writer or a Japanese SEO specialist confirm.
On the technical side, both versions get their own sitemap entries, their own titles and meta descriptions, and structured data in the page's language. Search Console lets you compare performance by country and by page, so you can see whether /en/ pages are reaching overseas users. For AI assistants and AI search features, clear one-sentence definitions, question headings and consistent company details in both languages help those systems describe you correctly. Nobody can guarantee rankings or AI citations in either language.
Which CMS is best for a Japanese and English bilingual site?
For bilingual website design in Japan, WordPress with a mature language plug-in suits most company sites; a headless CMS with built-in locales suits larger or more design-driven sites; a static site generator suits small sites that change rarely. The right pick depends on who edits the site each week.
WordPress is familiar to many Japanese marketing teams and translators, has a Japanese admin interface, and multilingual plug-ins handle paired pages, translated menus and hreflang. The trade-off is plug-in updates and hosting care. Our WordPress developer for Japan page covers that route in depth.
Headless CMS tools keep content in structured fields with a locale per entry, and a front end built in Astro or Next.js renders fast pages in both languages. They suit sites with many templates or content reused across web and apps. A plain static build, where we edit content for you, is cheapest to run and very fast, but your team cannot edit it without us.
WordPress + language plug-in
Editors get a familiar dashboard and paired-page linking; you pay for plug-in licences and keep updates current.
Headless CMS
Structured locales, fast front end, good for large sites; content-heavy builds start at US$300.
Static build
Lowest running cost for small sites from US$150; changes go through us or a developer.
How much does bilingual website design cost?
With BtechWaleTech, a bilingual brochure site of up to 100 pages starts at US$150 and takes one to two weeks once both sets of copy are ready. A content-heavy site of 299 or more pages starts at US$300 and takes three to five weeks.
The cost of bilingual website design reflects templates, language architecture and testing, not word count. A 20-page company site in two languages is still a 20-template-page job with two content loads. What pushes the quote up: many unique templates, bilingual forms that send different confirmation emails, a translator workflow inside the CMS, a store or booking engine in both languages, and integrations with systems that only speak one language.
Translation is a separate line in your budget, paid to your translator. For company sites, many clients underestimate it; a translator's quote for a thirty-page site is worth getting before you fix a launch date. For wider yen budgeting across site types, see website design cost in Japan.
In bilingual website design, every form, auto-reply and error message needs both languages, and they are the parts teams forget. A Japanese visitor who fills in a Japanese form and receives an English confirmation email notices immediately.
Japanese forms have their own conventions: name fields in kanji plus a furigana reading, postal code lookup that fills the prefecture and city, and address order from large to small. English forms use given name and family name fields and a free-form address. We build a form for each language rather than one form with translated labels.
Japan's Act on the Protection of Personal Information is administered by the Personal Information Protection Commission. We build the privacy page layout, consent checkboxes and data-minimal forms; the wording of your privacy policy in both languages, and whether other countries' laws also apply to your English audience, is for your own lawyer to confirm.
- Separate Japanese and English form layouts, not translated labels
- Auto-reply emails in the language the visitor used
- Error messages and validation text in both languages
- Privacy, terms and cookie notices paired and linked by hreflang
Working with a team in India on your bilingual site: hours, calls, payment and the first two weeks
India runs three and a half hours behind Japan. Our working day overlaps your afternoon, from about 12:30 pm JST, and continues into your evening, so a call after lunch and a written summary before you leave the office is a normal rhythm.
Calls happen on Google Meet or Zoom in English. On a bilingual website design project, it helps if one person on your side reads both languages: they can answer our layout questions about the Japanese text and pass decisions to colleagues. We quote in USD; you pay in USD or JPY by Wise or bank wire, or by PayPal, with invoices issued from India and nothing billed before you approve the written quote.
Domain, hosting, CMS logins and analytics are opened in your company's name. We work through user accounts you create and can remove at any time.
Days 1 to 5
Kick-off call, a shared page tree marking which pages exist in both languages, the URL pattern agreed, and a copy template sent to you and your translator.
Days 6 to 10
Typography sample page in Japanese and English on staging, header and switcher design approved, and the first template built with real copy in both languages.
Red flags when you hire for bilingual website design
The biggest warning sign in bilingual website design is a quote that treats the second language as a plug-in toggle. If a developer cannot explain how hreflang, canonicals and the switcher will work, the Japanese or English half will likely underperform in search.
Other warnings: a designer who shows only English mock-ups and promises the Japanese “will fit”; a site that loads a full Japanese font on every page; forms with one set of fields for both languages; and machine-translated pages published without anyone fluent reading them. A cookie-based switcher, where one URL shows different languages to different people, is another problem, because a crawler sees only one of them.
- No written plan for URLs and hreflang before design
- Mock-ups in one language only
- Machine translation published without review
- One URL serving two languages
- Domain or CMS registered in the developer's name
Bilingual website design launch checklist
Run through this bilingual website design checklist on staging before the site goes live. Each item catches a problem that is cheap to fix now and expensive after Google has indexed the wrong thing.
- Every page URL follows the agreed /ja/ and /en/ pattern
- hreflang tags are reciprocal and include x-default
- Canonical tags point to the same-language URL
- The lang attribute matches the page language
- Japanese headings checked at phone width for bad line breaks
- Web fonts subsetted or served from the system stack
- Switcher leads to the matching page in the other language
- Forms, emails and error messages exist in both languages
- Both sitemaps submitted and both versions checked in Search Console
- A fluent reader has approved the Japanese and the English
Worked example: a hypothetical Yokohama engineering firm adds English
This scenario is made up to show how bilingual website design works in practice. Picture a 40-person precision engineering firm in Yokohama with a ten-year-old Japanese site. Overseas buyers find it through trade shows, then give up because the English page is a single PDF brochure.
We would propose moving the site to subdirectories: the Japanese pages keep their content under /ja/ with redirects from the old URLs, and a new /en/ section covers capabilities, materials, tolerances, industries served, certifications the firm already holds, and a contact form that goes to the English-speaking sales manager. Not every Japanese page gets an English twin; the president's message and local recruitment pages stay Japanese only, and hreflang links only the pairs.
The firm's sales manager adapts the Japanese capability text into English drafts; we edit them for overseas search terms such as the machining processes buyers type. Build would start from US$150 for a site of this size. After launch, the firm could watch Search Console to see whether English pages gain impressions from Europe and North America and decide whether monthly SEO from US$150/mo is worth adding. Any results would be the firm's own; we would not forecast them.
Manufacturers with larger catalogues may prefer our manufacturing website design approach.