Guide Japan SEO

TL;DR — Search-engine usage and partnerships in Japan peut modifier, so vérifier current market données avant prioritizing platforms. The durable difference is the language: the même word peut be written in several scripts (kanji, hiragana, katakana, or the Latin alphabet), and chaque version peut be a separate keyword. And vous besoin réel localization, pas a rapide translation.

Japan isn’t a “non-Google” market

Si you’ve lire our market-specific SEO hub, vous know que some countries run on leur propre engines — China on Baidu, Russia on Yandex, South Korea on Naver. It’s natural to assume Japan belongs on que liste parce que of Yahoo! Japan. It doesn’t.

Here’s the clé fact: Yahoo! Japan’s organic résultats de recherche are generated by Google’s technology, and have been since a 2010 agreement. Yahoo! Japan is a huge, popular portal — news, shopping, auctions, a Q&A service — but its réel web résultats de recherche come from Google sous the hood. So quand someone indique vous “vous besoin to do Yahoo! Japan SEO separately,” que advice is out of date. Si vous rank on Google in Japan, vous généralement rank on Yahoo! Japan aussi.

So ce que is différent à propos de Japan?

Two choses, and neither is a separate algorithm:

1. The Japanese writing system. Japanese mixes four façons of writing:

• Kanji (漢字) — characters borrowed from Chinese (e.g. 寿司 pour sushi).
• Hiragana (ひらがな) — a phonetic script pour native words and grammar.
• Katakana (カタカナ) — a phonetic script mostly pour foreign/loan words and brand noms (e.g. コーヒー pour “coffee”).
• Rōmaji — the Latin alphabet, utilisé pour some brand noms and tech terms.

The même idea peut be typed in plus que un of ces, and ceux versions aren’t toujours interchangeable. “Coffee shop” peut be カフェ (a Western-style cafe) or 喫茶店 (a traditional Japanese coffee house) — différent scripts, genuinely différent meaning. That’s pourquoi Japanese keyword research signifie checking chaque variant separately, pas picking un and moving on.

2. Localization over translation. Machine-translating votre English page into Japanese usually isn’t suffisant — and souvent reads as unnatural. Réel localization adapts payment méthodes (Japanese shoppers expect options comme convenience-store payment), page design (Japanese sites tend to be denser and plus text-heavy que Western ones), and legal/trust details. There’s même a spécifique legal disclosure page (the “Tokushoho” page) que e-commerce sites selling to Japanese consumers are attendu to publish. Our translation vs. localization guide goes deeper on que distinction.

Un chose to pas obtenir confused by

Si vous search “Japanese keyword hack,” you’ll trouver a lot of pages — but that’s a hacking topic, pas a keyword-research un. It’s quand attackers break into a site (souvent an outdated CMS) and inject spammy Japanese pages. Si vous trouvé que term parce que weird Japanese pages showed up on votre propre site, jump to the Avancé tab — there’s a section on cleaning it up.

Vouloir the complet version — the 2010 deal and pourquoi it encore holds, the four-script keyword workflow, the current market-share numbers (Bing is surprisingly grand in Japan now), and the localization checklist? Switch to the Avancé tab.

TL;DR — Treat search-engine share and syndication arrangements in Japan as time-sensitive inputs, pas permanent assumptions. The durable Japan-specific fonctionner is (1) keyword research à travers kanji / hiragana / katakana / romaji, où variants carry différent volumes and parfois différent intent, and (2) genuine localization (payment, legal disclosures, page conventions), pas translation. The “Japanese keyword hack” is a site-compromise attack, covered as an aside. As a Pour market-share claims, cite the measurement source and date and éviter assigning a causer the données ne fait pas establish.

Japan’s search landscape: Google, Yahoo! Japan, and the deal que ties les

The unique la plupart load-bearing fact pour Japan SEO is que Yahoo! Japan runs on Google’s search technology. Ce n’est pas folklore — it’s documented from several independent angles.

