Japan SEO

Japan isn't a non-Google market — Google leads and Yahoo! Japan has run on Google's search technology since 2010. The real work is Japanese keyword research across kanji, hiragana, katakana, and romaji, plus genuine localization over translation.

First published: Jul 3, 2026 · Last updated: Jul 19, 2026 · Advanced
demand #4 in Market-Specific SEO#11 in International SEO#249 on the site

Japan is not a non-Google market. Google leads Japanese organic search, and Yahoo! Japan has run on Google's search and ad technology since a July 27, 2010 deal — reconfirmed operative through October 2022 by a 2024 Japan Fair Trade Commission filing, and under a commercial contract LINE Yahoo extended through at least March 2027 after abandoning a considered switch to Naver's search technology — so most of what people call 'Yahoo! Japan SEO' is just SEO. The distinctive work is Japanese keyword research across four scripts (kanji, hiragana, katakana, romaji), whose variants can carry different search volumes and even different intent, and real localization (payment methods, the Tokushoho legal-disclosure page, page-design conventions) rather than machine translation. A separate, similarly-named topic — the 'Japanese keyword hack' — is a site-compromise spam attack, not a keyword strategy. This guide maps the landscape, the keyword-research workflow, and where Japan does and doesn't differ from a Google program.

TL;DR — Treat search-engine share and syndication arrangements in Japan as time-sensitive inputs, not permanent assumptions. The durable Japan-specific work is (1) keyword research across kanji / hiragana / katakana / romaji, where variants carry different volumes and sometimes different intent, and (2) genuine localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. (payment, legal disclosures, page conventions), not translation. The “Japanese keyword hack” is a site-compromise attack, covered as an aside. As a For market-share claims, cite the measurement source and date and avoid assigning a cause the data does not establish.

Evidence for this claim A Japanese-market site should use locale-specific URLs and content intended for Japanese users rather than automatic translation or redirects alone. Scope: Google's current international site guidance; no search-engine market-share claim. Confidence: high · Verified: Google Search Central: Managing multi-regional sites Evidence for this claim Search demand should be researched in Japanese and evaluated by geography; translated English keyword lists are not evidence of local demand. Scope: Google Trends geographic comparison and normalization limits. Confidence: high · Verified: Google Trends Help: FAQ about data

Japan’s search landscape: Google, Yahoo! Japan, and the deal that ties them

The single most load-bearing fact for Japan SEOJapan SEO is the practice of optimizing sites to rank in Japan — a market where Google leads and Yahoo! Japan has run on Google's search technology since 2010. The distinctive work is Japanese-language keyword research across kanji, hiragana, katakana, and romaji, plus genuine localization rather than translation. is that Yahoo! Japan runs on Google’s search technology. This is not folklore — it’s documented from several independent angles.

The 2010 deal itself: contemporaneous tech press reported that “Yahoo search will be powered by Google in the future” and that “users of the service will be served both paid and algorithmic search results generated by Google technology” (TechCrunch, July 27, 2010). Google’s own announcement was published the same day on the Google Japan Blog, authored by Daniel Alegre, then Google’s VP for Asia Pacific and Japan (Google Japan Blog, July 27, 2010) — it’s in Japanese, so I’m paraphrasing rather than quoting it in English: it confirms Google had previously supplied search technology to Yahoo! Japan from 2001 to 2004, and that Yahoo! Japan’s auction, shopping, and Chiebukuro (Q&A) content would feed into Google’s Japanese search indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.. On the record from Yahoo! Japan’s side, its then-CEO explained the choice of Google over Microsoft plainly: “We had many discussions with Yahoo Inc. and in the end, they recognized that this was the right strategy for us in Japan” (Masahiro Inoue, quoted in Fortune, July 27, 2010).

