Agent skill · marketing growth · kostja94
localization-strategy
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.
Why this skill is useful
Provides specific localization strategies and SEO principles that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-06-09. 860 stars on the source repository.
What this skill does
Strategies: 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: 1. Target markets: Priority languages/regions 2. Product type: SaaS, AI tool, content 3. 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-DE vs de-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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills kostja94/localization