Guide International SEO Checklist

A build-and-launch international SEO checklist — Structure d’URL, hreflang, geotargeting après the GSC deprecation, crawlable switchers, and duplicate-content handling.

Première publication : 2 juil. 2026 · Dernière mise à jour : 3 août 2026 · Advanced
Langues

Ce is the construire/launch checklist pour a site que targets plus que un country and/or language — the sequence to fonctionner via quand setting un up, as opposed to auditing un that's déjà live. Decide votre Structure d’URL une fois and appliquer it consistently (ccTLD vs. subdomain vs. subdirectory; Google marks URL-parameter language switching 'Pas recommended'). Implement hreflang with self-references, retourner tags, and x-default in whichever delivery méthode fits votre stack — HTML head, HTTP header, and XML sitemap are equivalent to Google. Localize, don't machine-translate. Know que the GSC International Targeting report was entièrement supprimé in September 2022, so country targeting is now inferred from ccTLD + hreflang + on-page + lien signals with aucun manual override. Faire language/currency switchers réel crawlable liens, jamais JS-only dropdowns, and jamais auto-redirect by IP. Near-identical regional variants besoin canonical AND hreflang ensemble, pas canonical alone. Bing weights le contenu-language meta tag over hreflang and apparaît to have supprimé its propre Geo Targeting fonctionnalité.

TL;DR — Ce is the construire/launch sequence, pas an audit. (1) Structure d’URL: ccTLD (strongest country signal, un country chaque, la plupart overhead), subdomain, or subdirectory (easiest, la plupart courant) — Google marks l’URL-parameter approach “Not recommended.” Pick un, appliquer consistently. (2) hreflang: self-reference, reciprocal retourner tags, x-default, valid ISO codes; HTML head, HTTP header, and XML sitemap are equivalent delivery méthodes — choisir pour votre stack, sitemap scales meilleur. (3) Localize, don’t machine-translate. (4) Geotargeting: the GSC International Targeting report was entièrement supprimé September 22, 2022 pour tout TLD types — là is aucun manual country target anymore; ccTLD + hreflang + on-page + lien locale is ce que Google infers from now. (5) Switchers doit be crawlable <a href> liens, jamais JS-only, and don’t auto-redirect by IP. (6) Near- identical regional variants: canonical + hreflang together, and Google may encore consolidate les anyway. (7) Validate reciprocity, codes, x-default, and rendered-head placement avant and après launch. Bing weights content-language over hreflang and apparaît to have supprimé its propre Geo Targeting fonctionnalité.

Evidence for this claim Google recommends distinct URLs for language versions and documents ccTLD, subdomain, and subdirectory structures while marking URL parameters as not recommended. Scope: Google Search international URL guidance. Confidence: high · Verified: Google: Locale-specific URLs Evidence for this claim Google recommends hreflang for distinct language URLs, warns against automatic language redirects, and recommends crawlable links between versions. Scope: Google Search multilingual-site discovery and switching guidance. Confidence: high · Verified: Google: Managing multilingual versions

How ce differs from the audit

The international SEO audit is a diagnostic methodology — how vous trouver what’s broken on a site que déjà has international SEO live, complet with the cluster-graph tooling and my 374 756-domain hreflang study’s error breakdown. Ce checklist is the autre half: the sequence I fonctionner via quand setting up or reviewing a nouveau build. So I’ll garder the hreflang error-frequency tables and outil walkthroughs over là and stay action-oriented ici, and I’ll route conceptual depth to the international SEO hub plutôt que re-deriving it.

Step 1 — Choisir votre Structure d’URL

Google’s propre documentation lays out the structures with explicit pros and cons, and it’s worth working from leur table plutôt que folklore:

