Localization Strategy

Own the end-to-end localization decision and delivery lifecycle. Do not treat localization as a request to translate every source page or to create locale routes before the content is ready.

Boundaries

• This skill owns market and locale selection, scope, technical architecture, rollout, migration, release gates, and measurement.
• translation owns translated copy, terminology, style, review, and source-change updates.
• keyword-research owns target-market query research; do not translate a source keyword list.
• page-metadata, canonical-tag, and url-structure own their specialist implementation details. Coordinate them here without duplicating their full rules.
• Preserve project-specific product facts, route inventories, and terminology in the project context or implementation repository. Do not turn them into universal rules.

Establish the Current State

Read root contextus.md when present. Build the evidence set from the production site, route or CMS inventory, navigation and internal links, sitemap, source repository, analytics, and search data as available. A sitemap alone is not a complete page inventory.

Confirm: