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
Decision gist · record as of 2026-07-21
Internationalization helps you plan multi-language site structure, choose URL patterns, and implement hreflang correctly. 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.
Use it when
- Internationalization requires hreflang tags to tell search engines which language version of a page targets which audience.
- Internationalization recommends: use ccTLDs (example.de) for strong regional targeting and when you need separate hosting.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
rampstackco/claude-skills/internationalization · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
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.
Internationalization
Add languages and regions in a way that works for users, search engines, and the team maintaining the content. Stack-agnostic.
When to use
- Adding the first non-English (or non-default) language
- Adding additional locales to an existing internationalized site
- Choosing URL structure for languages
- Implementing hreflang tags
- Designing translation workflow
- Handling currency, date, time, and
(truncated - see the full file via the links below)
File tree — 2 files
skills/internationalization/SKILL.md
skills/internationalization/references/locale-checklist.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Plan multi-language site structure with URL patterns and hreflang”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Build applications ready for international audiences with comprehensive guidance on text externalization, message formatting, and locale-specific adaptations. Learn to handle dates, times, numbers, currency, and right-to-left layouts using modern APIs and libraries like react-intl. Covers practical implementation patterns and best practices for managing translations and regional variations across your codebase.
Localization-l10n guides you through adapting internationalized applications for specific regions, languages, and cultural contexts. It covers translation management with namespace organization, locale-specific formatting for dates and currency, RTL support, and regional feature handling like address formats and measurement units. The skill includes testing strategies, content delivery optimization, and integration patterns to ensure your app works seamlessly across global markets.
Build truly global applications with framework-agnostic localization patterns covering the entire i18n pipeline. Learn locale detection strategies, ICU message formatting with proper pluralization rules, RTL layout techniques using CSS logical properties, and SEO best practices with hreflang tags. Includes practical guidance on choosing between compile-time and runtime i18n libraries, managing translation workflows, and avoiding common pitfalls in multilingual development.
This skill equips your Next.js App Router project with complete i18n capabilities using next-intl v4. It walks you through setting up locale-based routing, extracting user-facing strings into translation files, and scaling translations across 14+ languages via parallel Codex agents—then verifies the results to catch missing keys or residual English content.
Validate internationalization and localization across your product with systematic testing of translation completeness, locale-specific date/time/currency formatting, right-to-left language layouts, and cultural appropriateness. Detect hardcoded strings, verify Unicode support, and ensure native speaker quality before launching into new markets or adding language support.
This skill systematically audits your application's internationalization layer to catch untranslated content and locale-specific gaps before deployment. It integrates with Claude Code to scan codebases for hardcoded strings and verify that all user-facing text has proper translation coverage across your supported languages.
More skills localization-strategy (MIT) · internationalization (MIT) · Internationalizing Websites (MIT) · blog-translate (MIT) · translation (MIT) · localization-toolkit (MIT) · i18n-expert (MIT)