The 2010 deal itself: contemporaneous tech press reported que “Yahoo search will be powered by Google in the future” and que “utilisateurs of the service va be served les deux paid and algorithmic résultats de recherche generated by Google technology” (TechCrunch, July 27, 2010). Google’s propre announcement was publié the même day on the Google Japan Blog, authored by Daniel Alegre, alors Google’s VP pour Asia Pacific and Japan (Google Japan Blog, July 27, 2010) — it’s in Japanese, so I’m paraphrasing plutôt que quoting it in English: it confirms Google had previously supplied search technology to Yahoo! Japan from 2001 to 2004, and que Yahoo! Japan’s auction, shopping, and Chiebukuro (Q&A) content voudrait feed into Google’s Japanese search index. On the record from Yahoo! Japan’s side, its then-CEO explained the choice of Google over Microsoft plainly: “We had nombreux discussions with Yahoo Inc. and in the fin, ils recognized que ce was the correct strategy pour us in Japan” (Masahiro Inoue, quoted in Fortune, July 27, 2010).

Is it still vrai? Yes — and here’s the partie I comme, parce que it’s a government document plutôt que a blog post. In 2024 the Japan Fair Trade Commission approved a commitment plan from Google que describes Google having “restricted the provision of technologies pour moteur de recherches and search advertising to Yahoo” from September 2, 2015 via October 31, 2022 (JFTC, April 22, 2024). The même 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 encore operative into late 2022 — and the remedy en réalité preserves Yahoo/LINE Yahoo’s ongoing accès to que technology. Lire the JFTC action carefully, though: it’s pas “Google was punished pour powering Yahoo! Japan.” It’s the opposite direction — Google was trouvé to have limited how beaucoup of que shared technology Yahoo pourrait utiliser to compete in mobile search-ad syndication, and the filing explicitly notes approval “ne fait pas mean que Google LLC’s conduct violated the Act.” Même as recently as 2025, US Department of Justice lawyers cited the 2010 Yahoo! Japan arrangement in Google’s US antitrust remedies cas as an exemple of Google having voluntarily shared données avant — with the utile precision, per Bloomberg Law’s reporting, que it applied seulement to Google’s Japanese-language index, pas its global index.

There’s a plus current — and plus directement utile — réponse to “is the deal encore active” que the JFTC filing, aussi. 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 années. The original contract was due to expire at the fin 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 décrit ci-dessus — as the contract wound bas, but shelved que plan parce que it couldn’t resolve data-security and personal-information-handling concerns. Le résultat, per contemporaneous Japanese business-press coverage citing Nikkei: “Yahoo! JAPANの検索サービスは、少なくとも2027年3月末まではグーグルから技術供与される” (“Yahoo! JAPAN’s search service va continuer to recevoir technology from Google via au moins the fin of March 2027”) (Web担当者Forum, May 17, 2024, citing 日本経済新聞/Nikkei). As of ce réussir (mid-2026) I trouvé aucun newer reporting of a plus loin renewal, modifier, or termination — the March 2027 floor is encore the la plupart current commercial-contract fact disponible. (Ce is a separate données point from the JFTC filing ci-dessus: the JFTC filing documents a restriction period Google was trouvé to have imposed dans an otherwise-ongoing relationship; ce earnings disclosure documents the underlying commercial contract’s term. Les deux are vrai and ils reinforce the même conclusion from différent angles.)

A few clarifications que matter pour accuracy:

• Ce n’est pas 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 entre SoftBank and Naver Corporation — the même Naver behind Korea’s Naver. 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, pas a pure mirror. Google generates the core web results; Yahoo! Japan wraps les in its propre portal shell with its propre properties (News, Chiebukuro, Shopping) layered in. And reportedly, LINE’s in-app search — LINE being the messaging app la plupart of Japan uses — was switched to Yahoo! Japan Search après the merger (industry-sourced, pas first-party-confirmed). Si accurate, tout three of Japan’s dominant consumer search surfaces resolve to the même Google-powered results.

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

Per StatCounter’s June 2026 snapshot pour Japan: Google 59,04%, Bing 33,1%, Yahoo! 6,23%, DuckDuckGo 0,72%, Yandex 0,33%, CocCoc 0,31% (StatCounter Global Stats). Two choses to flag honestly ici. Premier, the historical reversal: in 2010, per Fortune, Yahoo! Japan alone held ~57% of Japan’s search requêtes and Google ~38% — by 2026 ceux roles have almost complètement flipped, consistent with utilisateurs increasingly reaching Google directement plutôt que via the Yahoo! Japan wrapper. Second, Bing at roughly a third of the market is genuinely surprising and beaucoup plus élevé que the ~5-10% Bing share Japan was historically reported at. It’s réel in StatCounter’s page-view-weighted données, 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/navigateur defaults. Plausibly it reflects Windows/Edge default-browser behavior post-Copilot, but I’m pas going to assert que as fact. And Yahoo! Japan remaining at ~6% of search pendant que encore being the #2 site in Japan by trafic (Similarweb, May 2026) captures the whole story: it’s a giant portal, a petit standalone moteur de recherche.

