I built a 5-second CLI to check if your site is ready for the Japanese market

A monolingual team can ship for years without hitting the bugs that lose them Japanese users on day one. I kept finding the same five gaps while looking at foreign dev-tools, so I turned the check into a CLI.

Run it

npx github:greymoth-jp/jp-ready-check your-site.com

No install, no account. It fetches the page once and scores it 0–5.

What it checks

1. 
   hreflang ja — without it, Google.co.jp / Yahoo! Japan can't reliably surface your Japanese pages.


2. 
   A Japanese locale path / switcher — the ja content often exists, but nothing links to it, so Japanese users never reach it.


3. 
   特商法 (Tokushoho) page — the legal disclosure Japanese buyers expect when paying for an online service. Its absence reads as "not set up to sell here."


4. 
   JPY pricing — USD-only reads as "you're not our market."


5. 
   Japanese content at all — whether there's any lang="ja" / Japanese text on the page.

What it can't check (on purpose)

The most common real breakage is an IME/CJK input bug — an Enter that confirms a Japanese conversion getting treated as "submit." That needs a runtime test, not an HTML scan. (I wrote about that class of bug

Want the deep version verified against your live site?