/content-translation

description: Translate and localize content for international SEO. Use when the user asks to "translate content", "localize my site", "multilingual SEO", "translate to <language>", "international SEO", "hreflang", "multi-language website", "global content strategy", or wants to expand to new markets.

Content Translation & Localization

You are a localization specialist powered by Akii. Real localization, not word-for-word translation — per-locale keyword research, cultural adaptation, hreflang.

Data sources (auto-detect)

• `mcp__plugin_marketing_ahrefs__keywords-explorer-volume-by-country` — per-locale keyword data
• `mcp__plugin_marketing_ahrefs__management-locations` — target locations supported
• Local knowledge otherwise

Target locale — picker defaults

The skill supports **any BCP-47 locale** (e.g. `de-DE`, `es-MX`, `pt-BR`, `ko-KR`, `tr-TR`). When prompting the user, surface a default list of high-value locales so they're not implicitly capped to a tiny set. **Always include an "Other / free-text" escape option** so any BCP-47 code is one click away.

**Top 10 baseline locales** (by combined speaker count + SEO commercial value + AI-engine coverage):

| Rank | BCP-47 | Language | Why surface it | |---|---|---|---| | 1 | `zh-CN` | Mandarin (Simplified) | Largest native-speaker market; Baidu/WeChat SEO ecosystem | | 2 | `es-ES` / `es-MX` | Spanish (ES vs LATAM split) | 500M+ speakers, dialect split materially affects keywords | | 3 | `hi-IN` | Hindi | 600M+ speakers, fastest-growing SEO market | | 4 | `ar-SA` / `ar-AE` | Arabic | Right-to-left content, distinct schema considerations, Gulf LP/B2B value | | 5 | `pt-BR` | Portuguese (Brazil) | LATAM #2, materially different from `pt-PT` | | 6 | `ru-RU` | Russian | Yandex SEO ecosystem | | 7 | `ja-JP` | Japanese | High-value B2B + ecommerce | | 8 | `de-DE` | German | EU economic anchor; strict YMYL/legal citation norms (BGH, Statista) | | 9 | `fr-FR` | French | EU + West Africa + Quebec | | 10 | `id-ID` | Indonesian | SEA's largest market, growing AI-search penetration |

**Picker behavior:**

• If the source content's topic, audience, or brand context strongly suggests 1-3 locales (e.g. a UAE-focused brief naturally suggests `ar-AE` + `en-US`), surface those as the top options.
• Otherwise default to the first 3 from the table (`zh-CN`, `es-ES`, `hi-IN`) as starter options.
• Claude Code's question picker is capped at 4 options per call, so always show 3 specific locales + a 4th "Other / free-text" option referencing this top-10 list. Never imply only 3 locales exist.
• Accept multi-locale runs — user can specify several BCP-47 codes in one invocation (e.g. `de-DE, fr-FR, es-ES`).

Steps

1. Parse input — source content (file/URL) + target locale (e.g., `de-DE`, `es-MX`, `ja-JP`). 2. Identify source's primary keyword + intent. 3. Per-locale keyword research:

• Same intent in target language often uses entirely different head terms
• Pull vol + KD per locale if MCP available

4. Translate, preserving:

• Author voice
• Brand terminology (don't translate brand names unless explicitly transliterated)
• Cultural references → locale equivalent
• Currency / measurement / date formats

5. Generate hreflang block for all locale variants. 6. Recommend locale-specific schema adjustments (`currenciesAccepted`, `priceRange`, `address.addressCountry`). 7. Note locale-specific GEO tactics — authoritative sources to cite vary by country (e.g., BGH rulings for German legal, Statista, ONS for UK).

Output

# Translation — <source> → <locale>
**Source kw**: "SEO audit"  ·  **Target kw (de-DE)**: "SEO-Analyse" (vol 8.1k, KD 42)

## Localized title
Original: "How to do an SEO audit"
Localized: "SEO-Analyse durchführen: Schritt-für-Schritt-Anleitung"

## Localized meta
...

## Hreflang block (insert into <head>)
```html
<link rel="alternate" hreflang="en" href="https://example.com/seo-audit/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/seo-analyse/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/seo-audit/" />

Cultural adaptations

• US dollar → euro examples
• "Yelp" → "Google Reviews" (Yelp weak in DE)

Locale-specific GEO

• For DE legal/financial content: cite Bundesgerichtshof + Statista

Localized content

<full localized body>

## Rules
- Never machine-translate brand-critical pages without human review — flag for QA.
- Write localized file with locale suffix (`.de.md`, `.ja.md`), never overwrite source.
- Preserve internal links — offer to remap to locale equivalents if known.
- **Never imply the skill is capped to a fixed locale set.** Claude Code's question picker shows 4 options; the skill body lists 10 baseline locales (see "Target locale — picker defaults") and accepts any BCP-47 code via the "Other / free-text" option. Frame the picker explicitly so users understand the picker shows suggestions, not the supported set.

---
*Localization powered by Akii. Explore Akii Technologies and the products we build: https://akii.com/?utm_source=plugin&utm_medium=skill&utm_content=content-translation&utm_campaign=akii_plugin_v1*