The practical upshot: votre Japan organic strategy is a Google strategy. There’s aucun separate Yahoo! Japan organic-ranking submission traiter — aucun Yahoo!-spécifique webmaster-guidelines portal exists, parce que there’s aucun separate index to submit to. Recherche Google Console and general Google SEO technique cover it.

Japanese keyword research: kanji, hiragana, katakana, romaji

Ce is où Japan SEO arrête looking comme Google SEO and starts requiring market-specific fonctionner. Japanese has four façons of rendering words, and a unique concept peut legitimately be searched in plus que un of les:

• Kanji (漢字) — logographic characters borrowed from Chinese. Skews formal/professional; courant pour established native concepts.
• Hiragana (ひらがな) — a phonetic syllabary pour native words and grammar. Souvent softer/plus informal.
• Katakana (カタカナ) — a phonetic syllabary pour loanwords, foreign brand noms, and tech terms. Si votre brand has an English nom, Japanese searchers va probable type it in katakana.
• Rōmaji — Latin-alphabet transliteration. The smallest slice, but réel — notably pour IT/tech requêtes and brand noms sans an established katakana rendering. (Aucun reliable quantified share of romaji requêtes exists, so I’ll leave it qualitative plutôt que invent a number.)

There’s aussi a genuine tokenization wrinkle underneath ce: Japanese doesn’t utiliser spaces entre words, so moteur de recherches rely on dictionary-based morphological segmenters plutôt que splitting on whitespace. That’s partie of pourquoi “exact match” keyword thinking translates poorly to Japanese — the engine is segmenting votre content and the requête, pas matching space-delimited strings.

Pourquoi the même concept has différent volumes by script

The variants are separate requête strings, and keyword outils (and Google itself) treat les que façon. Volumes — and parfois intent — differ. Three exemples que faire the point:

• Coffee shop — the lead exemple, parce que the script tracks a real semantic distinction, pas simplement spelling. カフェ (kafe, katakana) signifie a Western-style cafe; 喫茶店 (kissaten, kanji) signifie a traditional Japanese coffee house; コーヒーショップ (kōhī shoppu, katakana) is the literal “coffee shop.” Optimizing pour un and ignoring the others peut miss a genuinely différent searcher.
• Mobile phone — 携帯電話 (kanji, formal/complet formulaire), 携帯 (kanji, abbreviated), and ケータイ (katakana rendering of the abbreviation) peut chaque pull différent volumes pour ce que a Western SEO voudrait appel “one keyword.”
• Sushi — a unique concept with 3+ valid renderings: すし (hiragana), スシ (katakana), 寿司 (kanji, la plupart courant). It montre the range peut exceed the basic three-script framing.

An observed pattern worth stating carefully — as a pattern, pas a rule: katakana tends to correlate with commercial intent pour Western/international products, hiragana skews informational/native, and kanji skews formal/professional/B2B. Ce is industry consensus plutôt que a unique authoritative source, so treat it as a utile heuristic, pas law.

The practical workflow

1. Commencer from the concept, pas the string. Liste every plausible kanji, hiragana, katakana, and (où relevant) romaji rendering — pour brand/foreign terms, generate multiple katakana transliterations, since plus que un peut exist.
2. Pull volume pour chaque variant separately in votre keyword outil (Ahrefs Keywords Explorer, etc.) plutôt que assuming ils consolidate.
3. Compne sont pas simplement volume but the SERP pour chaque — si the ranking pages differ, the intent differs, and vous may besoin distinct content.
4. Have a native Japanese speaker sanity-check the shortlist. Outils tell vous volume; seulement a native reader reliably catches qui variant sounds natural, spammy, or subtly incorrect pour votre audience.

Localization vs. translation pour Japan

Japan is the standard textbook cas of “translation is necessary but pas sufficient.” A linguistically-correct traduction automatique peut encore lire as unnatural, and — worse — be non-compliant or untrustworthy. Some concrete localization fonctionner que translation alone jamais surfaces:

