Localization Strategy Agent Skill
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow, glossary, and style guide, use translation.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/kostja94/marketing-skills --skill localization-strategyThe instruction itself
18 sections, as written by the authorStrategies: Localization
Guides localization strategy for AI/SaaS products expanding into global markets. Covers i18n implementation, translation, pricing, and marketing adaptation--not just text translation.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, target markets, and brand.
Identify:
- Target markets: Priority languages/regions
- Product type: SaaS, AI tool, content
- Technical stack: Next.js, React, etc.
Localization vs. Translation
Localization includes:
- Product: Features, UI/UX, cultural adaptation
- Pricing: True localization (adjust by market) vs. cosmetic (currency only)
- Marketing: Channels, content, user personas
- Compliance: GDPR, local regulations
Technical (i18n)
URL Structure
Choose one; be consistent:
| Option | Example | Pros / Cons |
|--------|---------|-------------|
| Subdirectories | /en/, /de/, /zh/ | Recommended; maintains domain authority |
| Subdomains | de.example.com | Separate hosting; less authority transfer |
| ccTLD | example.de | Strongest geo signal; costly |
- Use subdirectories, not subdomains for i18n; subdomains transfer less authority.
- Default locale: Root path for default (e.g.
/for English); prefix for others (/zh/,/de/). - IETF BCP 47: Use valid codes (
en,en-US,zh-CN,pt-BR). Same language, different country (e.g.de-DEvsde-AT) needs ≥20% content difference for Google to differentiate.
i18n SEO Principles
- No hardcoded strings: All user-facing text via translation dictionary.
- Symmetric alternates: Every locale page lists ALL other versions (including self-reference). ~75% of international sites have hreflang errors; missing reciprocal links is the most common.
- x-default: Always include for fallback when user language/location doesn't match any version.
- Canonical alignment: Canonical must match the same regional version hreflang refers to; misalignment causes Google to ignore hreflang.
- Full SEO coverage: Metadata, OpenGraph, JSON-LD (
inLanguage), and sitemap all locale-aware.
Common Issues (Next.js + next-intl)
| Issue | Solution |
|-------|----------|
| Route conflict | generateStaticParams(); validate locale |
| Auto redirect | localeDetection: false |
| Middleware | Apply only to prefixed paths (e.g. /zh) |
| URL duplication | Manual switcher; getLocalizedHref() |
SEO
- Hreflang on all language versions; self-reference + symmetric annotations.
- Language switcher: Use
<a>not<button>; links in initial HTML. - Canonical: Handle multi-domain if using local TLDs; align with hreflang.
- SPAs: Use sitemap-based hreflang as backup when HTML head is JS-rendered. See rendering-strategies.
Keyword Research by Market
| Market | Tool |
|--------|------|
| Russia | Yandex Wordstat |
| Korea | Naver DataLab |
| Global | Google Keyword Planner, SEO tools |
Consider: Cultural expressions, search habits, competition, long-tail in small markets.
Terminology & Translation
- Translation workflow, glossary, style guide: See translation for full workflow
- Avoid machine translation for product/marketing: See translation (Human vs MT)
Pricing Strategies
| Strategy | Use |
|----------|-----|
| True localization | Adjust price by purchasing power |
| Cosmetic | Display currency only; same price |
| Tools | Parity Deals, Chargebee |
i18n SEO Checklist (New Feature / New Locale)
New feature with i18n
- Add translation keys to all locale JSON files. Use translation for glossary, style guide, and translation workflow.
- Add
generateMetadata()with alternates (hreflang) per page. - Add JSON-LD with
inLanguageand translated fields. - Add page to sitemap with hreflang annotations.
- Set
langattribute on<html>; UTF-8 encoding.
New locale
- Add locale code to config; create
{code}.jsondictionary. - Register in sitemap locale list; regenerate.
- Add OpenGraph
localeandalternateLocale. - Ensure all alternates are symmetric (every page lists all versions).
Multilingual Risks
- Batch publishing: Too many translated pages at once can trigger de-indexing or thin-content penalties.
- Mitigation: Roll out slowly; ensure content is product/industry relevant; avoid Wikipedia-like breadth; monitor indexing in GSC.
Avoid
- IP-based redirects that override user preferences.
- Machine translation without localization for product/marketing (see translation).
- Missing reciprocal hreflang between language versions.
- Canonical tags that conflict with hreflang.
Output Format
- Market priority
- i18n approach
- Keyword strategy per market
- Pricing recommendation
- Technical checklist
- i18n SEO checklist (if applicable)
Related Skills
- pricing-strategy: Base price structure; localization-strategy covers pricing by market
- page-metadata: Hreflang implementation
- url-structure: URL hierarchy for i18n (subdirectories, subdomains)
- content-strategy: Multilingual content planning; avoid thin translations
- translation: Translation workflow, glossary, style guide, human vs MT; produces content for localized pages
- navigation-menu-generator: Language switcher SEO
- affiliate-marketing: Local affiliates for target markets
- gtm-strategy: New market entry; localization as GTM for new geography
Other skills for the same job
different authors, same section of the catalogue
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.
Materials science toolkit. Crystal structures (CIF, POSCAR), phase diagrams, band structure, DOS, Materials Project integration, format conversion, for computational materials science.
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
How to use it
Take kostja94/localization-strategy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.