blog-translate

Translates blog posts into target languages with SEO-optimized localization and format preservation.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/captaindevv/SEO-ajaypipes --skill blog-translate-captaindevv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blog-translate
Source: https://github.com/captaindevv/SEO-ajaypipes/tree/main/skills/blog-translate
Command: npx skills add https://github.com/captaindevv/SEO-ajaypipes --skill blog-translate-captaindevv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Translating blog posts for international audiences often produces literal, machine-quality output that breaks markdown structure, ignores local search behavior, and leaves numbers, dates, and currencies in the source format. This Skill converts existing blog posts into publication-ready translations that preserve structure and localize SEO elements per target market. ## Core Features & Use Cases - Structure-preserving translation: Translates markdown, MDX, or HTML posts while keeping frontmatter keys, image URLs, code blocks, SVG chart attributes, schema JSON-LD, and citation capsules intact. - SEO keyword localization: Maps source keywords to terms native speakers actually search for in each target market, then applies them consistently across titles, meta descriptions, and headings. - Locale-aware formatting: Converts numbers, dates, currencies, and quote styles per locale (de-DE, fr-FR, es-MX, ja-JP, and more) using built-in translation rules and cultural profiles. - Quality guardrails: Scans output for machine-translation artifacts such as literal idioms, mixed-language sentences, and unlocalized frontmatter, flagging each issue with file path and line number. - Use Case: You wrote an English blog post and want German, French, and Japanese versions. Run the translation once and receive three structurally identical, SEO-localized files saved under translations/de, translations/fr, and translations/ja. ## Quick Start Translate my blog post 'content/ai-trends.md' into German, French, and Japanese with localized keywords and formatting.

Frequently Asked Questions about blog-translate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate a blog post into multiple languages at once?▼

Provide the source file and a comma-separated list of ISO 639-1 target codes such as de,fr,es,ja. The Skill spawns a translator agent per language, runs them in parallel, and saves each result under translations/{lang}/{localized-slug}.

How to translate markdown blog posts without breaking frontmatter or images?▼

The translation preserves markdown structure, HTML tags, frontmatter keys, image URLs, code blocks, and SVG attributes. Only translatable text such as titles, headings, alt text, figcaptions, and body paragraphs is converted.

Does blog translation localize keywords for each target market?▼

Yes. The Skill decides whether the source keyword is the established term in the target market or whether a local equivalent with real search behavior should replace it, then applies the mapping to titles, meta descriptions, and H2 headings.

What file formats does blog translation support?▼

It accepts markdown, MDX, and HTML source files. Source language is auto-detected from the frontmatter lang field, the HTML lang attribute, or content analysis of script and stop words.

What happens if I enter an invalid language code?▼

Invalid codes are rejected with a suggestion, for example jp returns a hint asking if you meant ja for Japanese. If a target language equals the detected source language, that target is skipped with a notice.

When should I use translation versus cultural localization for blog content?▼

Run translation first to convert the language, then run the localize step for cultural deep-adaptation such as brand examples, legal references, and CTA tone. Translation handles language conversion only and is designed to run before localization.