Language targeting

Long definition

Most international SEO advice jumps straight to locale targeting (en-US, en-GB, es-MX). Language targeting — hreflang="en", hreflang="es" — is the simpler alternative that's right more often than people assume.

The decision tree:

• One page in a language, no regional differences. Use language targeting. hreflang="en" covers every English speaker without forcing a country choice. A SaaS product page with USD pricing and global terms of service usually fits here, especially for B2B tools sold internationally on a single price.
• Different pages per region of the same language. Use locale targeting. hreflang="en-US", hreflang="en-GB", hreflang="en-AU" route users to the right regional version. Pricing in local currency, local legal pages, regional phone numbers all push toward locale.
• Mixed: one English version for most of the world, plus a UK-specific version. A common pattern. Use language-only en for the global page and en-GB for the UK page. Google routes UK users to en-GB and everyone else (including US, AU) to the language-only version. x-default should also point somewhere sensible for users whose locale doesn't match anything.

Implementation example for a single-language-targeted page:

<link rel="alternate" hreflang="en" href="https://example.com/en/page" />
<link rel="alternate" hreflang="es" href="https://example.com/es/page" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en/page" />

The benefit: fewer URLs, simpler hreflang clusters, less content duplication, less hreflang validation overhead. The cost: you can't tailor a US visitor differently from a UK visitor — they both see the same English page.

A common antipattern is forcing locale targeting when language alone is enough. A SaaS company with three locale variants (en-US, en-GB, en-AU) and identical content on each is fragmenting authority across three URLs and burning hreflang complexity for no user-facing differentiation. The cleaner setup is one en page plus an x-default.

When users explicitly need a regional variant later (US-specific pricing, UK-specific legal page) the migration from language to locale targeting is straightforward — split the new page into a locale variant, leave the rest on language targeting. Hreflang clusters can mix granularities.

Common misconceptions

• "Always use locale targeting to be safe." Adds complexity and fragments authority when content doesn't actually vary. Use the simplest targeting that fits the actual content.
• "hreflang='en' means English-language users in any country." Correct. There's no implicit country in language-only targeting; Google routes any English-locale user to the en page when no more-specific match exists.
• "You must use either language OR locale across the whole site." You can mix. A site can have language-targeted homepage and locale-targeted pricing pages, as long as each hreflang cluster is internally consistent.
• "Language targeting hurts SEO compared to locale." It doesn't. The right targeting for the content beats the more granular one. Mismatches (locale targeting on identical content) cause more problems than language-only setups do.