<b>SOP: Language-based routing inside a geo</b>
Purpose: serve the landing in the user's language, not just the country's official one.
☐ Step 1 — Read the browser Accept-Language header first; it beats geo for actual language.
☐ Step 2 — Fall back to geo language only when the header is missing or generic.
☐ Step 3 — Handle multilingual geos explicitly: Canada (EN/FR), Switzerland (DE/FR/IT), Belgium (NL/FR).
☐ Step 4 — Map dialects sensibly — pt-BR and pt-PT are different offers; es-MX and es-ES too.
☐ Step 5 — Keep an English fallback landing for every geo; unmapped languages still need to convert.
☐ Step 6 — Test by spoofing the header, not just the IP. They disagree more than you'd expect.
The header is the better signal. Confirm your tracker actually reads it.
Review language coverage when you add geos.
Smartlink Ops
@SmartlinkOps
<b>SOP: Language-based routing inside a geo</b>
Этот пост опубликован в Telegram-канале Smartlink Ops. Подписаться можно по ссылке: @SmartlinkOps.