Japanese Navigation and Menu Localization:
Labels, Breadcrumbs, and IA That Feel Natural

TL;DR

Key Takeaways

• Japanese global nav is noun-style — 設定 not 設定する, ユーザー管理 not ユーザーを管理. Verb-form labels read as instructional and break the visual balance of the bar.
• Katakana vs kanji is decided per term, not globally — 設定 and 料金 take kanji; ダッシュボード and テンプレート stay katakana. Forcing either direction reads as wrong.
• Breadcrumbs follow Japanese conventions — the first crumb is ホーム or トップ, the current page is non-linked text, and the region is often labelled 現在地 for clarity and accessibility.
• Global-nav width must be planned for rendered kanji — short character counts can render wide, and a bar that fits seven English items can wrap with Japanese labels.
• Japanese B2B IA is more explicit — buyers expect 会社概要, 料金 / お見積もり, and 資料ダウンロード surfaced directly, not buried under a single Resources or Company menu.

Why Navigation Is the First Trust Signal

Navigation is the most-seen surface of any product. It is present on every page, it frames every workflow, and for a Japanese B2B evaluator it is the first place the eye lands when assessing whether a foreign product has actually been localized or simply run through translation. A body paragraph that reads slightly unnaturally can be forgiven as detail. A global nav whose labels are grammatically foreign is structural — it sets the tone for everything below it.

The difficulty is that navigation localization rarely fails on accuracy. The words are usually correct. Settings really does mean 設定. Pricing really does mean 料金. The failures are at a layer translation memory does not reach: the grammar of the label (noun versus verb form), the script choice (katakana versus kanji), the conventions of the breadcrumb trail, the rendered width of the bar, and the overall shape of the information architecture. These are decisions, not translations, and they are usually made by default rather than deliberately.

Japanese business users read these signals fluently because Japanese B2B software has converged on strong conventions over two decades. A nav that respects those conventions disappears — the user finds what they need without noticing the nav. A nav that violates them creates a small, persistent friction on every page, and that friction is exactly what procurement and evaluation teams register as a localization-quality risk.

Noun-Style vs Verb-Style Labels

English navigation mixes grammatical forms freely. A single nav can contain a noun (Settings), a gerund (Reporting), an imperative (Get Started), and a verb phrase (Manage Team). English readers do not perceive this as inconsistent. Japanese navigation does not work this way. The convention is strongly noun-form, and a Japanese nav that mixes grammatical forms reads as uneven and amateurish.

The most common error is translating an English verb-phrase label literally into a Japanese verb phrase. Manage Users becomes ユーザーを管理 when the natural Japanese nav label is ユーザー管理 — the noun compound. Get Started becomes 始める when, as a nav item rather than a button, the natural form is はじめに or 使い方. The verb forms are not wrong as language; they are wrong as navigation grammar.

The exception that proves the rule is the primary call-to-action button. Buttons take the verb form: 無料で始める (Start Free), お問い合わせ (Contact Us), 資料をダウンロード (Download Materials). The grammatical distinction is real and Japanese users read it instantly — a verb form signals an action the user takes, a noun form signals a place the user goes. Putting a verb form in the nav blurs that distinction.

Katakana vs Kanji: Choosing the Script Per Term

The second navigation decision is script. Every navigation term has to land in one of three forms — kanji, katakana, or English left as-is — and the choice is made per term, not by a global policy. Teams that apply a blanket rule (translate everything to kanji, or keep everything in katakana) produce navigation that feels wrong in opposite ways.

The governing principle is usage, not translatability. If a term has an established kanji form that Japanese business users encounter daily, use the kanji. If a term entered Japanese through software and never developed a natural kanji equivalent, leave it in katakana. Forcing a kanji translation onto a katakana-native term is the more visible error: rendering Dashboard as 制御盤 or 計器盤 reads as bizarre, because no Japanese SaaS product calls it that — it is ダッシュボード.

