ot-geo-i18n-strategy

Defines i18n strategy and implementation requirements for bilingual EN/PL marketing sites with location-based language selection.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/triage-software/skills --skill ot-geo-i18n-strategy-triage-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ot-geo-i18n-strategy
Source: https://github.com/triage-software/skills/tree/main/skills/ot-geo-i18n-strategy
Command: npx skills add https://github.com/triage-software/skills --skill ot-geo-i18n-strategy-triage-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Retrofitting language routing into a finished landing page is a classic budget trap. This Skill locks the i18n decisions before design begins, covering URL structure, locale detection, hreflang, and per-locale content strategy for bilingual EN/PL marketing sites. ## Core Features & Use Cases - Decision Framework: Locks URL structure (default locale at /, secondary at /pl/), first-visit-only detection via Accept-Language, and a persistent visible language toggle. - SEO Requirements: Specifies hreflang pairs (en, pl-PL, x-default) and indexability rules so both locale versions rank without JS-only swaps. - Per-Locale Proof Strategy: Directs market-specific evidence per locale (PLN pricing and EU data residency for PL; GitHub stars and benchmarks for EN) rather than literal translation. - Use Case: When building a bilingual landing page, use this Skill to hand the implementer concrete build requirements — framework-native i18n routing, namespaced key files, locale-aware formatting, and acceptance checks. ## Quick Start Use the geo i18n strategy skill to define the URL structure, redirect rules, and hreflang setup for my bilingual EN/PL marketing site.

Frequently Asked Questions about ot-geo-i18n-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure URLs for a bilingual EN/PL website?▼

Serve the default locale (EN for global audiences) at the root path and the secondary locale in a path prefix like /pl/. Avoid subdomains and query parameters so both locale versions remain cleanly indexable.

How to redirect visitors based on browser language without trapping them?▼

Detect language only on first visit via the Accept-Language header or navigator.language, redirect once to /pl/ for pl-* users with a dismissible banner, and always provide a visible EN/PL toggle persisted in a cookie.

What hreflang tags does a bilingual EN/PL site need?▼

Every page needs an hreflang pair: en (self and alternate), pl-PL, and x-default pointing to EN. Both locale versions must be server-rendered and indexable rather than swapped via JavaScript only.

Should marketing copy be translated or written per locale?▼

Copy should be written per locale, not translated. Brief the copywriter in the target market's own number-led language patterns and localize proof points, such as PLN pricing for PL and GitHub stars for EN.

Why does client-side language detection cause problems?▼

Client-only detection causes locale flicker because the page renders in one language before switching. Server-side redirects based on the Accept-Language header are preferred for a stable first render.