Is it still true? Yes — and here’s the part I like, because it’s a government document rather than a blog post. In 2024 the Japan Fair Trade Commission approved a commitment plan from Google that describes Google having “restricted the provision of technologies for search engines and search advertising to Yahoo” from September 2, 2015 through October 31, 2022 (JFTC, April 22, 2024). The same filing pins the original Google Services Agreement to July 27, 2010 (matching the press date exactly) and an amendment to November 1, 2014. So we have official, dated proof the arrangement was still operative into late 2022 — and the remedy actually preserves Yahoo/LINE Yahoo’s ongoing access to that technology. Read the JFTC action carefully, though: it’s not “Google was punished for powering Yahoo! Japan.” It’s the opposite direction — Google was foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. to have limited how much of that shared technology Yahoo could use to compete in mobile search-ad syndication, and the filing explicitly notes approval “does not mean that Google LLC’s conduct violated the Act.” Even as recently as 2025, US Department of Justice lawyers cited the 2010 Yahoo! Japan arrangement in Google’s US antitrust remedies case as an example of Google having voluntarily shared data before — with the useful precision, per Bloomberg Law’s reporting, that it applied only to Google’s Japanese-language index, not its global index.

There’s a more current — and more directly useful — answer to “is the deal still active” than the JFTC filing, too. At LINE Yahoo’s FY2023 full-year earnings briefing in May 2024, the company confirmed it had extended its commercial search- technology supply contract with Google by two years. The original contract was due to expire at the end of March 2025; LINE Yahoo had reportedly been evaluating a switch to Naver’s search technology — Naver co-owns LY Corporation’s parent via the SoftBank/Naver joint venture described above — as the contract wound down, but shelved that plan because it couldn’t resolve data-security and personal-information-handling concerns. The result, per contemporaneous Japanese business-press coverage citing Nikkei: “Yahoo! JAPANの検索サービスは、少なくとも2027年3月末まではグーグルから技術供与される” (“Yahoo! JAPAN’s search service will continue to receive technology from Google through at least the end of March 2027”) (Web担当者Forum, May 17, 2024, citing 日本経済新聞/Nikkei). As of this pass (mid-2026) I found no newer reporting of a further renewal, change, or termination — the March 2027 floor is still the most current commercial-contract fact available. (This is a separate data point from the JFTC filing above: the JFTC filing documents a restriction period Google was found to have imposed within an otherwise-ongoing relationship; this earnings disclosure documents the underlying commercial contract’s term. Both are true and they reinforce the same conclusion from different angles.)

A few clarifications that matter for accuracy:

  • This is not the US Yahoo. yahoo.com in the US runs on Bing. Yahoo! Japan is a separate corporate lineage, today a brand operated by LY Corporation (renamed from Z Holdings in October 2023, itself renamed from Yahoo! Japan Corporation in 2021). LY Corporation is majority-owned via A Holdings, a 50/50 joint venture between SoftBank and Naver Corporation — the same Naver behind Korea’s NaverNaver SEO is optimizing for Naver, South Korea's dominant portal-style search engine. Naver favors content published on its own properties (Naver Blog, Cafe, Knowledge iN) and ranks it with its own C-Rank and D.I.A. systems, so the work is as much about getting inside the ecosystem as it is about a standalone website.. That’s a genuinely odd connective-tissue fact: the company running Yahoo! Japan is half-owned by the parent of Korea’s dominant search portal.
  • It was a hybrid, not a pure mirror. Google generates the core web results; Yahoo! Japan wraps them in its own portal shell with its own properties (News, Chiebukuro, Shopping) layered in. And reportedly, LINE’s in-app search — LINE being the messaging app most of Japan uses — was switched to Yahoo! Japan Search after the merger (industry-sourced, not first-party-confirmed). If accurate, all three of Japan’s dominant consumer search surfaces resolve to the same Google-powered results.

Current market share (dated — and Bing is the surprise)

Per StatCounter’s June 2026 snapshot for Japan: Google 59.04%, Bing 33.1%, Yahoo! 6.23%, DuckDuckGo 0.72%, Yandex 0.33%, CocCoc 0.31% (StatCounter Global Stats). Two things to flag honestly here. First, the historical reversal: in 2010, per Fortune, Yahoo! Japan alone held ~57% of Japan’s search queries and Google ~38% — by 2026 those roles have almost completely flipped, consistent with users increasingly reaching Google directly rather than through the Yahoo! Japan wrapper. Second, Bing at roughly a third of the market is genuinely surprising and much higher than the ~5-10% Bing share Japan was historically reported at. It’s real in StatCounter’s page-view-weighted data, but I’d treat the size of the shift as noteworthy and the cause as speculation — StatCounter doesn’t publish a causal breakdown, and its methodology skews with device/browser defaults. Plausibly it reflects Windows/Edge default-browser behavior post-Copilot, but I’m not going to assert that as fact. And Yahoo! Japan remaining at ~6% of search while still being the #2 site in Japan by traffic (Similarweb, May 2026) captures the whole story: it’s a giant portal, a small standalone search engine.