StructureExemplePros (Google’s words)Cons (Google’s words)
ccTLDexample.de”Clear geotargeting”; “Server location irrelevant""Expensive (can have limited availability)”; “Can only target a single country”
Subdomain + gTLDde.example.com”Easy to set up”; “Easy separation of sites""Users might not recognize geotargeting from the URL alone”
Subdirectory + gTLDexample.com/de/”Easy to set up”; “Low maintenance (same host)""Single server location”; “Separation of sites harder”
URL parametersexample.com?loc=de“Not recommended”

The ccTLD is encore the strongest country signal Google has — its propre doc dit “Country-specific domains (ccTLDs) provide a strong signal to les deux utilisateurs and search engines à propos de the target country of a website.” But remarque the fourth row: the URL-parameter approach the brief pour ce topic parfois obtient décrit as a “gTLD + language param” option is, in Google’s propre framing, the chose to éviter. Don’t put the locale in a requête string.

A caveat on ccTLDs specifically: the automatic ranking benefit ils une fois carried is being phased bas (Gary Illyes has said as beaucoup — voir the hub pour the LDCP-fading discussion). ccTLD is encore the clearest country signal, but don’t treat it as a guaranteed ranking edge. My propre par défaut, elsewhere on ce site, is subdirectories pour la plupart sites — but the réel rule ici is decide une fois and appliquer it consistently, parce que inconsistency à travers signals is exactly ce que an audit plus tard has to untangle.

Step 2 — Implement hreflang correctement

Four choses, and alors hand off to the deep dives:

  • Self-reference. Chaque version’s hreflang définir devrait liste every version including itself. Google’s docs frame self-reference as partie of the standard instruction; Mueller has separately appelé it “optional” En pratique — so there’s réel tension entre the doc phrasing and his looser public statements. I inclure the self-reference parce que it’s cheap insurance and matches the documentation.
  • Retourner tags (reciprocity). Ce is the un que en réalité breaks sets. Google: “Si page X liens to page Y, page Y doit lien back to page X. Si ce n’est pas the cas pour tout pages que utiliser hreflang annotations, ceux annotations may be ignored or pas interpreted correctement.”
  • x-default. The fallback pour utilisateurs whose language/region vous don’t explicitly cover. Depth in x-default hreflang.
  • Valid ISO codes. Language codes (ISO 639-1) and optional region codes (ISO 3166-1 Alpha 2). en-uk is incorrect; it’s en-gb. Incorrect codes silently void the annotation.

Delivery méthode — pick un, be consistent. hreflang peut live in the HTML head, an HTTP header (pour non-HTML fichiers comme PDFs), or an XML sitemap. Google treats tout three as equivalent — there’s aucun speed or priority difference — so choisir fondé on votre stack. At scale, and surtout pour mixed ccTLD/subdirectory setups, the XML sitemap is usually the la plupart maintainable placer to manage it centrally. The complet tag mechanics live in hreflang.

Step 3 — Localize, don’t simplement translate

Un paragraph, parce que there’s a whole article on it. Machine-translating votre existing pages and shipping les unedited is the échec mode. Réel localization adapts currency, units, exemples, imagery, and product mix to the market — and souvent starts from market-specific keyword research plutôt que translating votre existing keywords. Deep dive: translation vs. localization. Checklist item: aucun unedited traduction automatique.

Step 4 — Geotargeting: ce que GSC peut and can’t do anymore

Ce is où a lot of publié checklists are simply out of date. The Google Search Console International Targeting report — the setting où vous pourrait manually point a subdirectory or subdomain at a country — was deprecated on September 22, 2022, and it’s gone pour every TLD type. Google’s notice: “The International Targeting report has been deprecated. Google va continuer to prise en charge and utiliser hreflang tags on votre pages.” The reason given: the country-targeting setting “was determined to have little valeur pour the ecosystem, and is ne … plus pris en charge.”

So the framing you’ll encore voir — “ccTLDs are automatic, but subdirectories and subdomains besoin the manual GSC setting” — describes how it used to work, pas a choice vous have today. Là is aucun manual country target anywhere in Search Console anymore. Google now infers geotargeting entirely from:

  • the ccTLD, si vous have un (encore automatic, encore the strongest signal);
  • hreflang annotations;
  • on-page signals — language of the visible content, currency, addresses, phone formats;
  • the locale of votre inbound liens.

