International SEO

TL;DR — International SEO is how you tell search engines which languages and countries your site is for, so the right person sees the right version. It’s two separate questions — what language is this page in, and what country is it for — and three main levers: your URL structure, hreflang tags, and on-page signals like currency and address. hreflang is the big one, and the thing to remember up front is that it’s a hint, not a command.

What international SEO is

If your site serves people in more than one language or more than one country, you have an international SEO problem to solve — whether you’ve thought about it or not. The goal is simple to state: help Google and Bing understand which version of a page is meant for which audience, and serve that version to the right person.

The mistake almost everyone makes at the start is treating “language” and “country” as the same thing. They aren’t:

• Language targeting is for multilingual sites — the same content offered in more than one language.
• Country targeting is for multi-regional sites — content aimed at users in different countries, sometimes in the same language.

Quick examples to make it stick: Canada is one country with two official languages (English and French) — that’s language targeting inside one country. The US and UK are two countries that mostly share a language — that’s country targeting with the same language. Plenty of big sites need both at once.

The three things you actually control

1. URL structure. Where the localized versions live:
   • ccTLD — example.de for Germany, example.fr for France. Strongest “this is for that country” signal, but expensive and harder to manage.
   • Subdomain — de.example.com. Easy to set up.
   • Subdirectory — example.com/de/. Low maintenance, everything under one domain. For most sites, this is what I’d pick.
2. hreflang. A small tag that says “this URL is the German version, that one is the French version.” It’s what lets Google show a UK visitor the UK page even when the US page is the one that technically ranks.
3. On-page signals. Currency, address, phone number, language of the text, links from local sites. These quietly reinforce who a page is for. Evidence for this claim Google supports locale-specific URLs and hreflang, and also considers ccTLDs and several page, server, and local-link signals when identifying an intended audience. Scope: Google Search locale guidance; these are signals rather than guaranteed targeting controls. Confidence: high · Verified: 2026-07-14 Google: Managing multi-regional and multilingual sites

The one thing to get right early

hreflang is a hint, not a directive. You can set it perfectly and Google can still decide to show a different version, or fold two near-identical language pages into one. Its real job isn’t to force anything — it’s to swap in the right regional version in the search results when it can. Set it up correctly anyway, because when it’s broken that swapping doesn’t happen at all.

Also know two things that have changed: Google removed the old “International Targeting” report from Search Console back in 2022, so you don’t set country targets there anymore. And Bing doesn’t really run on hreflang — it prefers a different tag (more on both in the Advanced version).

Want the deeper version — how to choose your URL structure, hreflang at scale, why the ccTLD advantage is fading, and how Bing differs — switch to the Advanced tab. Each subtopic (hreflang, x-default, translation vs. localization, keyword research, auditing, and multilingual SEO) has its own deep dive linked from there.

Test yourself: International SEO

TL;DR — International SEO runs on two axes (language vs. country) and three levers (URL structure, hreflang, on-page signals). hreflang is a hint: its payoff is version-swapping in the SERP, not indexing, and Google will override it. The ccTLD ranking boost — Google’s LDCP algorithm — is fading (Gary Illyes, July 2024). The GSC International Targeting report was deprecated in 2022. Bing leans on the content-language meta tag, treating hreflang as “a far weaker signal.” At enterprise scale, manual hreflang will fail — automate generation and monitor constantly. My defaults: subdirectories and one page per language. Gate market entry on demand, eligibility, capacity, competition, and economics before picking architecture — and none of this guarantees indexing, rankings, or traffic; it just improves the odds engines match locale versions correctly.

Two axes, not one

The single most useful distinction in this whole topic is that language targeting and country targeting are different things. Google’s own docs draw the line cleanly: “Multilingual websites are those that offer content in more than one language,” while “Multi-regional websites are those that explicitly target users in different countries.” You can need one, both, or neither.

Gary Illyes put the trap bluntly: “The language is absolutely not a tell for what country you are targeting.” A French page could be for France, Canada, Belgium, or Switzerland. If you care about country, you have to signal country explicitly — a region code in your hreflang (fr-CA, not just fr) or a ccTLD. Language alone doesn’t do it. And the HTML lang attribute is no help: Illyes’ example was a site where “Joomla just came with the Lang attribute set to English… And then you looked at the page, and it was 100% German.” Engines learned long ago not to trust it.

None of this axis-mapping is a guarantee mechanism, and it’s worth saying plainly: getting the language/country distinction and the technical signals right can improve how well Google and Bing match locale versions to searchers, but it doesn’t promise indexing, rankings, traffic, conversions, a specific displayed locale, or citations in AI answers for any one page. The signal list below comes with its own documented limits on what does and doesn’t count.

