internationalizing-websites_skill

This skill helps you internationalize Next.js sites with SEO-ready hreflang, localized sitemaps, and language-specific content to improve global reach.

JavaScript

126

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill littleben/awesomeagentskills --skill internationalizing-websites

SKILL.md7.8 KB
WORKFLOW.md13.9 KB

Overview

This skill adds multi-language support to Next.js websites with built-in SEO considerations like hreflang tags, localized sitemaps, and language-specific meta content. It provides a step-by-step workflow, scripts to scaffold locale files, and validation checks to ensure correct routing and search-engine-facing signals. The goal is reliable localization that preserves SEO and user experience across markets.

How this skill works

The skill scaffolds new locale files from your base language, updates Next.js i18n configuration and routing, and injects localized entries into sitemaps and metadata. It offers scripts to add languages, generate translation placeholders, and add structured-data translations, then guides you through testing language switchers, hreflang tags, and localized meta tags. Finally it provides validation steps and SEO checks to ensure search engines index each language version correctly.

When to use it

Adding new language versions to an existing Next.js site
Setting up i18n for a new Next.js project
Optimizing international SEO (hreflang, localized sitemaps, meta tags)
When discussing localization, translation, multi-language support, or specific languages (e.g., Japanese, Chinese, Korean)
Before submitting multilingual sitemaps to Google Search Console

Best practices

Keep complete base translation files (en.json) as templates before adding languages
Use AI for initial drafts but always have native speakers review translations
Maintain consistent URL structure and language codes (ISO 639-1, plus regional variants)
Avoid auto-redirects by IP—allow users and crawlers to access all language versions
Verify hreflang tags, <html lang> attributes, and localized meta tags for every page

Example use cases

Add Japanese and Chinese versions and update sitemap with hreflang entries
Run i18n-add-languages.mjs to scaffold translation files and update locale mappings
Translate metadata and structured data per language, then validate with curl and Search Console
Set up language switcher and test routing across locales during staging
Run automated checks to ensure no untranslated strings or incorrect language codes are deployed

FAQ

Run the provided i18n-add-languages.mjs script to copy base files, update locale mappings, and add URLs to the sitemap; then fill translations and validate.

Should I use AI or human translators?

Use AI to generate initial drafts for speed, but always have native speakers review for cultural accuracy and SEO keyword alignment.

How do I verify hreflang and sitemap updates?

Inspect public/sitemap.xml for alternate links and hreflang entries, check <html lang> attributes in pages, and use Google Search Console’s hreflang validation tools.