• The Tokushoho disclosure page. Japan’s Act on Specified Commercial Transactions (特定商取引法) governs how e-commerce sites doit disclose to Japanese consumers (Japanese Law Translation, the government’s official English text). En pratique, Japanese e-commerce sites publish a dedicated disclosure page (conventionally titled 特定商取引法に基づく表記) lié from the footer, covering the business operator’s identity, adresse, and retourner policy. Precise wording: ce is a widely-followed compliance pattern construit on the Act’s advertisement-disclosure requirements and the associated ministerial ordinance — pas a unique statutory sentence que literally dit “publish one page.” But its absence is a well-known red flag to Japanese shoppers, so it’s a réel trust signal regardless of how vous characterize the statute.
• Payment expectations. Convenience-store (konbini) payment and bank transfer are courant expectations, alongside cards — a market convention worth accommodating, though I’d présent it as widely-observed plutôt que pinned to un citation.
• Design conventions. Japanese homepages tend to be denser and plus text-heavy que Western minimalism; that’s a réel UX expectation, pas a mistake to “fix.”

On the pure-SEO side, Google’s guidance ici is generic international-SEO guidance — Google doesn’t publish Japan-specific ranking docs, qui is itself an accurate framing point: Japan falls sous the même international/multilingual/hreflang framework as every autre market. The un directly-relevant rule pour localized sites: “Localized versions of une page are seulement considéré duplicates si the principal content of lune page remains untranslated” (Recherche Google Central) — i.e. translating seulement votre navigation/footer pendant que leaving the corps in English peut obtenir lune page treated as a duplicate. Utiliser hreflang to map votre ja/ja-JP variants comme quelconque autre international site.

Japanese search behavior

Two habits shape Japanese SERPs. Premier, it’s a mobile-first, app-centric market — LINE dominates messaging, and portal apps are heavily utilisé. (Indexation mobile-first itself is historical/complet 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 notamment Japan autour 2015, cited as general rationale — but I’ve seen aucun evidence Japan was a named tester market, so I won’t overstate it.) Second, formality and politeness register montrer up in requête phrasing, qui ties back to the script-choice patterns ci-dessus.

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

Parce que of the nom, some personnes arrive at “Japanese keyword” content thinking it’s a gray-hat tactic. It isn’t. Google’s propre web.dev documentation is blunt: “The Japanese keyword hack typically creates nouveau pages with autogenerated Japanese text on votre site in randomly generated directory noms” (Google, web.dev). Ceux pages are “monetized en utilisant affiliate liens to stores selling fake brand merchandise and alors affiché dans la recherche Google.” A courant tell: “Si you’ve reçu a notification que someone vous don’t know has verified votre site dans la recherche Google Console, there’s a strong possibility que votre site has been hacked” (même source).

The important prevention point: cleanup alone isn’t suffisant. Per the même web.dev article, 20% of hacked sites are hacked à nouveau dans un day (web.dev) — so vous have to fermer the entry point (usually an outdated CMS/plugin), rotate passwords, and enable 2FA, pas simplement delete the spam pages. Ce has been a long-running pattern; the Recherche Google Central Aider Community has threads reporting it à travers au moins a decade. Complet step-by-step in the Playbook lens ci-dessous.

AI summary

A condensed prendre on the Avancé version:

• Japan is a Google market, pas a non-Google un. Yahoo! Japan has run on Google’s search/ad technology since the July 27, 2010 deal; the 2024 Japan Fair Trade Commission filing confirms it was operative via Oct. 31, 2022, and it was encore cited in 2025 US antitrust litigation. Separately, LINE Yahoo’s propre May 2024 earnings disclosure confirmed a 2-année contract extension keeping Google-powered search running via au moins March 2027, après LINE Yahoo shelved a considéré switch to Naver’s search technology over unresolved données- security concerns. La plupart “Yahoo! Japan SEO” is simplement Google SEO — aucun separate organic submission traiter exists.
• Pas the US Yahoo. US yahoo.com runs on Bing; Yahoo! Japan is a separate entity, today a brand of LY Corporation (half-owned via a SoftBank/Naver JV).
• Market share (StatCounter, June 2026): Google ~59%, Bing ~33% (surprisingly élevé — report the number, pas an unverified causer), Yahoo! ~6%. A near-reversal from 2010 (Yahoo! ~57%, Google ~38%).
• Keyword research spans four scripts: kanji, hiragana, katakana, romaji. Variants are separate requête strings with différent volumes and parfois différent intent (カフェ = Western cafe vs. 喫茶店 = traditional coffee house). Katakana ≈ commercial / loanwords / brand noms; hiragana ≈ informational; kanji ≈ formal (pattern, pas rule). Japanese has aucun word spaces, so engines segment morphologically.
• Localization > translation: the Tokushoho disclosure page (compliance pattern, pas a literal statutory “page” requirement), konbini/bank-transfer payment, denser page design. Google’s guidance is generic international SEO — Japan has aucun special ranking docs; utiliser hreflang normally.
• “Japanese keyword hack” = a site-compromise spam attack, pas a tactic. web.dev documents it; 20% of hacked sites are re-hacked dans a day, so fix the entry point.