Prioritize the market before you lock architecture

Before you commit to a URL structure, gate the market itself — architecture is expensive to undo, and picking it before you know the market is worth entering is backwards. The practical checklist I use: search demand in that language/country, whether your product or service is actually eligible to sell or operate there, whether you have the operational capacity to support it (support, legal, payments, fulfillment), how competitive the market already is, and whether the unit economics work once you convert. Treat Ahrefs-style traffic and keyword-volume numbers as estimates for sizing and comparing markets against each other; treat your own Google Search Console or analytics rows as observed first-party data once you’re already live somewhere similar. Skipping this gate is how teams end up with an expensive ccTLD in a market that was never going to convert. The international SEO keyword research page covers the market-by-market research workflow in depth.

Choosing your URL structure

This is the one architectural decision that’s expensive to undo, so it’s worth getting right. Google uses several signals to work out your target locale — ccTLD, hreflang, server location, and on-page signals like local addresses, phone numbers, currency, and local site links — but URL structure is the one you commit to in infrastructure.

My default for most sites is the subdirectory. It keeps all your authority under one domain instead of splitting it across separate ccTLDs, and it’s far less to maintain. John Mueller has said for years that “subdomains and subdirectories are essentially equivalent” from Google’s side, so the deciding factors are usually operational, not magical SEO ones — pick what fits your stack and your long-term plan. That’s practitioner guidance from running this at scale, not a universal Google ranking rule — Google’s own documentation lists tradeoffs for each option and doesn’t declare one structure the winner.

The big caveat is the ccTLD story. ccTLDs are still the strongest country signal — Google calls them “a strong signal… about the target country of a website” — but that advantage is shrinking. Gary Illyes, on Search Off the Record in July 2024, described the underlying mechanism and its decline: “One of the main algorithms… is called something like LDCP — language demotion country promotion… But nowadays… it doesn’t really make sense for us to like automatically apply that little boost because it’s ambiguous.” He went further: “I think eventually, like in years’ time, that [ccTLD benefit] will also fade away,” because “think about all the funny domain names that you can buy… It doesn’t say anything anymore about the country.” His practical advice matched mine — there’s still marketing value in a ccTLD, “but I would not worry too much about it” for ranking. Google has even been redirecting its own country ccTLDs to google.com.

hreflang: the core technical signal

hreflang is the workhorse of international SEO, and it’s the thing I’ve spent more time on than almost any other technical topic — it was one of my first contributions when I joined Ahrefs, editing our hreflang guide.

What it actually does. hreflang tells Google (and Yandex) which language/region a URL is meant for. Its real benefit is version-swapping in the SERP: a UK visitor can be shown your en-gb page even when the en-us page is what ranks, provided hreflang is set up correctly. When the tags are broken, that swapping just doesn’t happen. What hreflang does not do is guarantee indexing or override canonicalization — it’s one of roughly 19 canonicalization signals, not a trump card.

Three implementation methods, all equivalent: <link rel="alternate" hreflang="…" href="…" /> tags in the <head>; an HTTP Link: header; or <xhtml:link> entries in your XML sitemap. There’s no inherent speed difference — the signals are checked at crawl time either way, so use whichever your stack generates most reliably. (On a mixed ccTLD-plus-.com setup, centrally-hosted XML sitemaps are the usual way to manage cross-domain clusters.)

The golden rules:

• Bidirectional / reciprocal. If page X points to page Y, Y must point back to X. hreflang works in clusters — a set of pages all referencing each other — and a cluster only forms when the links are reciprocal. This is also how signal-sharing works across the cluster: the strongest page can lift the others.
• Self-referencing is best practice but, per Mueller, technically “optional.”
• x-default is your fallback for users whose language/region doesn’t match any specific version.
• Use real region codes. en-GB, fr-BE, zh-Hans — ISO 639-1 language plus an optional ISO 3166-1 region. There are no EU, LATAM, APAC, or MENA region codes; you target individual countries (es-MX, es-AR, es-CO).

Common errors are everywhere. In the Ahrefs hreflang study I worked on — the largest ever done, across 374,756 hreflang-using domains — 67% had at least one issue. My honest reaction at the time: “I’m surprised the numbers weren’t worse… I suspect a lot of these sites have basic implementations.” The point stands: “Hreflang is complex and hard to get right. It can break in so many different ways.”

