← ClaudeAtlas

internationalizing-websiteslisted

Adds multi-language support to Next.js websites with proper SEO configuration including hreflang tags, localized sitemaps, and language-specific content. Use when adding new languages, setting up i18n, optimizing for international SEO, or when user mentions localization, translation, multi-language, or specific languages like Japanese, Korean, Chinese.
aiskillstore/marketplace · ★ 329 · Web & Frontend · score 79
Install: claude install-skill aiskillstore/marketplace
# Internationalizing Websites Complete workflow for adding multi-language support to Next.js websites with SEO best practices. ## When to use this Skill - Adding new language versions to existing website - Setting up i18n (internationalization) for new website - Configuring SEO for multiple languages - User mentions: "add language", "translation", "localization", "hreflang", "multi-language" ## Supported Languages Common target markets: - 🇺🇸 English (en) - Global market - 🇯🇵 Japanese (ja) - Asian market - 🇨🇳 Chinese (zh) - Chinese market Extended support available for: - Korean (ko), Portuguese (pt), Spanish (es), French (fr), German (de) - Arabic (ar), Vietnamese (vi), Hindi (hi), Indonesian (id), Thai (th) - Traditional Chinese (zh-hk), Italian (it), Russian (ru) ## Internationalization Workflow Copy this checklist and track your progress: ``` i18n Progress: - [ ] Step 1: Prepare base language files - [ ] Step 2: Add new language files - [ ] Step 3: Update configuration files - [ ] Step 4: Add translations - [ ] Step 5: Configure SEO elements - [ ] Step 6: Validate and test ``` ### Step 1: Prepare base language files Ensure English (`en.json`) files exist as templates: **Required directories**: - `i18n/messages/en.json` - Main translations - `i18n/pages/landing/en.json` - Landing page translations **Verify structure**: ```bash # Check if base files exist ls i18n/messages/en.json ls i18n/pages/landing/en.json ``` If missing, create them with complete tran