Documentation officielle

Primary-source documentation relevant to Japan SEO. Google is the operative engine (notamment pour Yahoo! Japan’s organic results), so Google’s international/multilingual docs are the closest chose to “official Japan guidance” — Google publishes aucun Japan-specific ranking documentation.

Google — international / multilingual

• Managing multi-regional and multilingual sites — the framework Japan falls sous (là is aucun Japan-specific version).
• Tell Google à propos de localized versions of votre page — the localized-versions / duplicate rule pour translated pages.
• How Recherche Google handles multilingual searches (Sept. 2023) — how Google auto-detects qui language(s) to serve. Background seulement; confirmer the article corps contre the live page — automated récupère renvoyé seulement the blog index.

Google — the “Japanese keyword hack” (web.dev)

• Fix the Japanese keyword hack — Google’s propre detection-and-cleanup guide pour the spam attack.

Japanese government (localization/compliance)

• Act on Specified Commercial Transactions (Tokushoho) — official English translation — the legal basis pour e-commerce disclosure requirements in Japan.

Regulatory (the Google/Yahoo! Japan arrangement)

• JFTC — Approval of the Commitment Plan submitted by Google LLC (April 22, 2024) — the dated, quasi-official confirmation the search-technology arrangement was operative via Oct. 2022.

Yahoo! Japan

• Aucun standalone Yahoo!-Japan organic-SEO / webmaster-guidelines portal exists — parce que organic ranking is Google’s algorithm. Portal properties (Shopping, Auctions) have leur propre merchant onboarding, but that’s e-commerce feed integration, pas organic-ranking SEO.

Quotes from the source

On-the-record statements. Chaque lien deep-links to the quoted passage on the source page.

The 2010 Google / Yahoo! Japan deal

• “Yahoo search will be powered by Google in the future” and “utilisateurs of the service va be served les deux paid and algorithmic résultats de recherche generated by Google technology.” — TechCrunch, July 27, 2010. Jump to quote
• “We had nombreux discussions with Yahoo Inc. and in the fin, ils recognized que ce was the correct strategy pour us in Japan.” — Masahiro Inoue, President/CEO, Yahoo! Japan Corporation, quoted in Fortune, July 27, 2010. Jump to quote

(Google’s propre July 27, 2010 announcement — Daniel Alegre on the Google Japan Blog — is Japanese-language seulement, so it’s paraphrased in the Avancé tab plutôt que quoted as English; ne faites pas treat quelconque English rendering of it as a verbatim Google quote.)

The arrangement’s persistence — JFTC

• Google LLC “restricted the provision of technologies pour moteur de recherches and search advertising to Yahoo” from September 2, 2015 via October 31, 2022; and approval of the commitment plan “does not mean that Google LLC’s conduct violated the Act.” — Japan Fair Trade Commission, April 22, 2024. Jump to quote

The arrangement’s persistence — the commercial contract (2024 extension)

• “Yahoo! JAPANの検索サービスは、少なくとも2027年3月末まではグーグルから技術供与される” (“Yahoo! JAPAN’s search service va continuer to recevoir technology from Google via au moins the fin of March 2027”) — Web担当者Forum, citing Nikkei, May 17, 2024. Jump to quote

Google on localized-page duplication

• “Localized versions of une page are seulement considéré duplicates si the principal content of lune page remains untranslated.” — Recherche Google Central. Jump to quote

The “Japanese keyword hack” (web.dev)

• “The Japanese keyword hack typically creates nouveau pages with autogenerated Japanese text on votre site in randomly generated directory noms.” — Google, web.dev. Jump to quote
• “Ces pages are monetized en utilisant affiliate liens to stores selling fake brand merchandise and alors affiché dans la recherche Google.” — même source. Jump to quote
• “Si you’ve reçu a notification que someone vous don’t know has verified votre site dans la recherche Google Console, there’s a strong possibility que votre site has been hacked.” — même source. Jump to quote