hreflang is a hint, not a directive. This is the line people most need to internalize. As Mueller put it (Bluesky, May 2025): “hreflang doesn’t guarantee indexing… if they are the same (eg fr-fr, fr-be), it’s common that one is chosen as canonical.” And: “Often hreflang will still swap out the URL, but reporting will be on the canonical URL.” So Google may consolidate near-identical language variants, and your reporting will sit on whichever URL it picked as canonical.

Other signals — and the things Google ignores

Beyond hreflang and ccTLD, Google reads on-page localization: local currency, addresses, phone numbers, the language of the body text, and links from local sites. Two things it explicitly does not use: geolocation meta tags (geo.position, geo.region, geo.placename) and IP-based location analysis, which it calls “not reliable.”

It helps to keep straight which job each signal is actually doing, because they get blended together constantly: language detection comes from the page’s visible content, not from code-level data or the URL — Google determines it by reading what’s actually on the page. Locale targeting (which country a page is for) is signaled by ccTLD, hreflang, server location, and the on-page cues above — though Google is explicit that server location alone “is not definitive.” hreflang does a narrower job than either of those: it maps alternate locale URLs to each other so the right one can be swapped into results; it does not declare a page’s language. And canonicalization is the separate decision about which URL actually gets indexed and ranked — hreflang feeds into it but doesn’t control it outright.

A trap to avoid: don’t auto-redirect users by IP. Google’s guidance is to “avoid automatically redirecting users to a different language version based on their perceived geographic location.” Geo-redirects trap the crawler in whatever locale it appears to originate from, so Google never sees your other versions — and in the EU, IP-based geoblocking can run into the Anti-Geoblocking Regulation. Use separate, stable URLs per language, keep them directly reachable (no locale-only paths that vanish once you leave the “right” region), and give users explicit links to switch language or region themselves rather than guessing on their behalf. Same reasoning kills cookie-based or Accept-Language-based content switching: Google recommends “using separate locale URL configurations” with hreflang instead of locale-adaptive pages, because Googlebot doesn’t set Accept-Language headers by default and commonly crawls from US-based infrastructure — so a response that adapts based on perceived location or headers may simply never be seen in its other locales at all.

The GSC International Targeting report is gone

If a guide tells you to set your country target in Search Console, it’s out of date. Google deprecated the International Targeting report on September 22, 2022, stating the country-targeting feature “was determined to have little value for the ecosystem, and is no longer supported.” What replaced it? Nothing direct — country targeting is now inferred from ccTLD + hreflang + on-page signals + inbound links. The hreflang error data that used to live in that report is also gone from GSC, so you validate hreflang with a crawler now. Google did confirm it “will continue to support and use hreflang tags.” To check which version Google actually indexed for a page, use the URL Inspection tool.

How Bing handles this differently

This is where most guides either skip Bing or get it wrong — and I’ve had the benefit of being on a panel with Bing’s Fabrice Canel to hear it firsthand. Bing’s signal stack is genuinely different from Google’s. Canel’s own words: “hreflang is indeed a far weaker signal than content-language at Bing.”

Bing’s preferred signals, in rough priority order:

1. <meta http-equiv="content-language" content="fr-FR"> — the content-language meta tag
2. The Content-Language HTTP header
3. ccTLD / server location
4. Body-text language
5. Locale of inbound linking pages

So the cross-engine recipe is: implement hreflang for Google, and add content-language meta tags for Bing. Bing will read hreflang, but treats it as weak. And unlike Google (which killed its own targeting report in 2022), Bing removed its Geo Targeting feature too — Fabrice Canel confirmed in September 2020 that it did not carry over to the redesigned Bing Webmaster Tools, telling SEOs to use the content-language meta tag or HTTP header instead.

Other engines need their own workflow

Google versus Bing is not the whole international map. Once a market depends on another engine, keep the shared content and technical foundation but verify the provider-specific workflow instead of translating a Google checklist:

The details belong in the market-specific SEO guides. The useful rule here is simpler: shared SEO principles travel; product controls, submission paths, diagnostics, and undocumented behavior do not.

International SEO at scale

I ran international SEO at IBM, on one of the largest enterprise sites in the world — multiple CMSs, multiple infrastructures, tens of millions of URLs. The single biggest lesson: manual hreflang management fails at scale. You cannot hand-curate reciprocal tags across millions of pages and multiple systems. What works:

