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.
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
- Read the source file (markdown, MDX, or HTML).
- Auto-detect source language. Order of preference:
- Frontmatter
lang field.
- HTML
lang attribute.
- Content analysis (script, common stop words).
- 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)."
- 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 the translatable surface:
- Frontmatter:
title, description, tags, author (only when
translatable, e.g. role labels, not personal names).
- All headings (H1, H2, H3).
- Body paragraphs.
- Image
alt text and <figcaption> content.
- Chart
<text> and <tspan> content; preserve every SVG attribute (x,
y, font-size, fill, transform).
- FAQ questions and answers.
- Citation capsule text.
- Key Takeaways or summary box.
- CTA text.
- Internal-link zone anchor text.
Preserve unchanged:
- Markdown and HTML structure, tags, attributes.
- Image URLs, link URLs, frontmatter keys.
- Code blocks (translate inline comments only when meaningful).
- Internal-link zone markers (
[INTERNAL-LINK: ...]).
- Source organization names in citations (Gartner, McKinsey, etc.).
- Person names.
- Schema JSON-LD blocks (translate only the user-facing string values).
Identify the primary and secondary keywords for Phase 3.
Phase 3: Keyword Localization
For each target language:
- Decide whether the source keyword is the established term in the target
market. If yes (e.g., "Content Marketing" stays in German), keep it.
- If a local equivalent has real search behavior, swap to it.
- Apply the same logic to secondary keywords.
- Record the mapping. The translator agent uses it to update title, meta
description, and H2 headings consistently.
Phase 4: Translation
Spawn the blog-translator agent (via Task) for each target language with:
- The source content.
- The keyword localization map from Phase 3.
- The target language code.
- Pointers to
references/translation-rules.md and the cultural profile in
references/cultural-adaptation.md if one exists for the target locale.
Run agents in parallel when translating into multiple languages.
The agent returns the fully translated post in the same format as the input.
Phase 5: Post-Processing
For each translated version:
- Add or update locale frontmatter:
lang: "de"
translatedFrom: "en"
translatedDate: "YYYY-MM-DD"
slug: "wie-man-ki-slop-vermeidet"
- Verify structural integrity:
- Same number of H2 and H3 sections as the original.
- All images present with translated alt text.
- All SVG charts present with translated text labels (length-adjusted:
DE +30%, FR +15%, JA -20%, others see
references/translation-rules.md).
- FAQ count matches.
- Citation capsules present in each H2.
- Save translated files:
translations/
{lang}/{localized-slug}.{ext}
When invoked from blog-multilingual, save into
multilingual/{lang}/{localized-slug}.{ext} instead.
Phase 6: Translation-Quality Guardrails
Scan the output for machine-translation artifacts before reporting done:
- Literal idioms (English idioms transliterated, not adapted).
- Unnatural word order (SOV translated as SVO into a non-SVO language, or
the reverse).
- Mixed-language sentences (other than established loanwords).
- Number, date, or currency strings still in source format.
- Frontmatter strings still in the source language.
Flag every issue inline (file path, line number, fix suggestion). The
translator agent should re-pass any flagged passage before delivery.
Phase 7: Delivery
## Translation complete: [Original title]
### Source
- Language: [source]
- File: [source path]
### Translations
| Language | File | Keywords adapted | Status |
|----------|------|------------------|--------|
| de | translations/de/{slug}.md | [N] | ok |
| fr | translations/fr/{slug}.md | [N] | ok |
### Quality checks
- Structural integrity: pass / fail per language
- Meta tags localized: pass / fail per language
- Numbers, dates, currencies formatted per locale: pass / fail
- Keywords localized: [N] keywords adapted
- Machine-translation artifacts flagged: [N] (see notes above)
### Next steps
- Run `/blog localize <file> --locale <code>` for cultural deep-adaptation.
- Run `/blog locale-audit translations/` to verify completeness.
- Use `/blog multilingual` to combine write, translate, localize, hreflang
in one command.
Error Handling
| Scenario |
Action |
| Unsupported language code |
Suggest the correct ISO 639-1 code |
| Source equals a target |
Skip with "Source is already in [lang]" |
| File not found |
Report error with suggested path |
| Translator agent timeout |
Retry once, then report partial results |
| Binary or non-text file |
Report error, suggest correct file |
Cross-References
- Next step (cultural depth):
/blog localize <file> --locale <code>
- QA sweep across all language versions:
/blog locale-audit <directory>
- One-command pipeline:
/blog multilingual <topic> --languages <codes>
1---2name: blog-translate3description: >4 Translate existing blog posts into one or more target languages with5 SEO-optimized localization. Produces native-quality translations that6 preserve markdown structure, frontmatter, schema JSON-LD, image and chart7 embeds, and citation capsules. Localizes keywords, meta tags, numbers,8 dates, currencies, and quote styles per locale. Flags machine-translation9 artifacts for review. Run BEFORE blog-localize: this handles language10 conversion; localize handles cultural adaptation after translation11 completes.12 Use when user says "translate blog", "blog translate", "uebersetzen",13 "traduire", "traducir", "translate post", "blog auf Deutsch", "blog en14 espanol".15user-invokable: true16argument-hint: "<file> --to <comma-separated-codes>"17compatibility: Standalone within claude-blog. Invoked by blog-multilingual.18metadata:19 source: https://skillmd.com/skills/infrasity-labs/blog-translate20---2122# Blog Translate, SEO-Optimized Blog Translation2324Translates an existing blog post into one or more target languages. Unlike25generic translation, this skill produces SEO-optimized, publication-ready26content with localized keywords, meta tags, and culturally correct27formatting.2829## Key References3031Load on demand:3233- `references/translation-rules.md`, format preservation, number/date/currency34 formats per locale, quote handling, quality criteria.35- `references/cultural-adaptation.md`, cultural profiles per locale (DACH,36 Francophone, Hispanic, Japanese, custom). This file is shared with37 `blog-localize` (do not duplicate).3839## Workflow4041### Phase 1: Input Parsing42431. Read the source file (markdown, MDX, or HTML).442. Auto-detect source language. Order of preference:45 - Frontmatter `lang` field.46 - HTML `lang` attribute.47 - Content analysis (script, common stop words).483. Parse target languages from `--to` as comma-separated ISO 639-1 codes49 (`de,fr,es,ja,pt-BR`). If `--to` is missing, ask the user once: "Which50 languages should I translate to? Provide ISO 639-1 codes (e.g., de, fr,51 es, ja, pt-BR)."524. Validate every code. Reject invalid ones with a suggestion (`jp` becomes53 "Did you mean `ja` for Japanese?"). If a target equals the source54 language, skip it with a notice.5556### Phase 2: Content Analysis5758Extract the translatable surface:5960- Frontmatter: `title`, `description`, `tags`, `author` (only when61 translatable, e.g. role labels, not personal names).62- All headings (H1, H2, H3).63- Body paragraphs.64- Image `alt` text and `<figcaption>` content.65- Chart `<text>` and `<tspan>` content; preserve every SVG attribute (`x`,66 `y`, `font-size`, `fill`, `transform`).67- FAQ questions and answers.68- Citation capsule text.69- Key Takeaways or summary box.70- CTA text.71- Internal-link zone anchor text.7273Preserve unchanged:7475- Markdown and HTML structure, tags, attributes.76- Image URLs, link URLs, frontmatter keys.77- Code blocks (translate inline comments only when meaningful).78- Internal-link zone markers (`[INTERNAL-LINK: ...]`).79- Source organization names in citations (Gartner, McKinsey, etc.).80- Person names.81- Schema JSON-LD blocks (translate only the user-facing string values).8283Identify the primary and secondary keywords for Phase 3.8485### Phase 3: Keyword Localization8687For each target language:88891. Decide whether the source keyword is the established term in the target90 market. If yes (e.g., "Content Marketing" stays in German), keep it.912. If a local equivalent has real search behavior, swap to it.923. Apply the same logic to secondary keywords.934. Record the mapping. The translator agent uses it to update title, meta94 description, and H2 headings consistently.9596### Phase 4: Translation9798Spawn the `blog-translator` agent (via Task) for each target language with:99100- The source content.101- The keyword localization map from Phase 3.102- The target language code.103- Pointers to `references/translation-rules.md` and the cultural profile in104 `references/cultural-adaptation.md` if one exists for the target locale.105106Run agents in parallel when translating into multiple languages.107108The agent returns the fully translated post in the same format as the input.109110### Phase 5: Post-Processing111112For each translated version:1131141. Add or update locale frontmatter:115 ```yaml116 lang: "de"117 translatedFrom: "en"118 translatedDate: "YYYY-MM-DD"119 slug: "wie-man-ki-slop-vermeidet"120 ```1212. Verify structural integrity:122 - Same number of H2 and H3 sections as the original.123 - All images present with translated alt text.124 - All SVG charts present with translated text labels (length-adjusted:125 DE +30%, FR +15%, JA -20%, others see `references/translation-rules.md`).126 - FAQ count matches.127 - Citation capsules present in each H2.1283. Save translated files:129 ```130 translations/131 {lang}/{localized-slug}.{ext}132 ```133 When invoked from `blog-multilingual`, save into134 `multilingual/{lang}/{localized-slug}.{ext}` instead.135136### Phase 6: Translation-Quality Guardrails137138Scan the output for machine-translation artifacts before reporting done:139140- Literal idioms (English idioms transliterated, not adapted).141- Unnatural word order (SOV translated as SVO into a non-SVO language, or142 the reverse).143- Mixed-language sentences (other than established loanwords).144- Number, date, or currency strings still in source format.145- Frontmatter strings still in the source language.146147Flag every issue inline (file path, line number, fix suggestion). The148translator agent should re-pass any flagged passage before delivery.149150### Phase 7: Delivery151152```153## Translation complete: [Original title]154155### Source156- Language: [source]157- File: [source path]158159### Translations160| Language | File | Keywords adapted | Status |161|----------|------|------------------|--------|162| de | translations/de/{slug}.md | [N] | ok |163| fr | translations/fr/{slug}.md | [N] | ok |164165### Quality checks166- Structural integrity: pass / fail per language167- Meta tags localized: pass / fail per language168- Numbers, dates, currencies formatted per locale: pass / fail169- Keywords localized: [N] keywords adapted170- Machine-translation artifacts flagged: [N] (see notes above)171172### Next steps173- Run `/blog localize <file> --locale <code>` for cultural deep-adaptation.174- Run `/blog locale-audit translations/` to verify completeness.175- Use `/blog multilingual` to combine write, translate, localize, hreflang176 in one command.177```178179## Error Handling180181| Scenario | Action |182|----------|--------|183| Unsupported language code | Suggest the correct ISO 639-1 code |184| Source equals a target | Skip with "Source is already in [lang]" |185| File not found | Report error with suggested path |186| Translator agent timeout | Retry once, then report partial results |187| Binary or non-text file | Report error, suggest correct file |188189## Cross-References190191- Next step (cultural depth): `/blog localize <file> --locale <code>`192- QA sweep across all language versions: `/blog locale-audit <directory>`193- One-command pipeline: `/blog multilingual <topic> --languages <codes>`