The practical upshot: your Japan organic strategy is a Google strategy. There’s no separate Yahoo! Japan organic-ranking submission process — no Yahoo!-specific webmaster-guidelines portal exists, because there’s no separate index to submit to. Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. and general Google technical SEOTechnical SEO is the practice of making a site easy for search engines to crawl, render, index, and (now) be eligible for AI answers. It's the foundation that lets your content and links rank — not a ranking trick of its own. cover it.

Japanese keyword research: kanji, hiragana, katakana, romaji

This is where Japan SEO stops looking like Google SEO and starts requiring market-specific work. Japanese has four ways of renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. words, and a single concept can legitimately be searched in more than one of them:

  • Kanji (漢字) — logographic characters borrowed from Chinese. Skews formal/professional; common for established native concepts.
  • Hiragana (ひらがな) — a phonetic syllabary for native words and grammar. Often softer/more informal.
  • Katakana (カタカナ) — a phonetic syllabary for loanwords, foreign brand names, and tech terms. If your brand has an English name, Japanese searchers will likely type it in katakana.
  • Rōmaji — Latin-alphabet transliteration. The smallest slice, but real — notably for IT/tech queries and brand names without an established katakana renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM.. (No reliable quantified share of romaji queries exists, so I’ll leave it qualitative rather than invent a number.)

There’s also a genuine tokenizationA token is the smallest unit of text (or image/audio/video) an LLM processes — roughly 4 characters, or about ¾ of an English word. A context window is the maximum number of tokens (input plus output) a model can hold at once, like its short-term memory. wrinkle underneath this: Japanese doesn’t use spaces between words, so search engines rely on dictionary-based morphological segmenters rather than splitting on whitespace. That’s part of why “exact match” keyword thinking translates poorly to Japanese — the engine is segmenting your content and the query, not matching space-delimited strings.

Why the same concept has different volumes by script

The variants are separate query stringsThe `?key=value` data tacked onto the end of a URL after a question mark — used for tracking, sessions, filtering, sorting, and search — and one of the biggest sources of duplicate URLs and wasted crawling in SEO., and keyword tools (and Google itself) treat them that way. Volumes — and sometimes intent — differ. Three examples that make the point:

  • Coffee shop — the lead example, because the script tracks a real semantic distinction, not just spelling. カフェ (kafe, katakana) means a Western-style cafe; 喫茶店 (kissaten, kanji) means a traditional Japanese coffee house; コーヒーショップ (kōhī shoppu, katakana) is the literal “coffee shop.” Optimizing for one and ignoring the others can miss a genuinely different searcher.
  • Mobile phone — 携帯電話 (kanji, formal/full form), 携帯 (kanji, abbreviated), and ケータイ (katakana rendering of the abbreviation) can each pull different volumes for what a Western SEO would call “one keyword.”
  • Sushi — a single concept with 3+ valid renderings: すし (hiragana), スシ (katakana), 寿司 (kanji, most common). It shows the range can exceed the basic three-script framing.

An observed pattern worth stating carefully — as a pattern, not a rule: katakana tends to correlate with commercial intent for Western/international products, hiragana skews informational/native, and kanji skews formal/professional/B2B. This is industry consensus rather than a single authoritative source, so treat it as a useful heuristic, not law.

The practical workflow

  1. Start from the concept, not the string. List every plausible kanji, hiragana, katakana, and (where relevant) romaji rendering — for brand/foreign terms, generate multiple katakana transliterations, since more than one can exist.
  2. Pull volume for each variant separately in your keyword tool (Ahrefs Keywords Explorer, etc.) rather than assuming they consolidate.
  3. Compare not just volume but the SERP for each — if the ranking pages differ, the intent differs, and you may need distinct content.
  4. Have a native Japanese speaker sanity-check the shortlist. Tools tell you volume; only a native reader reliably catches which variant sounds natural, spammy, or subtly wrong for your audience.