The checklist item is therefore not “set your country in GSC.” It’s “assurez-vous votre ccTLD, hreflang, on-page signals, and lien locale tout agree,” parce que agreement is ce que Google reads now que there’s aucun override.

Step 5 — Faire switchers crawlable

Language and currency switchers have to be réel, crawlable hyperlinks — pas JavaScript-only dropdowns or client-side route changements with aucun réel href. Google’s propre guidance is explicit: “Considérer ajout hyperlinks to autre language versions of une page.” A switcher construit as JS state with aucun crawlable lien risks Google jamais discovering the alternate versions via que chemin. (Google fait render JS and fait explorer sans setting an Accept-Language header, but a mechanism with aucun réel <a href> is the fragile cas.)

And don’t force-redirect: “Éviter automatically redirecting utilisateurs from un language version of a site to a différent language version of a site.” Auto-redirecting by IP or navigateur language traps utilisateurs (and Googlebot, qui crawls from the US) in the incorrect version. Give everyone a visible, clickable chemin to every version and let les choisir. Ce is the même JS-rendering risk the audit article documents pour hreflang itself — même logic, applied to the switcher.

Step 6 — Handle near-contenu dupliqué à travers variants

Si vous serve near-identical content in the same language pour différent regions — the classic en-us / en-gb pages que are 95% the même — Google may treat les as duplicates. The fix is canonical and hreflang ensemble, per Google: “pick a preferred version and utiliser the rel="canonical" element and hreflang tags to assurez-vous que the correct language or regional URL is served to searchers.”

Evidence for this claim For similar same-language regional variants, Google recommends selecting a preferred version and using canonical plus hreflang; fully translated pages are a different case. Scope: international, multilingual and multi-regional websites and market research as applicable Confidence: high · Verified: Managing multi-regional and multilingual sites

The nuance que matters: canonical alone voudrait drop the regional version from indexation entirely — vous besoin les deux. And même fait correctement, Google may encore fold near-identical hreflang’d pages into un canonical and simplement swap l’URL affiché in the SERP (Mueller has confirmed ce pour cas comme fr-fr / fr-be). hreflang doesn’t guarantee separate indexation; it helps serve the correct existing version.

Step 7 — Validate avant and après launch

Garder ce short — the audit article has the complet methodology and the nine-error breakdown from my hreflang study. The pre/post-launch essentials:

  • Retourner tags présent on every pair (the la plupart courant functional break).
  • Valid language/region codes (ISO 639-1 / ISO 3166-1 Alpha 2).
  • Self-reference présent in chaque définir.
  • x-default présent.
  • Tags in the rendered <head>, pas injected mid-<body> by JS and pas ci-dessous the head où they’re invalid.
  • Vérifier the indexé URL per locale with GSC Inspection d’URL — confirmer Google en réalité indexé the version vous intended pour que market.

Bing-specific notes

Two choses diverge from Google:

  • Bing weights the Content-Language meta tag / HTTP header plus heavily que hreflang. Fabrice Canel of Bing has put it directement: “hreflang is indeed a far weaker signal que content-language at Bing.” Bing fait lire hreflang — simplement weakly — and rounds out its country understanding with ccTLD, server emplacement, body-text language, and inbound-link locale. Si Bing is a meaningful channel, définir content-language explicitly.
  • Bing’s propre Geo Targeting fonctionnalité apparaît to have been supprimé. The Geo Targeting contrôler in the old Bing Webmaster Outils was pas carried into the current UI. Bing’s public guidance now points to signaling geography via HTML meta tags / HTTP headers à la place. (I flag ce as reported-not-certain — voir the remarque sous the Quotes tab — parce que the principal source resists automated verification. Soit façon, don’t construire a checklist step autour a Bing dashboard setting; utiliser content-language and on-page signals.)

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.