Logo
Agent Skills
  • Skills
  • Category
  • Publishers
  • Cookbook
  • Blog
Logo
Agent Skills
Cookbook/Adding Multi-language Support
Adding Multi-language Support
advanced30 min read

Steps

  1. 1

    Install the Skill

    Download the internationalization skill to your skills folder.

  2. 2

    Create Base Language Files

    Set up your English (en.json) files as templates.

  3. 3

    Add New Languages

    Use the skill to add new language files.

  4. 4

    Configure SEO

    Set up hreflang tags and localized sitemaps.

  5. 5

    Test and Validate

    Verify language switching and SEO elements work correctly.

Back
Logo
Agent Skills

Discover and download skills for Claude Code and other AI agents

GitHub
Skills
  • Category
  • Publishers
  • Cookbook
Resources
  • Blog
  • GitHub
Legal
  • Privacy Policy
  • Terms of Service
Copyright © 2026 All Rights Reserved.

Adding Multi-language Support

Learn how to internationalize your Next.js website using the Internationalizing Websites skill.

Why Internationalization Matters

  • Reach global audiences
  • Improve SEO for different regions
  • Better user experience for non-English speakers

Install the Skill

mkdir -p ~/.claude/skills/awesomeskills/internationalizing-websites
curl -L https://raw.githubusercontent.com/littleben/awesomeAgentskills/main/internationalizing-websites/SKILL.md > ~/.claude/skills/awesomeskills/internationalizing-websites/SKILL.md

Getting Started

Ask Claude:

"Help me add Japanese language support to my Next.js website"

Key Concepts

Language Files Structure

i18n/
├── messages/
│   ├── en.json
│   └── ja.json
└── locale.ts

hreflang Tags

Essential for international SEO:

<link rel="alternate" hreflang="en" href="https://example.com/" />
<link rel="alternate" hreflang="ja" href="https://example.com/ja/" />

URL Structure

  • English: https://example.com/
  • Japanese: https://example.com/ja/
  • Chinese: https://example.com/zh/

Best Practices

  1. Use native speakers for translation review
  2. Maintain SEO keywords in each language
  3. Adapt content to local culture, don't just translate
  4. Test thoroughly in all supported languages