Localization vs. translation for Japan

Japan is the standard textbook case of “translation is necessary but not sufficient.” A linguistically-correct machine translation can still read as unnatural, and — worse — be non-compliant or untrustworthy. Some concrete localizationLocalization is adapting content for a specific target market — not just translating the words, but adjusting currency, formats, idioms, cultural references, local search terms, and trust signals so the experience feels native. work that translation alone never surfaces:

  • The Tokushoho disclosure page. Japan’s Act on Specified Commercial Transactions (特定商取引法) governs how e-commerce sites must disclose to Japanese consumers (Japanese Law Translation, the government’s official English text). In practice, Japanese e-commerce sites publish a dedicated disclosure page (conventionally titled 特定商取引法に基づく表記) linked from the footer, covering the business operator’s identity, address, and return policy. Precise wording: this is a widely-followed compliance pattern built on the Act’s advertisement-disclosure requirements and the associated ministerial ordinance — not a single statutory sentence that literally says “publish one page.” But its absence is a well-known red flag to Japanese shoppers, so it’s a real trust signal regardless of how you characterize the statute.
  • Payment expectations. Convenience-store (konbini) payment and bank transfer are common expectations, alongside cards — a market convention worth accommodating, though I’d present it as widely-observed rather than pinned to one citation.
  • Design conventions. Japanese homepages tend to be denser and more text-heavy than Western minimalism; that’s a real UX expectation, not a mistake to “fix.”

On the pure-SEO side, Google’s guidance here is generic international-SEO guidance — Google doesn’t publish Japan-specific ranking docs, which is itself an accurate framing point: Japan falls under the same international/multilingual/hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. framework as every other market. The one directly-relevant rule for localized sites: “Localized versions of a page are only considered duplicates if the main content of the page remains untranslated” (Google Search Central) — i.e. translating only your navigation/footer while leaving the body in English can get the page treated as a duplicate. Use hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. to map your ja/ja-JP variants like any other international site.

TIP Generate the locale plumbing after the Japanese pages are localized

The generator validates hreflang codes and emits reciprocal annotations. It does not research Japanese queries, review script choice, or determine whether separate ja and ja-JP URLs are justified.

Once the localized URL set is final, enter it in my Hreflang Generator to produce consistent head tags, headers, or sitemap annotations. Hreflang Generator Free

  1. Have a native reviewer approve the page and its intended audience.
  2. Use ja for Japanese generally, adding ja-JP only when a distinct Japan-specific version is warranted.
  3. Deploy reciprocal annotations and verify the live canonical URL set.

Japanese search behavior

Two habits shape Japanese SERPs. First, it’s a mobile-first, app-centric market — LINE dominates messaging, and portal apps are heavily used. (Mobile-first indexingGoogle's practice of using the mobile version of a page's content — crawled by Googlebot smartphone — for indexing and ranking. It is not a separate index and not a ranking boost. itself is historical/complete now: Google announced it November 4, 2016, began transitioning sites from late 2017, and rolled out broadly from March 2018; mobile search overtook desktop in several markets including Japan around 2015, cited as general rationale — but I’ve seen no evidence Japan was a named test market, so I won’t overstate it.) Second, formality and politeness register show up in query phrasing, which ties back to the script-choice patterns above.

Aside: the “Japanese keyword hack” — a spam attack, not a strategy

Because of the name, some people arrive at “Japanese keyword” content thinking it’s a gray-hat tactic. It isn’t. Google’s own web.dev documentation is blunt: “The Japanese keyword hack typically creates new pages with autogenerated Japanese text on your site in randomly generated directory names” (Google, web.dev). Those pages are “monetized using affiliate links to stores selling fake brand merchandise and then shown in Google Search.” A common tell: “If you’ve received a notification that someone you don’t know has verified your site in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results., there’s a strong possibility that your site has been hacked” (same source).

The important prevention point: cleanup alone isn’t enough. Per the same web.dev article, 20% of hacked sites are hacked again within one day (web.dev) — so you have to close the entry point (usually an outdated CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms./plugin), rotate passwords, and enable 2FA, not just delete the spam pages. This has been a long-running pattern; the Google Search Central Help Community has threads reporting it across at least a decade. Full step-by-step in the Playbook lens below.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.