• Automate everything possible. Generate hreflang from a system of record — often middleware connecting your CMSs — rather than letting each team hand-write tags.
• Check repeatedly. Problems emerge constantly; this is a constant crawl + alerts job, not a once-a-quarter audit. Expect breakage and build systems to catch it.
• Watch for “head section breaks.” hreflang tags pushed into the <body> by malformed HTML are ignored — verify they’re in the rendered <head>.
• Verify the indexed URL per locale with GSC’s URL Inspection, because hreflang’s effectiveness depends on which version actually got indexed, not just what your canonical tag says.

Architecturally, my preference at scale is one page per language rather than one page per country/locale — it produces fewer, stronger pages, enables dynamic personalization, and sidesteps a lot of hreflang complexity. Patience matters too: international changes move at the speed of crawl cycles, not at the speed your stakeholders want.

Where to go next

This hub is the map. Each subtopic below is its own deep dive:

Hreflang (its own section in the sidebar)

• hreflang — the tag in full: the three implementation methods, clusters, reciprocity, common errors, and validation.
• x-default hreflang — the fallback value for users whose language/region matches none of your versions, and where it actually helps.

Localization, content, and audits

• translation vs. localization — why machine-translating pages isn’t the same as localizing for a market, and what Google’s auto-translation guidance means for you.
• international SEO keyword research — researching demand market-by-market, where the same language differs by country (the classic “ibis” vs. “bin chicken” gap).
• international SEO audit — how to crawl, validate, and debug hreflang clusters and locale signals across a multi-market site.
• multilingual SEO — the language-targeting half of the discipline in depth.

AI summary

A condensed take on the Advanced version:

• International SEO = telling engines which language and/or country each page is for, so the right version reaches the right user. Two axes — language targeting (multilingual) vs. country targeting (multi-regional) — and three levers: URL structure, hreflang, on-page signals.
• None of this guarantees outcomes. Getting the axes and signals right improves how well engines match locale versions to searchers — it doesn’t promise indexing, rankings, traffic, conversions, a specific displayed locale, or AI citations.
• Gate the market before the architecture. Prioritize on search demand, product/ service eligibility, operational capacity, competition, and unit economics. Treat Ahrefs-style volume/traffic numbers as estimates for sizing markets; treat your own GSC/analytics rows as observed data once you’re live somewhere similar.
• Language ≠ country. “The language is absolutely not a tell for what country you are targeting” (Gary Illyes). To target a country, use a region code (fr-CA) or a ccTLD; the HTML lang attribute is unreliable.
• URL structure: ccTLD (strongest country signal, but expensive + splits authority) / subdomain (easy) / subdirectory (consolidates authority, low maintenance). Patrick’s default: subdirectory. Subdomains and subdirectories are “essentially equivalent” to Google.
• ccTLD advantage is fading. Google’s LDCP (language demotion country promotion) boost is being de-emphasized; Illyes (July 2024): it “will also fade away.” Marketing value remains; ranking value doesn’t.
• hreflang is a hint, not a directive. Payoff = version-swapping in the SERP, not indexing. It’s ~1 of 19 canonicalization signals. Rules: reciprocal/bidirectional clusters, self-reference (optional but good), x-default, real region codes (no EU/ APAC). 67% of 374,756 domains had hreflang issues (Ahrefs study).
• Each signal has a distinct job: language detection reads visible content (not code/URL); locale targeting comes from ccTLD/hreflang/server location/on-page cues; hreflang maps alternate URLs (doesn’t declare language); canonicalization decides the indexed URL. Don’t auto-redirect by IP (traps the crawler; EU Anti-Geoblocking risk) — use stable separate URLs, explicit switcher links, and hreflang instead of locale-adaptive pages. Google ignores geo meta tags and IP analysis.
• GSC International Targeting report deprecated Sept 22, 2022 — “little value for the ecosystem.” Country targeting now inferred from ccTLD + hreflang + on-page + links. hreflang still supported.
• Bing differs: “hreflang is a far weaker signal than content-language at Bing” (Fabrice Canel). Bing prioritizes the content-language meta tag + HTTP header. Bing removed its own Geo Targeting feature from Bing Webmaster Tools in 2020.
• Other engines stay separate: Naver and Yandex have their own webmaster workflows and participate in IndexNow; Cốc Cốc documents its own crawler, submission form, sitemap discovery, and directives. Do not infer undocumented behavior from Google.
• At scale (IBM): manual hreflang fails — automate generation via middleware, monitor constantly, verify the indexed URL per locale. One page per language = fewer, stronger pages.

Official documentation

The primary-source docs that govern international targeting at each engine.

Google

