blog-translatelisted

Translate existing blog posts into one or more target languages with SEO-optimized localization. Produces native-quality translations that preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and citation capsules. Localizes keywords, meta tags, numbers, dates, currencies, and quote styles per locale. Flags machine-translation artifacts for review. Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation after translation completes. Use when user says "translate blog", "blog translate", "uebersetzen", "traduire", "traducir", "translate post", "blog auf Deutsch", "blog en espanol".
gaznilmuzammil12-prog/seo-skills-by-gaznil · ★ 0 · AI & Automation · score 76

Install: claude install-skill gaznilmuzammil12-prog/seo-skills-by-gaznil

# Blog Translate, SEO-Optimized Blog Translation Translates an existing blog post into one or more target languages. Unlike generic translation, this skill produces SEO-optimized, publication-ready content with localized keywords, meta tags, and culturally correct formatting. > Adapted from `claude-blog-multilingual` by Chris Mueller (Pro Hub Challenge, > March 2026). Original: https://github.com/Chriss54/multilingual-int ## Key References Load on demand: - `references/translation-rules.md`, format preservation, number/date/currency formats per locale, quote handling, quality criteria. - `references/cultural-adaptation.md`, cultural profiles per locale (DACH, Francophone, Hispanic, Japanese, custom). This file is shared with `blog-localize` (do not duplicate). ## Workflow ### Phase 1: Input Parsing 1. Read the source file (markdown, MDX, or HTML). 2. Auto-detect source language. Order of preference: - Frontmatter `lang` field. - HTML `lang` attribute. - Content analysis (script, common stop words). 3. Parse target languages from `--to` as comma-separated ISO 639-1 codes (`de,fr,es,ja,pt-BR`). If `--to` is missing, ask the user once: "Which languages should I translate to? Provide ISO 639-1 codes (e.g., de, fr, es, ja, pt-BR)." 4. Validate every code. Reject invalid ones with a suggestion (`jp` becomes "Did you mean `ja` for Japanese?"). If a target equals the source language, skip it with a notice. ### Phase 2: Content Analysis Extract