How devrait vous approach SEO pour Japan?

Réponse a couple of questions and you’ll land on a recommendation. Every branch comes from the landscape and mechanics ci-dessus.

SOP: Japanese multi-script keyword research

A repeatable procedure pour building a Japanese keyword map que doesn’t miss script variants. Run it per topic cluster.

1. Liste the seed concepts in English pour the cluster you’re targeting.
2. Generate every script rendering pour chaque concept: the kanji formulaire, the hiragana formulaire, the katakana formulaire, and (pour brand/foreign/tech terms) the romaji formulaire. Pour foreign brand noms, generate multiple katakana transliterations — plus que un spelling peut circulate.
3. Have a native Japanese speaker prune obviously-wrong or unnatural renderings avant vous spend outil credits — but garder quelconque variant that’s plausibly a réel requête même si it “feels” secondary.
4. Pull search volume pour chaque variant separately in votre keyword outil (Ahrefs Keywords Explorer, etc.). Ne faites pas assume the outil consolidates variants.
5. Eyeball the SERP pour chaque variant. Si two variants retourner clearly différent ranking pages, ils have différent intent — remarque les as separate targets, pas duplicates (the カフェ vs. 喫茶店 cas).
6. Tag chaque variant by probable intent en utilisant the script heuristic (katakana ≈ commercial/loanword, hiragana ≈ informational, kanji ≈ formal) — as a hypothesis to validate contre the SERP, pas a fixed rule.
7. Map variants to pages. Same-intent variants peut share une page (as natural on-page variations); different-intent variants may besoin leur propre pages.
8. Record volumes with a date and re-pull periodically — Japanese script-variant volumes shift, and vous don’t vouloir to reuse stale numbers.

Japan SEO Mythes et erreurs à éviter

The claims que come up la plupart souvent — several are widely repeated and incorrect:

• “Vous devez submit votre site to Yahoo! Japan separately, comme the old Yahoo Directory.” Aucun. Yahoo! Japan’s organic results have come from Google’s algorithm since the July 27, 2010 deal (reconfirmed operative via Oct. 2022 by the 2024 JFTC filing, and sous a commercial contract LINE Yahoo extended via au moins March 2027). (Do-instead: run un Google program — Search Console, standard SEO technique — and you’ve covered Yahoo! Japan’s organic results. Portal fonctionnalités comme Shopping have separate merchant onboarding, but that’s pas organic-ranking SEO.)
• “Yahoo! Japan is the same as US Yahoo, so it uses Bing.” Aucun. US yahoo.com runs on Bing; Yahoo! Japan is a separate entity (now a brand of LY Corporation) running on Google. (Do-instead: don’t appliquer US-Yahoo/Bing assumptions to Japan — treat Japan organic as Google.)
• “Kanji, hiragana, and katakana versions of a keyword are simplement stylistic variants — pick un.” Aucun — they’re separate requête strings with différent volumes and parfois différent meaning (カフェ = Western cafe vs. 喫茶店 = traditional coffee house). (Do-instead: research chaque variant separately and comparer SERPs avant deciding qui to target or si vous besoin distinct pages.)
• “A good translation is the same as localization.” Aucun — translation converts language; localization adapts payment méthodes, legal disclosures (the Tokushoho page), design conventions, and trust signals. (Do-instead: localize with native speakers and cover the compliance/trust couche; a literal translation peut be grammatically correct yet non-compliant and off-putting.)
• “The Japanese keyword hack is a legitimate/gray-hat SEO tactic.” Aucun — it’s a site-compromise spam attack documented by Google’s propre web.dev. (Do-instead: si vous voir auto-generated Japanese spam pages on votre site, treat it as a security incident — voir the Playbook.)
• “Romaji is how most Japanese people search.” Aucun — native-script (kanji / hiragana / katakana) requêtes dominate; romaji is a minority behavior, mainly pour IT/tech terms and brand noms sans a settled katakana formulaire. (Do-instead: cover romaji où it’s genuinely relevant, but don’t construire votre keyword map autour it, and don’t invent a romaji-share percentage.)
• “Bing is negligible in Japan, so ignore it.” Stale. StatCounter’s June 2026 données puts Bing autour a third of Japan’s search market. (Do-instead: since Japan organic is a Google program anyway, ce mostly doesn’t modifier votre SEO fonctionner — but don’t repeat the old “~5% Bing” figure, and treat the causer of Bing’s rise as unconfirmed.)