• Managing multi-regional and multilingual sites — the core doc: the language-vs-country definitions, URL structure options, and the full list of locale signals Google uses.
• Localized versions of your pages (hreflang) — the three implementation methods, the bidirectional requirement, self-reference, x-default, and valid language/region codes.
• International SEO overview — the top-level index for Google’s international guidance.
• Locale-adaptive pages — why dynamically served locale content is risky, and the recommendation to use separate URLs + hreflang instead.
• x-default hreflang announcement (April 2013) — the original introduction of the x-default fallback value.
• International Targeting report deprecated — the 2022 deprecation notice: country targeting “had little value for the ecosystem”; hreflang continues to be supported.

Bing / Microsoft

• Bing Webmaster Guidelines — Bing’s signal priorities, including the content-language meta tag and HTTP header.
• Going International (Bing Webmaster Blog, 2009) — foundational and still-cited: ccTLD as a primary signal, and the warnings against JS- and cookie-based language switching.
• Bing Webmaster Tools Removes Geo-Targeting Feature (Search Engine Roundtable, Sept 2020) — Fabrice Canel confirms the old Geo Targeting feature was not carried over to the redesigned Bing Webmaster Tools.

Quotes from the source

On-the-record statements from Google and Bing that frame how international targeting actually works.

Google — language vs. country, and ccTLDs

• “Multilingual websites are those that offer content in more than one language.” / “Multi-regional websites are those that explicitly target users in different countries.” — Google Search Central docs. Jump to quote
• “Country-specific domains (ccTLDs) provide a strong signal to both users and search engines about the target country of a website.” — Google Search Central docs. Jump to quote
• “The language is absolutely not a tell for what country you are targeting.” — Gary Illyes, Google (Search Off the Record, July 2024). Read the coverage
• “One of the main algorithms… is called something like LDCP — language demotion country promotion… nowadays… it doesn’t really make sense for us to like automatically apply that little boost because it’s ambiguous.” — Gary Illyes, Google (July 2024). Read the coverage
• “I think eventually, like in years’ time, that [ccTLD benefit] will also fade away.” — Gary Illyes, Google (July 2024). Read the coverage

Google — hreflang and URL structure

• “hreflang doesn’t guarantee indexing… if they are the same (eg fr-fr, fr-be), it’s common that one is chosen as canonical.” — John Mueller, Google (Bluesky, May 2025). Read the coverage
• “Often hreflang will still swap out the URL, but reporting will be on the canonical URL.” — John Mueller, Google (May 2025). Read the coverage
• “From our point of view… subdomains and subdirectories are essentially equivalent.” — John Mueller, Google. Read the coverage

Google — the deprecated report

• “The ability to target search results to specific countries using Search Console country targeting was determined to have little value for the ecosystem, and is no longer supported.” — Google Search Console Help. Jump to quote

Bing / Microsoft

• “hreflang is indeed a far weaker signal than content-language at Bing.” — Fabrice Canel, Microsoft Bing. Read the coverage

The decision frameworks

1. Do you need language targeting, country targeting, or both?

Start here, because it determines every signal downstream.

• Same content in multiple languages, audience defined by language → language targeting (multilingual). hreflang with language codes (de, fr, ja).
• Same/similar content aimed at specific countries → country targeting (multi-regional). hreflang with region codes (en-GB, en-US) and/or ccTLDs.
• Both (e.g. French and English, each split by country) → region-coded hreflang (fr-CA, fr-FR, en-CA, en-US).
• The trap: language alone never implies country. If country matters, signal it explicitly.

2. ccTLD, subdomain, or subdirectory?

Work down the list; stop at the first that fits.

1. Subdirectory (example.com/de/) — my default. Choose it unless you have a specific reason not to: it consolidates authority, is cheapest to run, and Google treats it as equivalent to a subdomain.
2. Subdomain (de.example.com) — choose it when infrastructure or org structure makes separate hosts genuinely easier, and you accept it may be treated more like a separate site.
3. ccTLD (example.de) — choose it when brand/marketing/legal reasons demand a local domain (local trust, country requirements), not for the SEO boost — that LDCP advantage is fading. Budget for the cost and the split authority.
4. URL parameters — don’t. Not recommended for locale.

3. Match the signal or product to the job

Do not flatten language detection, locale mapping, canonicalization, and submission into one “priority” stack.

For Bing specifically, retain the provider-scoped content-language guidance above. Do not call hreflang Google’s language detector: its job is mapping alternate URLs after Google has read the visible content.

4. The “is my hreflang even working?” check