The pattern: terms tied to long-standing business vocabulary (設定, 料金, 機能, 事例, 資料) take kanji; terms that arrived with software and have no kanji tradition (ダッシュボード, テンプレート, サポート) stay katakana. The danger zone is the small set of terms where both forms circulate — 連携 versus インテグレーション, 資料 versus リソース. There, the kanji form is almost always the safer choice for a B2B audience, because it reads as more precise and less imported.

Breadcrumbs and 現在地 Conventions

Breadcrumbs are where Japanese navigation conventions diverge most clearly from Western defaults, and where automated localization most consistently leaves artifacts. The separator itself rarely needs to change — the greater-than sign ( > ) is standard on Japanese B2B sites, and the slash ( / ) is also accepted. What needs attention is the first crumb, the current-page treatment, and the labelling of the breadcrumb region.

Three conventions distinguish a native Japanese breadcrumb trail. First, the home crumb is almost never left as the English word Home — it is ホーム or トップ (top page). Second, the final crumb, representing the current page, is shown as plain non-linked text, never as a clickable link, and Japanese users expect this strongly enough that a linked current crumb reads as a bug. Third, Japanese sites frequently label the breadcrumb region itself with 現在地 (current location) — a convention far rarer on English sites and valued both for clarity and for screen-reader accessibility.

A subtler point concerns how breadcrumbs interact with information architecture. English breadcrumbs sometimes compress or skip levels to stay short. Japanese B2B users tend to prefer the complete hierarchical path, because the breadcrumb doubles as a confirmation of where they are in a structure they expect to be explicit. Truncating the trail to save space works against the Japanese expectation that location is always clearly signposted.

Global-Nav Length and Width Constraints

A horizontal global nav designed for English labels frequently breaks when the Japanese labels render, and the reason is counter-intuitive: the Japanese labels are usually shorter in character count but wider on screen. Each full-width kanji or kana character occupies roughly the width of two Latin characters. 料金 is two characters but renders at about the width of four Latin letters; お問い合わせ is six characters but renders nearly as wide as the English Contact Us.

This means character-count budgets imported from the English design are misleading. A nav bar that comfortably fits seven English items can wrap or overflow once the Japanese labels are in place, especially if one label is a long polite form like お問い合わせ or 資料ダウンロード. The fix is to plan nav width against the rendered Japanese width, test with the actual longest labels in place, and avoid pairing very short kanji labels (機能, 料金) with long katakana or polite-form labels (インテグレーション, お問い合わせ) in a way that makes the bar look unbalanced.

Mobile navigation has a related but inverted issue. Because Japanese labels are short in character count, they fit comfortably in a vertical hamburger menu — but the same brevity can make tap targets ambiguous. A two-character label like 設定 gives a small touch area, so Japanese mobile navs often pair the label with an icon or add supporting text to keep the target legible and tappable.

Information Architecture Japanese B2B Users Expect

The deepest navigation decision is not labelling at all — it is structure. Western SaaS sites have trended toward flat, minimalist navigation: a handful of top items, with company information, documentation, and pricing details tucked behind a single Resources or Company dropdown. Japanese B2B buyers expect a more explicit, hierarchical architecture, and a nav that hides the sections they need creates friction in exactly the moments that matter for evaluation.

Three sections Japanese buyers expect to find directly, not buried, are these. A company-information section — 会社概要 — is close to mandatory for B2B credibility in Japan; its absence or burial is read as a trust gap. A clear pricing or estimate path — 料金 or, for enterprise sales, お見積もり (request a quote) — because Japanese procurement often begins with a formal estimate. And a documents or downloads section — 資料ダウンロード or お役立ち資料 — because requesting a service-overview document (資料請求) is a standard first step in the Japanese B2B funnel, often preceding any conversation.

Surfacing these in the global nav is not decoration. It signals to a Japanese evaluator that the vendor understands how Japanese companies actually buy. A foreign product that forces a Japanese buyer to hunt for 会社概要 or that has no 資料請求 path communicates, before any feature is examined, that the Japanese market was an afterthought.

12-Point Audit Checklist for Japanese Navigation Localization

Frequently Asked Questions