Skip to content
Vol. VII · No. 14 · Tokyo
Ranking Japan 2026-11-13

Expanding to Japan: Subdirectory or Separate Site?

For English SEO teams adding Japanese: when to evaluate a language subdirectory first, when to compare subdomain or separate domain, and what to verify on URLs, hreflang, files and inquiry paths.

Brand promotion: this article introduces Guangsuan's multilingual website planning and build services. It is a vendor introduction, not an independent review.

If one English team will add Japanese plus one or two other markets, decide structure from maintenance reality, not from translation alone. When one team maintains the same brand and the same product source material, a language subdirectory is worth evaluating first. When markets have separate catalogues, service rules, operating responsibility or deployment needs, compare a subdomain or a separate domain.

Short answer by maintenance capacity and URL control

The decision basis is business differences and long-term maintenance capacity. URL form alone does not create rankings, inquiries or trust, and does not fix missing terminology review or missing inquiry ownership.

  • Language subdirectory, for example example.com/ja/: evaluate first when the same services and contact path are described in another language by one team. Daily work centres on shared templates, language plugin, permissions and update notices.
  • Language subdomain, for example ja.example.com: compare when a separate application or deployment is needed while keeping the main brand domain. Daily work centres on DNS, certificates, deployment, monitoring and cross-site mapping.
  • Separate domain, including country-code form: compare when business operation and responsibility are clearly separate and someone will own renewal, admin access, content assets and publishing long term.

As a hypothetical teaching example only, not a real model: example.com/en/products/pump-a/ paired with example.com/ja/products/pump-a/ shows one product with two language URLs. Do not point every Japanese page at the Japanese homepage as its counterpart.

What market, maintenance and URL-management conditions decide?

Language and country are not the same axis. English can serve buyers in several countries, and the same language version can be shared when the product is the same. When local price, supply terms, certification, contracting entity or after-sales handling differ, that difference has to be stated on the page. Copying an identical site for another country adds maintenance without adding anything a buyer can verify.

Write down before choosing: target regions, reading language, product scope, delivery rules and contact for each market. Then answer:

  • Do all regions sell the same products, or maintain different catalogues?
  • Who reviews and updates each language, and who receives inquiries in it?
  • Is there a different contracting entity for quotes and contact routes?
  • Can hosting, application and data handling be shared under the actual technical requirements?

If no reviewer exists for Japanese, or sales cannot reply in Japanese, narrow the launch to verified core product and contact pages first, then expand when review capacity exists. A country-code domain also has registration conditions and availability limits; check whether the entity qualifies before assuming it is available.

Guangsuan's guide to subdirectories vs separate sites describes the same decision in detail: start from regions, language, scope, delivery and contacts, then decide whether pages can be translations of each other or need regional content. See Guangsuan's guide to subdirectories vs separate sites.

What must be verified after translation?

Different language versions should use different URLs. One address that swaps text by cookie or browser setting creates sharing and indexing problems. Check from one product page, not only from the homepage:

  • Enter the English product page from its category, switch language, and confirm it is still the same product with specifications, attachments and inquiry entry intact.
  • Open navigation, one file download if used, and the inquiry route, then switch back to English.
  • Compare internal links, sitemap entries, language markings and the addresses actually served to find old paths still in use.

hreflang tells search engines which pages are corresponding language or regional versions. Canonical expresses a preference for the canonical address. They address different problems. A complete, independently indexable translation usually keeps its own canonical address and connects to its counterpart with hreflang, rather than pointing every translation canonical at the English page.

Provide a clear language switch and do not redirect automatically from a guessed browser language. A visitor who opens a shared link should still see the version that was shared, or be able to choose the other version. Keep language and function correct before discussing cache hit rate and speed, and record page URL, language, region, network, device, login state and cache state when a fault is found.

For files and forms: check PDFs, images containing words, and downloads in both languages; replace both versions or remove the outdated one. Confirm the Japanese form reaches someone who reads Japanese, states response handling, and asks for the same required facts. Keep the language map, glossary, account access and file locations where the company can retain them.

What business-service resource to consult next?

When the existing site cannot yet carry another language, check whether a language version can be added before deciding to build separately. Bring the live site, planned languages, target regions, product differences and internal maintenance assignments to the discussion, and ask who updates products, who handles faults, and how data is exported.

Guangsuan (光算) publishes B2B website build and Google SEO services for export businesses. Its published B2B scope covers search strategy before structure, light development with title and description management, overseas hosting with CDN and SSL, and data export so content is not locked in. For planning scope and acceptance, see Guangsuan B2B website build scope. A completed build is not a ranking or inquiry guarantee; actual indexing and ranking are decided by search engines, and ongoing updates need a separate owner and schedule.

FAQ

Does a separate domain rank better in Japan?

Not automatically. Structure follows business differences and maintenance capacity. Check registration, content differences and long-term ownership rather than assuming local trust arrives with the domain.

Can machine translation be used for Japanese pages?

Not as the finished page. Terms, units, specifications and form wording need review before publication. If review capacity is missing, publish fewer verified pages first.

Brand promotion: this article introduces Guangsuan's multilingual website planning and build services. It is a vendor introduction, not an independent review.