• Reciprocity: does every page in the cluster point back? (No cluster, no swap.)
• Self-reference present (best practice) and an x-default fallback set?
• Valid codes only — real ISO language/region, no EU/APAC/LATAM.
• Tags in the rendered <head>, not pushed to <body>.
• Confirm the actual indexed URL per locale via GSC URL Inspection — hreflang rides on whichever version got indexed.

Resources worth your time

My talks

• You’re Going To Screw Up International SEO — Pubcon Vegas 2017 — the IBM-era talk: international SEO breaks constantly, so expect problems and build systems to catch them. Automate everything; check repeatedly.
• International SEO: The Weird Technical Parts — Pubcon Vegas 2019 — hreflang clusters, sitemap vs. HTML (no speed difference), what Google tolerates, head-section breaks, and the dangers of auto-redirects.
• Hreflang Study and Interesting Issues — Brighton SEO 2023 — the version-swapping mechanic, hreflang as one of ~19 canonicalization signals, and “one page per language” as the simplifying architecture.
• International SEO Simplified — Outspoken Media panel (Nov 2023) — a panel with Bing’s Fabrice Canel and Bill Hunt on centralized vs. decentralized management, automation, and how Bing and Google differ.

My writing

• The largest-ever hreflang study — 374,756 hreflang-using domains, 67% with at least one issue, co-authored with Oleksiy Golovko.
• Hreflang Tags: The Easy Guide for Beginners — the guide I edited as one of my first Ahrefs contributions; the hreflang-cluster framing and a semi-automation template.

Tools I use for international work

• Ahrefs Site Explorer — traffic and ranking keywords by country, for sizing a market and reading competitors’ per-market strategy.
• Ahrefs Keywords Explorer — keyword research by country and language, with an AI Translator across 40+ languages; the tool that surfaces same-language-different-market gaps (the “ibis” vs. “bin chicken” example).
• Ahrefs Site Audit — crawls for nine categories of hreflang issues and visualizes the clusters for debugging.

From others

• International SEO: Everything you need to know — Motoko Hunt’s comprehensive guide at Search Engine Land.
• International SEO best practices — the Ahrefs checklist-style guide by Jamie Grant and Despina Gavoyannis.
• Hreflang Implementation — The 10 Biggest SEO Misconceptions — Motoko Hunt at Search Engine Journal; covers the “only homepage needs hreflang” and self-reference myths, with Mueller citations.
• Google Hints at Lowering SEO Value of ccTLDs — Search Engine Journal coverage of Gary Illyes’ July 2024 Search Off the Record episode on the LDCP algorithm fading.
• Google Reminds That hreflang Tags Are Hints, Not Directives — Search Engine Journal coverage of John Mueller’s May 2025 Bluesky thread on hreflang canonicalization.
• Bing: hreflang Is a Far Weaker Signal Than content-language — SE Roundtable coverage of Fabrice Canel’s statement on Bing’s signal priority stack.
• Search Off the Record: Internationalization and hreflang (July 2024 episode summary) — International Web Mastery’s detailed write-up of the Gary Illyes + Martin Splitt podcast episode, including the language-vs-country distinction and hreflang crawl dependency.

International SEO

International SEO is the practice of optimizing a site so search engines understand which countries and/or languages it targets, and serve the right version to each user. It spans URL structure, hreflang, and on-page localization.

Related: Hreflang, Multilingual SEO, x-default

International SEO

International SEO is the process of optimizing a website so search engines understand which countries and/or languages it’s targeting, and serve the most relevant version to each user. It works across two overlapping dimensions: multilingual sites offer content in more than one language (language targeting), and multi-regional sites explicitly target users in different countries (country targeting). A site can be one, both, or neither — Canada is one country with two official languages; the US and UK are two countries sharing one.

The distinction is technical, not just conceptual. Language targeting is governed by hreflang language codes; country targeting is governed by ccTLDs, URL structure, and on-page signals like currency, address, and local links. The three core technical levers are URL structure (ccTLD vs. subdomain vs. subdirectory), hreflang annotations, and on-page localization.

Two things trip people up most. First, hreflang is a hint, not a directive — Google can and does override it, and its main benefit is “version swapping” in search results rather than guaranteed indexing. Second, the Google Search Console International Targeting report was deprecated in 2022, so country targeting is now inferred from ccTLD, hreflang, and on-page signals rather than set directly. Bing handles all of this differently, leaning on the content-language meta tag far more than hreflang.

Related: Hreflang, Multilingual SEO, x-default

Changelog