Docsbook
Overview

Multi-Language Documentation SEO

Most product docs in 2026 are English-only. The teams that translate properly capture organic traffic the English-only sites never see — searches in Japanese, Spanish, German, Mandarin for the same buying intent.

This post is the practical SEO guide for shipping docs in 15 languages without breaking Google or AI search.

TL;DR#

  • Each language must live at a separate URL (/ja/, /es/, /de/)
  • Add hreflang tags so search engines know what is a translation of what
  • Use lang attribute on the <html> element
  • AI translation in 2026 is good enough for docs (not for marketing copy)
  • One canonical English source, AI translations on top — never duplicate sources

The fundamental rule#

One URL per (page, language) pair.

Wrong:

docs.yourcompany.com/quick-start?lang=ja
docs.yourcompany.com/quick-start (with cookies)

Right:

docs.yourcompany.com/quick-start
docs.yourcompany.com/ja/quick-start
docs.yourcompany.com/es/quick-start

Without separate URLs, Google indexes only one version. You lose 90% of the multi-language SEO upside.

hreflang setup#

Each page needs <link rel="alternate" hreflang="..."> tags pointing to every translation.

<link rel="alternate" hreflang="en" href="https://docs.yourcompany.com/quick-start">
<link rel="alternate" hreflang="ja" href="https://docs.yourcompany.com/ja/quick-start">
<link rel="alternate" hreflang="es" href="https://docs.yourcompany.com/es/quick-start">
<link rel="alternate" hreflang="x-default" href="https://docs.yourcompany.com/quick-start">

x-default tells Google "if no other locale matches, show this." Usually the English version.

Docsbook generates hreflang automatically when you enable a language in Settings → Languages.

When AI translation is good enough#

Three factors:

Content type AI translation quality Recommendation
Reference docs (API, config) High Use AI
Tutorials and how-to High Use AI, light human review
Marketing landing pages Medium Human review required
Brand copy (taglines, mission) Low Human translation
Code samples N/A Keep original
Error messages High when terminology is consistent Use AI

The improvement from 2023 → 2026 in LLM translation quality has been dramatic for technical content. For docs specifically, AI now matches or beats human translation on:

  • Terminology consistency (humans drift, models do not)
  • Speed (15 languages in minutes)
  • Cost ($0.001 per page vs $0.10 per word with humans)

What humans still beat:

  • Cultural localization (date formats, examples, brand voice)
  • High-stakes legal copy
  • Marketing taglines

For documentation, the cost-benefit tilts heavily toward AI translation in 2026.

Each language indexed separately#

Three signals matter:

  1. URL pattern — /ja/ subdirectory or ja.yourdomain.com subdomain (subdirectory is easier)
  2. hreflang tags — bidirectional, point both directions between all versions
  3. lang attribute — <html lang="ja"> on the Japanese version
  4. Sitemap entries — each language gets its own entry with xhtml:link annotations

Google then ranks each language in its respective locale's search results. A user in Japan searching in Japanese sees /ja/. A user in Spain searching in Spanish sees /es/.

What AI search engines do with translations#

Three behaviors observed:

ChatGPT#

ChatGPT will cite a translated page if the query is in that language. Asking ChatGPT "ドキュメンテーションプラットフォームを比較してください" (compare documentation platforms in Japanese) returns Japanese sources, including Japanese versions of docs.

Perplexity#

Same as ChatGPT — Perplexity strictly matches query language to source language. If you translate well, you gain a citation channel per language.

Gemini#

Google Gemini uses Google's underlying index. The same hreflang and locale signals that help Google AI Overviews help Gemini.

How Docsbook ships multi-language#

Three steps to enable a language:

  1. Dashboard → Settings → Languages → select language → enable
  2. AI translates the entire docs to that language (PRO: 50/month, PRO+: 500/month)
  3. Page appears at /{language-code}/{path} with hreflang and lang set correctly

15 languages supported: EN, ES, FR, DE, PT, IT, RU, ZH, JA, KO, AR, HI, TR, PL, NL.

You can also upload your own translations through the MCP tool upload_translation or the admin UI if you have a human translator.

Translation modes#

Three modes available:

  • Auto — Docsbook AI translates everything automatically
  • Manual — pending translations queue, you review before publishing
  • External — webhook your own translation pipeline (your TMS, your translators)

External mode is for teams that already have a translation memory and want to keep using it. The set_translation_mode MCP tool flips between modes.

Mistakes that kill multi-language SEO#

  • Query parameter switching (?lang=ja) — Google does not index these as separate pages
  • Cookie-based language detection — same problem, only one URL gets indexed
  • Missing hreflang tags — Google treats translations as duplicate content
  • One-way hreflang — both pages must reference each other
  • No lang attribute — screen readers and crawlers fall back to English

Cost economics#

Translating 200 pages to 14 additional languages:

DIY human translation Docsbook AI translation
Cost $20,000–80,000 Included in plan
Time 2–6 months Hours
Update cost $0.10–0.30 per word Free recompute when source changes
SEO indexing Manual hreflang setup Automatic

The Docsbook PRO+ plan ($59/mo) includes 500 translations/month — enough to keep 200 pages in 14 languages refreshed continuously.

Translate your docs to 15 languages with separate SEO per locale: start here. Each language indexed in its own market.

Updated

Powered by Docsbook