internationalization

Internationalization guides you through launching and maintaining a site across multiple languages and regions. It covers five interconnected layers: URL structure (subfolders, subdomains, ccTLDs), content organization patterns, hreflang implementation, translation workflow design, and locale-specific UX decisions like currency, date formats, and RTL layout.

Internationalization helps you plan multi-language site structure, choose URL patterns, and implement hreflang correctly.

AI-generated summary based on this skill's SKILL.md

★ 500 ⁮ 64 MIT updated 2026-07-21 by rampstackco

Install

rampstackco/claude-skills/internationalization · repository language: Python

Manual (git clone) CLI (skillfed)coming soon

git clone https://github.com/rampstackco/claude-skills
cp -r claude-skills/skills/internationalization ~/.claude/skills/internationalization

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

How do I set up a multi-language website with proper URL structure?

Internationalization covers three main URL patterns: subfolders (example.com/en/, example.com/fr/), subdomains (en.example.com, fr.example.com), or country-code top-level domains (example.com, example.fr). Subfolders are easiest to manage and share domain authority; subdomains isolate content but dilute SEO signals; ccTLDs signal strong regional intent but require separate domain management. Choose based on your audience size per region and SEO priorities.

What is hreflang implementation and why does internationalization require it?

Internationalization requires hreflang tags to tell search engines which language version of a page targets which audience. Add rel="alternate" hreflang="xx" links in your page head or XML sitemap, plus an x-default tag for users whose language isn't covered. This prevents duplicate content penalties and ensures the right version ranks in each region.

How should I choose between ccTLD, subdomain, or subfolder for languages?

Internationalization recommends: use ccTLDs (example.de) for strong regional targeting and when you need separate hosting; subdomains (de.example.com) for regional autonomy but accept some SEO dilution; subfolders (example.com/de/) for simplest management and shared domain authority. Subfolders suit most startups; ccTLDs suit established brands with per-region teams.

What locale-aware UX elements does internationalization cover?

Internationalization addresses currency display, date/time formatting, number separators, RTL layout for Arabic and Hebrew, language switcher placement, and regional payment methods. Test RTL designs early—text direction affects navigation, forms, and images. Provide a visible, accessible language switcher so users can override locale detection.

How do I manage translation workflow and content across multiple locales?

Internationalization guides you to establish a translation management system (TMS) that tracks which content is translated, approved, and live per locale. Define approval workflows, assign translators by language, and version control translations alongside code. Automate hreflang and canonical tag generation to keep metadata in sync as content updates.

How can I audit and fix an underperforming internationalization rollout?

Internationalization recommends auditing hreflang correctness, checking for stale or missing translations, verifying locale-specific UX (currency, dates, RTL), and testing language switcher functionality. Use Google Search Console to spot indexing issues per region. Prioritize fixing broken hreflang chains and untranslated critical pages first.

SKILL.md

rendered from the published skill — quoted content, verbatim