HOME SKILLS BLOG GITHUB
// SKILL

MULTILINGUAL PUBLISHING
ONE COMMAND, EVERY LANGUAGE

Writing in English and translating later is a friction-stack: you maintain four separate workflows, hreflang gets forgotten, cultural adaptation happens never. blog-multilingual collapses the stack into one command. Specify your topic plus a list of target languages; Claude Blog writes the source post, produces SEO-optimized translations with format preservation, runs cultural localization per locale, and emits hreflang tags ready for deploy. Four skills cooperating: write, translate, localize, locale-audit.

CONTRIBUTED BY CHRIS MUELLER · PRO HUB CHALLENGE · original repo
$
/blog multilingual <topic> --languages es,fr,de,ja

REQUIRES CLAUDE BLOG INSTALLED IN CLAUDE CODE

// HOW IT WORKS

FOUR SKILLS. ONE PIPELINE.

blog-multilingual is not a single skill but an orchestrator. It calls four cooperating skills in sequence: write (English source), translate (SEO-optimized format-preserving translation), localize (cultural adaptation per profile), and locale-audit (multilingual QA). At the end it emits hreflang tag stubs for every language pair plus x-default.

The pipeline runs unattended once you specify languages. You get back a complete international content suite ready to deploy: source post plus N translated and localized variants, plus hreflang tags ready to paste into your CMS or static site generator.

01
ONE COMMAND
/blog multilingual --languages es,fr,de,ja produces a complete international content suite. Source post plus 4 translated and localized variants, plus hreflang.
02
SEO-PRESERVED TRANSLATION
Translations preserve markdown structure, frontmatter, schema blocks, inline SVG, and locale-correct number, date, currency, quote formatting.
03
CULTURAL ADAPTATION
Beyond translation: DACH, Francophone, Hispanic, Japanese profiles adapt examples, idioms, and references to the target culture. Custom profiles supported.
04
HREFLANG AUTOGENERATED
Outputs ready-to-deploy hreflang tags linking every language variant. No manual hreflang maintenance, no broken international targeting.
// USAGE

HOW TO RUN MULTILINGUAL

Commands

CommandWhat it does
/blog multilingual <topic> --languages <codes>Writes the source, translates, localizes, and emits hreflang for every target language
/blog multilingual <topic> --languages es,fr,de,jaConcrete four-locale run. Produces source plus 4 translated and localized variants plus hreflang
/blog multilingual <topic> --languages de,fr --source en --no-localizeTranslation only, cultural adaptation skipped. Useful when you have an existing brand voice you do not want re-styled
/blog multilingual <topic> --languages es,ja --format mdxForce MDX output for Next.js, Astro, or Docusaurus targets. Defaults to auto-detect from your project

Locale codes follow BCP 47. Plain ISO 639-1 codes (es, fr, de, ja) default to the most widely used regional variant; specify the full tag (es-MX, pt-BR, zh-TW) to pin a specific region.

Cross-Skill References

blog-multilingual delegates the heavy lifting to specialist skills. You can also invoke each one standalone:

Cultural Profiles

Four built-in cultural profiles ship with the skill:

  • DACH for German-Austrian-Swiss with formal/informal register awareness
  • Francophone for French, Quebec French, and African French variants
  • Hispanic for Spain, Mexico, and Argentina variants
  • Japanese with formality registers (casual, polite, honorific)

Custom profiles can be added via YAML configs in the skill's references directory. Each profile defines example substitutions, idiom mappings, legal-reference swaps, and CTA tone adjustments applied during the localize phase.

// FAQ

QUESTIONS ABOUT MULTILINGUAL

blog-multilingual orchestrates four skills in sequence: write (English source), translate (SEO-optimized translation), localize (cultural adaptation), locale-audit (multilingual QA). Each step builds on the previous. Running translate alone gives you mechanical translations; running localize alone has nothing to localize. The orchestrator handles the full pipeline plus hreflang tag emission.
Markdown, MDX, HTML, frontmatter YAML, JSON-LD schema blocks, inline SVG, code blocks, and locale-correct number, date, currency, quote formatting. The blog-translator agent (no Bash, per security best practice) handles format preservation while the translation happens.
DACH (German-Austrian-Swiss with formal/informal register awareness), Francophone (French, Quebec French, African French variants), Hispanic (Spain, Mexico, Argentina variants), and Japanese (with formality registers: casual, polite, honorific). Custom profiles can be added via YAML configs in the skill's references directory.
After write + translate + localize complete, the orchestrator emits hreflang tag stubs for every language pair, plus x-default. The output is ready-to-paste into your CMS or static site generator. /blog locale-audit verifies hreflang correctness across the full multilingual suite post-publish.
Chris Mueller via the AI Marketing Hub Pro Hub Challenge. Chris also contributed seo-hreflang cultural profile enhancements to claude-seo v1.9.0. The multilingual blog suite scored 85/100 Proficient in the security and quality review. Original at github.com/Chriss54/claude-blog-multilingual. Integrated into Claude Blog v1.7.0 with Chris's permission.
// RELATED SKILLS

EXPLORE MORE

SEO TRANSLATION

Pure translation skill, SEO-optimized format preservation. Use standalone or via /blog multilingual.

SEO TRANSLATION →

CULTURAL LOCALIZATION

Deep adaptation beyond translation: idioms, examples, references per cultural profile.

CULTURAL LOCALIZATION →

MULTILINGUAL AUDIT

Post-publish QA across the full multilingual suite: completeness, hreflang correctness, meta parity, freshness.

MULTILINGUAL AUDIT →

VIEW ALL 28 SKILLS →

PUBLISH IN 4 LANGUAGES
IN ONE COMMAND.

$
git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git && bash claude-blog/install.sh
VIEW ON GITHUB ALL SKILLS >