blog-localize

Adapt translated blog posts culturally for target markets like DACH, Francophone, and Japanese locales.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translated blog posts often read as obviously translated, with foreign brand examples, irrelevant legal references, mismatched tone, and US-centric statistics that fail to resonate with local readers. This Skill performs deep cultural adaptation so content feels locally authored rather than translated. ## Core Features & Use Cases - Cultural Audit: Scans translated posts for foreign-origin markers such as US brands, foreign laws (CCPA, FTC), idioms, and inconsistent formality, then reports severity-ranked findings. - Localized Substitution: Swaps brand examples, statistics sources, CTAs, and legal references (e.g., CCPA to DSGVO, Walmart to MediaMarkt) using built-in profiles for DACH, Francophone, Hispanic, and Japanese markets. - Tone Calibration: Enforces consistent formal or informal address (Sie/du, tu/vous) and adjusts CTA aggressiveness per market conventions. - Use Case: After translating an English blog post into German, run localization for de-DE to replace American examples with DACH equivalents, switch to Sie form, and adapt CTAs to informational style. ## Quick Start Localize the translated file post-de.md for the German market using the blog-localize skill.

Frequently Asked Questions about blog-localize

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

FAQPage Schema
How do I localize a translated blog post for Germany?▼

Run the localization step after translation with the locale code de-DE. The workflow audits the post for foreign markers, swaps US brands for DACH equivalents like MediaMarkt, replaces CCPA with DSGVO, and enforces consistent Sie or du formality.

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

Translation converts text from one language to another, while localization adapts the translated content culturally. Localization replaces brand examples, statistics sources, CTAs, legal references, and tone so the post feels written for the target market.

Which locales and markets does blog localization support?▼

Built-in cultural profiles cover DACH, Francophone, Hispanic, and Japanese markets, accepting full codes like de-DE, fr-CA, es-MX, pt-BR, and zh-TW. For unsupported locales, a custom-locale template builds a minimal profile inline.

What happens if no local statistics exist for my target market?▼

The original statistic is kept with a geographic-scope note such as "In the US, ..." so readers understand the data context. Source attribution is never stripped, and local data is searched first before falling back.

Can I localize a blog post without translating it first?▼

Localization is designed to run after blog-translate produces a base translation. If the file is not in the expected language, the Skill warns you and offers to translate first before proceeding with cultural adaptation.