Incident playbook: the “Japanese keyword hack”

Linear runbook pour quand auto-generated Japanese spam pages apparaître on votre site (a site compromise, pas an SEO problem). Follow in order.

1. Confirmer the symptom. Run a site:yourdomain.com search and regarder pour pages of Japanese text in randomly-named directories vous didn’t créer. Vérifier Recherche Google Console’s Security Problèmes and Indexation reports.
2. Vérifier pour rogue GSC verifications. In Search Console, examiner verified owners. An unknown owner is a strong signal le site was hacked (per web.dev) — supprimer quelconque vous don’t recognize.
3. Prendre a backup / snapshot of the current (compromised) state avant vous modifier anything, pour forensics.
4. Trouver and fermer the entry point. Usually an outdated CMS core, theme, or plugin, or a compromised credential. Mettre à jour everything; examiner recently-modified fichiers and quelconque unfamiliar admin utilisateurs.
5. Supprimer the injected content. Delete the spam pages/directories and quelconque injected redirections, cloaking logic, or malicious scripts. Confirmer nothing legitimate dépend on les.
6. Rotate tout credentials and enable 2FA. CMS admins, hosting/SFTP, database. Ce is the step personnes skip — and 20% of hacked sites are re-hacked dans un day per web.dev, almost toujours parce que the door was left ouvrir.
7. Requête a examiner in Search Console si a manual action / security problème was flagged, une fois le site is clean.
8. Monitor site: results and GSC pour recurrence over the suivant weeks, and garder the CMS/plugins patched going forward.

Multi-script keyword exemples

Concrete avant/après cas showing pourquoi single-script keyword research misses trafic and intent in Japan.

1. Coffee shop — script tracks meaning, pas simplement spelling

• Before: Target seulement カフェ (kafe), assuming it signifie “coffee shop.”
• After: Split into カフェ (Western-style cafe), 喫茶店 (kissaten, traditional Japanese coffee house), and コーヒーショップ (literal “coffee shop”). The 喫茶店 searcher veut something genuinely différent — a distinct page/section peut win a visitor カフェ optimization voudrait jamais reach.

2. Mobile phone — abbreviation and script split the volume

• Before: Target the complet formal kanji 携帯電話 seulement.
• After: Aussi cover 携帯 (abbreviated kanji) and ケータイ (katakana of the abbreviation). Chaque pulls its propre volume pour ce que semble comme “one keyword” in English.

3. Sushi — a unique concept, 3+ valid renderings

• Before: Optimize pour 寿司 (kanji) alone.
• After: Remarque すし (hiragana) and スシ (katakana) as réel requête variants aussi. Même où ils share intent, mapping les montre the vrai topical footprint and peut inform natural on-page usage.

4. A foreign brand nom entering Japan

• Before: Assume searchers type the brand in its English (romaji) formulaire.
• After: Research the katakana transliteration(s) of the brand — that’s how la plupart Japanese searchers va type a foreign nom — and vérifier si plus que un katakana spelling is in circulation, so vous don’t cede the dominant variant.

AI prompts pour Japan SEO

Ready-to-copy prompts. Toujours have a native Japanese speaker vérifier the output — AI is a drafting aid pour script variants, pas a substitute pour native examiner.

Generate script variants pour keyword research

I'm doing Japanese keyword research. For each English concept below, list its
common Japanese renderings in: (1) kanji, (2) hiragana, (3) katakana, and
(4) romaji. For loanwords/brand names, include multiple katakana spellings if more
than one is commonly used. For each variant, note whether it likely signals
commercial, informational, or formal/professional intent, and flag any variants that
carry a genuinely different meaning (not just a spelling difference).

Concepts: [list your concepts]

Sanity-check localization vs. literal translation

Here is an English marketing sentence and its proposed Japanese translation. Tell me
whether the Japanese reads as natural, native-quality copy or as a literal/machine
translation, and rewrite it to sound natural to a Japanese consumer while preserving
meaning. Flag any cultural, formality-register, or trust issues.

English: [sentence]
Proposed Japanese: [translation]

Draft a Tokushoho page checklist

