Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

dalroot/agentic-seo25 stars(GitHub 25 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md6.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

OptionExamplePros / Cons
Subdirectories/en/, /de/, /zh/Recommended; maintains domain authority
Subdomainsde.example.comSeparate hosting; less authority transfer
ccTLDexample.deStrongest 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.
  • 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)

IssueSolution
Route conflictgenerateStaticParams(); validate locale
Auto redirectlocaleDetection: false
MiddlewareApply only to prefixed paths (e.g. /zh)
URL duplicationManual 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

MarketTool
RussiaYandex Wordstat
KoreaNaver DataLab
GlobalGoogle 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

StrategyUse
True localizationAdjust price by purchasing power
CosmeticDisplay currency only; same price
ToolsParity Deals, Chargebee

i18n SEO Checklist (New Feature / New Locale)

New feature with i18n

  1. Add translation keys to all locale JSON files. Use translation for glossary, style guide, and translation workflow.
  2. Add generateMetadata() with alternates (hreflang) per page.
  3. Add JSON-LD with inLanguage and translated fields.
  4. Add page to sitemap with hreflang annotations.
  5. Set lang attribute on <html>; UTF-8 encoding.

New locale

  1. Add locale code to config; create {code}.json dictionary.
  2. Register in sitemap locale list; regenerate.
  3. Add OpenGraph locale and alternateLocale.
  4. 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.

The English summary is being prepared. Showing the original description.

dalroot/agentic-seo25Updated Oct 20, 2026

When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.

The English summary is being prepared. Showing the original description.

dalroot/agentic-seo25Updated Oct 20, 2026

When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.

The English summary is being prepared. Showing the original description.

dalroot/agentic-seo25Updated Oct 20, 2026

When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.

The English summary is being prepared. Showing the original description.

dalroot/agentic-seo25Updated Oct 20, 2026

When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.

The English summary is being prepared. Showing the original description.

dalroot/agentic-seo25Updated Oct 20, 2026

When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.

The English summary is being prepared. Showing the original description.

dalroot/agentic-seo25Updated Oct 20, 2026

See all skills by dalroot

Report a problem with this skill