Deciding between language targeting and region targeting
Teams reflexively reach for region codes (es-MX, es-AR) when plain language (es) would serve better — or vice versa. The choice should follow content differentiation, not instinct. A test:
— Ask: does this page *differ* by country, or only by language? Different currency, shipping, legal, local examples → region. Same Spanish text for all of Latin America → language-only.
— If pages don't materially differ, region codes create near-duplicate clusters competing with each other. Use language-only and let Google's geotargeting and the user's own signals split the markets.
— If they do differ, region targeting is justified — but then the *content* must justify it. Identical text under es-MX and es-CO is a duplicate-content liability wearing a targeting costume.
— Special case: there is no region code for "Latin America." Use es-419 (the UN M49 region for Latin America/Caribbean) — Google supports it, many teams don't know it exists.
In a comparison of 8 multi-country Spanish sites, those using language-only where content was identical had fewer cannibalization issues than those that over-segmented by region. The data suggests over-segmentation is the more common error.
Unknown: the exact threshold of "differentiation" Google requires to treat region variants as distinct rather than duplicate. We have heuristics, not a published rule — so when in doubt, consolidate.
Hreflang Lab
@HreflangLab
Deciding between language targeting and region targeting
Этот пост опубликован в Telegram-канале Hreflang Lab. Подписаться можно по ссылке: @HreflangLab.