blog-translate

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

1|Updated Dec 24, 2021
One-click install
npx skills add https://github.com/arthur-fontaine/arthurfontaine.fr --skill blog-translate-arthur-fontaine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blog-translate
Source: https://github.com/arthur-fontaine/arthurfontaine.fr/tree/main/.agents/skills/blog-translate
Command: npx skills add https://github.com/arthur-fontaine/arthurfontaine.fr --skill blog-translate-arthur-fontaine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Translating blog content for international audiences usually breaks markdown structure, frontmatter, charts, and SEO metadata, and produces literal machine-translation output that fails to rank in local search results. ## Core Features & Use Cases - SEO-Optimized Translation: Localizes keywords, title tags, meta descriptions, and slugs per target market instead of transliterating them. - Format Preservation: Keeps markdown structure, frontmatter keys, image URLs, code fences, SVG chart attributes, and schema JSON-LD intact while translating only user-facing text. - Locale-Aware Formatting: Converts numbers, dates, currencies, and quote styles per locale (de-DE, fr-FR, es-MX, ja-JP, and more) using shared reference rules. - Quality Guardrails: Scans output for machine-translation artifacts such as literal idioms, mixed-language sentences, and unlocalized frontmatter, flagging each issue inline. - Use Case: Translate an English markdown blog post into German, French, and Japanese in one run, producing publication-ready files under translations/{lang}/ with localized slugs and verified structural integrity. ## Quick Start Translate my blog post content/posts/ai-slop.md into German and Japanese with SEO-optimized localization.

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 hreflang target codes such as de, fr, es-MX, or ja. The skill spawns a translator agent per language in parallel and saves each result under translations/{lang}/ with a localized slug.

How to translate markdown blog posts without breaking frontmatter and code blocks?▼

The skill translates only frontmatter values, headings, body text, alt text, and captions while preserving markdown structure, frontmatter keys, URLs, executable code fences, and SVG attributes. Schema JSON-LD is translated only for user-facing strings, never names or IDs.

Does blog translation localize keywords for SEO in each language?▼

Yes. The skill builds a keyword localization map per target language, keeping established terms like Content Marketing in German and swapping to native search terms where real local search behavior exists. Titles, meta descriptions, and H2 headings are updated consistently.

What language codes are supported for blog translation?▼

Targets use Google-compatible hreflang tags such as de, fr, es-MX, ja, pt-BR, and zh-Hant, normalized to ISO 639-1 with optional script and region codes. Ambiguous codes like es, pt, or zh require a region or explicit neutral mode, and invalid codes get a correction suggestion.

Why does my translated blog still look machine-translated?▼

Machine-translation artifacts include literal idioms, unnatural word order, mixed-language sentences, and unlocalized numbers or dates. The skill's quality guardrail phase scans for these patterns, flags each issue with file path and line number, and re-passes flagged passages before delivery.

What is the difference between blog translation and blog localization?▼

Translation handles language conversion, formatting, and keyword localization. Cultural deep-adaptation such as swapping brand examples, legal references, statistics sources, and CTA tone is reserved for the separate blog-localize step, which should run after translation completes.