I run an e-commerce site selling to Japanese consumers. List the fields a standard
Japanese "特定商取引法に基づく表記" (Act on Specified Commercial Transactions)
disclosure page conventionally includes. Present it as a checklist. Note that this is
general information, not legal advice, and that I should confirm requirements with a
Japan-qualified professional.

Audit a suspected Japanese keyword hack

My site may have the "Japanese keyword hack." Give me a step-by-step detection and
cleanup checklist: how to confirm it via site: search and Google Search Console, how
to find and close the likely entry point (outdated CMS/plugins, rogue GSC owners),
how to remove injected pages, and the prevention steps (credential rotation, 2FA,
updates) that stop re-infection.

Japan SEO setup checklist

The Japan-specific fonctionner, in order — la plupart of it keyword-research and localization, pas a separate engine:

• Confirmer you’re treating Japan organic as a Google program (Yahoo! Japan runs on Google — aucun separate organic tooling or submission).
• Vérifier le site in Recherche Google Console; run standard Google SEO technique.
• Map language/region with hreflang (ja / ja-JP) comme quelconque international site.
• Garantir the principal content is entièrement translated/localized, pas simplement the template — a corps left in English peut be treated as a duplicate.
• Do multi-script keyword research: kanji, hiragana, katakana, and (où relevant) romaji, chaque variant pulled separately.
• Pour foreign/brand terms, research the katakana rendering(s) specifically.
• Comparer SERPs per variant to catch different-intent variants (e.g. カフェ vs. 喫茶店) and map les to the correct pages.
• Have a native Japanese speaker examiner copy and the keyword shortlist.
• Pour e-commerce, publish the Tokushoho disclosure page (特定商取引法に基づく表記) and offer attendu payment méthodes (konbini, bank transfer).
• Don’t “fix” dense Japanese page conventions into Western minimalism si the market expects les.
• Ignore the temptation to construire a separate Yahoo! Japan program or a romaji-first keyword map.
• Monitor site: results and GSC pour quelconque sign of the Japanese keyword hack spam injection.

Ressources utiles

My connexe writing

• The Beginner’s Guide to SEO technique — the technical foundation a Japan program encore sits on, since Japan organic is a Google program.
• How to Do Keyword Research pour le SEO — the general workflow the multi-script Japanese traiter extends. (Ce is Japan’s premier dedicated piece from me — I don’t have prior Japan/Yahoo-Japan-specific writing to point vous to.)

From autour the industry

• Yahoo Japan To Utiliser Recherche Google (And Pas Bing) In The Future (TechCrunch) — the contemporaneous account of the 2010 deal and the NetRatings requête données behind the combined-share estimate.
• Yahoo Japan chooses Google pour search and ads (Fortune) — Masahiro Inoue’s on-record quotes and the 2010 market-share figures (Yahoo! Japan ~57%, Google ~38%).
• Approval of the Commitment Plan submitted by Google LLC (Japan Fair Trade Commission) — the dated regulatory confirmation the arrangement was operative via Oct. 2022.
• Yahoo! JAPANが検索サービス乗り換えを断念、グーグルとの提携を2年延長 (Web担当者Forum, citing Nikkei, May 17, 2024) — the plus current commercial-contract fact: LINE Yahoo extended its Recherche Google-technology supply contract by 2 années, guaranteeing Google-powered search via au moins March 2027, après abandoning a considéré switch to Naver’s search technology.
• Fix the Japanese keyword hack (Google, web.dev) — the authoritative detection-and-cleanup guide pour the spam attack.
• Localization SEO Que Fonctionne: 10 Real-World Lessons from 14 Markets (Ahrefs, Mateusz Makosiewicz) — inclut Ahrefs’ propre experience treating Japan as an early localization market, a real-world proof point que Japan trafic patterns are multi-script and non-obvious.
• Are Vous Choosing the Correct Keyword pour votre Japanese SEO? (Oban International) — a worked kanji/katakana volume exemple (treat the spécifique undated figures as illustrative; pull fresh numbers from votre propre outil).
• Moteur de recherche Market Share Japan (StatCounter Global Stats) — the current, dated market-share figures (re-pull avant relying on les; the split drifts month to month).

Testez vos connaissances: Japan SEO

Five rapide questions on how search en réalité fonctionne in Japan. Pick an réponse pour chaque, alors vérifier.

Journal des modifications