{"enrichment":{"faq":[{"a":"Localization-strategy guides you beyond translation to full market adaptation. Start by prioritizing target markets based on demand and fit. Then implement technical i18n infrastructure: set up URL structures (subdirectories, subdomains, or ccTLDs), configure hreflang tags to signal language/region variants to search engines, and localize metadata. Adapt pricing for local purchasing power, customize marketing messaging for cultural context, and adjust UX for regional preferences. Use market-specific keyword research to inform content strategy for each locale.","q":"How do I localize my SaaS for international markets?"},{"a":"Localization-strategy distinguishes these as separate concerns. Translation converts text from one language to another. Localization goes further: it adapts your entire product\u2014pricing, payment methods, imagery, colors, date formats, currency, and cultural references\u2014to resonate with each market. Localization-strategy emphasizes that content localization means researching region-specific keywords and user expectations, not just running copy through a translator. This deeper adaptation is what drives engagement and SEO performance in non-English markets.","q":"What's the difference between localization vs translation?"},{"a":"Localization-strategy covers both technical layers. For i18n, choose your URL structure first (subdirectories like /en/, /fr/ are most common), then implement language detection and a language switcher. Configure hreflang tags in your HTML head to tell search engines which page serves which language/region combination\u2014this prevents duplicate content penalties. Include a self-referential hreflang tag and an x-default fallback. Test your hreflang setup regularly; misalignment is a common pitfall that tanks multilingual SEO performance.","q":"How do I implement i18n and hreflang for multilingual SEO?"},{"a":"Localization-strategy provides structured checklists for market entry. Key items: prioritize markets by revenue potential and competitive fit; research region-specific keywords and search behavior; set up URL structure and hreflang; localize all user-facing copy, imagery, and cultural references; adapt pricing and payment methods; configure language detection and switcher; test across devices and browsers in target regions; set up analytics to track performance by locale; plan content calendar for each market; document compliance requirements (GDPR, data residency, etc.); and establish a process for launching new features across all locales simultaneously to avoid batch publishing penalties.","q":"What's included in a global growth localization checklist?"},{"a":"Localization-strategy recommends subdirectories (/en/, /fr/, /de/) as the most SEO-friendly and easiest to implement approach. Subdomains (en.example.com) work but signal separate sites to search engines. Country-code top-level domains (ccTLDs like .fr, .de) are strongest for local SEO but costly and harder to manage at scale. Avoid query parameters (?lang=en) for language selection\u2014they're harder for crawlers to index. Choose one structure, implement consistent hreflang across all variants, and ensure your server correctly serves the right language version based on URL.","q":"How should I structure URLs for a multilingual website?"},{"a":"Localization-strategy emphasizes pricing parity and market-specific positioning. Research local purchasing power and competitor pricing in each region\u2014don't simply convert your home-market price to local currency. Consider local payment methods (Alipay in China, Klarna in Europe, etc.). Adapt marketing messaging to cultural values and pain points; what resonates in the US may not work in Japan or Brazil. Test messaging with local audiences before full launch. Use region-specific keyword research to inform ad copy and landing pages. Monitor pricing parity complaints and adjust strategy if customers perceive unfairness.","q":"How do I adapt pricing and marketing for international markets?"}],"shadow_tags":["multi-region-seo","global-product-launch","language-switching","market-adaptation","cross-border-pricing","url-canonicalization","regional-compliance","content-localization","geo-targeting"],"summary_rewrite":"Localization-strategy guides SaaS and AI products through structured global expansion beyond simple translation. It covers market prioritization, i18n technical implementation (URL structure, hreflang, metadata), keyword research by region, and pricing adaptation strategies. The skill includes checklists for launching new features across locales and onboarding entirely new markets while avoiding common pitfalls like batch publishing penalties and hreflang misalignment."},"files":[{"bytes":6257,"path":"skills/strategies/commercial/localization/SKILL.md","sha256":"8973549520bf13c12e6d6ce921a93ed32a2b8499a45d26e8689c70c8acecc690","url":"https://skillfed.io/files/kostja94/marketing-skills/localization/ea7680bd/SKILL.md"}],"id":"kostja94/marketing-skills/localization","links":{"html":"https://skillfed.io/kostja94/marketing-skills/localization","md":"https://skillfed.io/kostja94/marketing-skills/localization.md","repo":"https://github.com/kostja94/marketing-skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":109,"language":null,"last_updated":"2026-06-09","license":"MIT","name":"localization-strategy","publisher":"kostja94","stars":762},"relations":{"similar":[{"id":"kostja94/marketing-skills/translation"},{"id":"kostja94/marketing-skills/metadata"},{"id":"daffy0208/ai-dev-standards/localization-engineer"},{"id":"kostja94/marketing-skills/description"},{"id":"OpenClaudia/openclaudia-skills/i18n"},{"id":"kostja94/marketing-skills/title"},{"id":"oakoss/agent-skills/localization-engineer"},{"id":"kostja94/marketing-skills/sitemap"},{"id":"rampstackco/claude-skills/internationalization"},{"id":"littleben/awesomeAgentskills/internationalizing-websites"}]},"slug":{"owner":"kostja94","repo":"marketing-skills","skill":"localization"},"version":"ea7680bd"}