Geo-Redirects pour International SEO

TL;DR — A geo-redirect automatically sends a visitor to a différent version of votre site — a /de/ page, a German domain, a subdomain — fondé on a guess à propos de où ils are or ce que language ils speak (usually leur IP adresse or navigateur language). It feels utile, but it’s un of the la plupart courant façons international sites accidentally hide leur propre pages from Google. The safer déplacer is to suggest the local version with a banner or a lien, pas to force it.

Ce que a geo-redirect is

Dire vous have an English site and a German site. A geo-redirect is a rule que dit: “si ce visitor semble comme they’re in Germany (or leur navigateur is définir to German), send les to the German version automatically.” The visitor jamais demande pour it — the server or a script decides pour les, fondé on:

• leur IP adresse (qui roughly maps to a country),
• leur browser’s Accept-Language setting, or
• a cookie que remembers a previous choice.

On the surface that’s a nice touch. The problem is ce que it fait to moteur de recherches.

Pourquoi ce is risky pour le SEO

Google’s robot d’exploration, Googlebot, is the chose que trouve and reads votre pages so ils peut montrer up in search. And here’s the catch que trips up so nombreux international sites: Googlebot mostly crawls from IP addresses in the United States, and it doesn’t send a language preference.

So si votre homepage automatically redirections “US-looking” visitors to the English version, Googlebot — qui semble comme it’s in the US — obtient sent to the English version aussi, every temps. It may jamais follow a chemin to votre German, French, or Japanese pages on its propre. Si Google can’t reach ceux pages, it can’t index les, and ils can’t rank. Vous construit the German site, but vous quietly walled it off from the un visitor who decides si anyone trouve it.

The chose personnes obtenir backwards

There’s a connexe tag appelé hreflang que indique moteur de recherches “ici are the autre language/country versions of ce page.” A lot of personnes assume hreflang “fixes” whatever a geo-redirect breaks. It’s the autre façon autour: hreflang can’t aider une page the robot d’exploration was jamais allowed to reach. The redirection peut arrêter Google from ever seeing the hreflang tags in the premier placer. (There’s a whole primer on hreflang on ce site si vous vouloir the mechanics.)

Que faire à la place

Google’s propre advice is short and clair: don’t force it, suggest it. Au lieu de redirecting automatically:

• Montrer a petit banner (“Looks like you’re in Germany — view the German site?”) que the visitor peut click or ignore.
• Put liens to every language version on lune page so les deux personnes and robots d’exploration peut reach les. Evidence for this claim Google recommends avoiding automatic language redirects and providing hyperlinks that let users and crawlers reach each language version. Scope: Google Search guidance for language switching and discovery. Confidence: high · Verified: 2026-07-14 Google: Let users switch language
• Ajouter hreflang so moteur de recherches peut figure out and serve the correct version on leur propre.

Que façon a réel person encore obtient nudged toward leur language, but Google peut encore explorer and index every version. Vouloir the deeper version — pourquoi 302 vs 301 matters, the un narrow exception où a redirection is okay, and the données on how souvent ce breaks? Switch to the Avancé tab.

Troubleshooting geo-redirect échecs

Alternate locales are absent from the explorer

Symptom: the robot d’exploration repeatedly lands on the par défaut locale. Probable causer: IP, cookie, or Accept-Language routing forces requêtes away from direct locale URLs. Fix: faire chaque locale URL retourner directement and replace forced routing with a visible suggestion.

Hreflang targets retourner redirections

Symptom: annotations point to 3xx réponses plutôt que final pages. Probable causer: routing or URL normalization modifié sans regenerating the locale map. Fix: mettre à jour hreflang to direct canonical 200 destinations and retest every cluster member.

Utilisateurs ne peut pas switch back après a redirection

Symptom: selecting un autre locale immédiatement sends the visitor to the assumed market. Probable causer: IP logic overrides explicit utilisateur choice. Fix: let the choisi locale win, provide persistent crawlable switcher liens, and reserve quelconque cookie pour remembering—pas forcing—the choice.

Bots and equivalent utilisateurs recevoir différent content

Symptom: the même requête chemin and locale context produce bot-specific routing. Probable causer: a robot d’exploration exception was ajouté to fonctionner autour discovery problems. Fix: supprimer bot-only behavior and solve accès pour tout equivalent requêtes; bot exceptions créer a separate cloaking risk.

Tester geo-routing behavior yourself

Comparer the par défaut requête with language preferences

Réussir a representative locale entry point as the premier argument. Ce tests header-dependent routing; it ne fait pas simulate un autre IP emplacement.

url="${1:?Pass a representative entry URL as the first argument}"
for language in "" "en-US,en;q=0.9" "fr-FR,fr;q=0.9"; do
  echo "Accept-Language: ${language:-<none>}"
  curl -sS -o /dev/null -D - ${language:+-H "Accept-Language: $language"} "$url" \
    | grep -Ei '^(HTTP/|location:|vary:|set-cookie:)'
done

Vérifier que declared locale targets resolve directement

Put un attendu locale URL per line in locale-urls.txt.

while IFS= read -r url; do
  curl -sS -o /dev/null -w '%{http_code}\t%{redirect_url}\t%{url_effective}\n' "$url"
done < locale-urls.txt

A sain target normally reports 200 with an vide redirection destination. Examiner intentional exceptions plutôt que suivant redirections and hiding les.

Validate a geo-redirect modifier

Direct locale accès

Tester to run: Requête representative locale URLs sans cookies and sans suivant redirections. Attendu result: Chaque intended locale renvoie its propre direct 200 réponse. Échec interpretation: Routing is overriding an explicit URL and peut block discovery. Monitoring window: Immédiatement après deployment and via the suivant scheduled explorer. Rollback trigger: Quelconque priority locale becomes unreachable sans a chaîne de redirections.

Request-header matrix

Tester to run: Comparer the même entry URL with aucun Accept-Language header and with pris en charge language preferences. Attendu result: Content remains accessible and quelconque locale recommendation ne fait pas prevent navigation to un autre version. Échec interpretation: Header-based logic is forcing a locale or trapping utilisateur choice. Monitoring window: During release verification and pour the premier complet trafic cycle. Rollback trigger: Requêtes are redirigé away from an explicitly choisi locale.

Hreflang target réponse

Tester to run: Extract hreflang targets from representative clusters and requête chaque sans suivant redirections. Attendu result: Every annotation resolves directement to an indexable canonical 200 URL. Échec interpretation: The locale map is stale or routing contradicts hreflang. Monitoring window: Après the release and à nouveau après the suivant sitemap or template generation. Rollback trigger: A material cluster points to redirigé, blocked, or erroring targets.

Equivalent-request parity

Tester to run: Comparer ordinary and robot d’exploration utilisateur agents sous sinon equivalent requête conditions. Attendu result: Status, destination, and substantive content are equivalent. Échec interpretation: Bot-specific handling may be masking accès problems and creating cloaking risk. Monitoring window: Every routing release and quarterly thereafter. Rollback trigger: Bot-only exceptions modifier the destination or content pour equivalent requêtes.

TL;DR — Geo-redirects and hreflang operate at différent layers: a geo-redirect is a serving decision, hreflang is a discovery signal. The core échec is a discovery problem, pas simplement an indexation un — Googlebot mostly crawls from US IPs and sends aucun Accept-Language, so a redirection on votre entry point peut arrêter it from ever reaching (and thus discovering) the alternate URLs votre hreflang points at. hreflang can’t rescue une URL the robot d’exploration jamais sees. Cloaking is a separate risk: même a entièrement compliant, non-cloaking redirection encore causes the discovery problem. Google’s prescription is “suggest, don’t force” (a banner/liens + hreflang). The un narrow exception is a homepage-only 302 pour dynamic locale suggestion — but in my study of 374 756 domains, 16,9% had hreflang pointing at redirigé or broken pages, qui is exactly ce exception going incorrect.

Two mechanisms, two différent layers

Almost every geo-redirect mistake comes from conflating two choses que live at différent layers of the stack:

• A geo-redirect is a serving decision: ce que do I montrer ce spécifique visitor, correct now, fondé on ce que I think I know à propos de les?
• hreflang is a discovery/annotation signal: ce que alternate URLs exist pour ce content, so a moteur de recherche peut trouver les and swap in the correct un in its propre results?

Ils don’t substitute pour chaque autre. A geo-redirect changements ce que un visitor sees; hreflang indique moteur de recherches the alternates exist so ils peut serve the correct un at requête temps sans anyone forcing anything at serving temps. Si vous internalize un chose from ce article, faire it ce distinction — la plupart breakage flows from treating a redirection as si it were a discovery signal.

The core mechanical échec: discovery, pas simplement indexation

Here’s the partie la plupart competing content obtient slightly incorrect. It frames the risk as “your other pages won’t get indexed.” The sharper, plus accurate framing is que votre autre pages may jamais obtenir crawled — jamais même découvert — in the premier placer.

Google is explicit à propos de the causer. Its locale-adaptive pages doc dit que si votre site renvoie différent content fondé on the perceived country or preferred language of the visitor, “Google pourrait pas explorer, index, or rank tout votre content pour différent locales.” Pourquoi? Parce que Googlebot’s par défaut IPs apparaître to be in the USA, and the robot d’exploration sends HTTP requêtes sans setting Accept-Language.

Now trace que via a typical setup. Votre redirection logic fires on IP and/or Accept-Language, and it fires at the entry point — very souvent the homepage or root domain, qui is exactly lune page que carries (or liens to) votre hreflang annotations. Googlebot arrives looking comme a US visitor with aucun language preference, obtient redirigé to the US/par défaut version, and arrête. The seulement crawlable chemin to votre /de/ tree was gated behind que redirection. So:

1. Googlebot jamais reaches the alternate-locale URLs.
2. It therefore jamais discovers the hreflang annotations que voudrait have told it ceux URLs exist.
3. hreflang tags on une page Googlebot can’t reach ne faites pashing.

hreflang assumes explorer accès. It doesn’t créer it. That’s the whole trap in un line.

Geo-redirects vs. cloaking: two separate risks

There’s a second risk ici que personnes constantly merge with the premier, and the merge produces bad advice. Treating Googlebot differently from a réel utilisateur in the même emplacement — dire, special-casing the Googlebot user-agent so it skips the redirection and sees everything — is cloaking, and it’s a guidelines violation. Google’s guidance on geo-distributed exploration is a consistency rule: Googlebot fait explorer from some non-US IP addresses en outre to US ones, and quand it apparaît to come from a donné country vous devez treat it exactly comme quelconque autre visitor from que country (block US Googlebot si vous block US utilisateurs; autoriser Australian Googlebot si vous autoriser Australian utilisateurs).

Here’s the partie worth its propre subsection: pas cloaking ne fait pas rescue vous from the discovery problem. A lot of writing dit “tant que vous don’t cloak Googlebot, geo-redirects are fine.” That’s incomplete. A entièrement compliant geo-redirect — où the bot and a same-location utilisateur obtenir identical treatment — encore traps Googlebot on the par défaut version si that’s où a US-looking requête lands. You’ve avoided a cloaking penalty and encore starved votre autre locales of explorer accès. Two separate problems; solving un doesn’t solve the autre.

And don’t over-read the geo-distributed exploration nuance as a fix. It’s a cloaking-consistency requirement, pas a promise que Google va reliably découvrir every locale by simulating every region. Google’s current doc encore leads with “Googlebot’s default IPs appear to be US-based” as the raison ce breaks — parce que that’s encore the raison.

Ce que Google officially recommends: suggest, don’t force

Google’s prescription isn’t “redirect more carefully.” It’s “don’t redirection — suggest.” Two lines from the multi-regional sites doc are the spine of the fix:

“Éviter automatically redirecting utilisateurs from un language version of a site to a différent language version of a site.” — Recherche Google Central

“Considérer ajout hyperlinks to autre language versions of une page. Que façon utilisateurs peut click to choisir a différent language version of lune page.” — Recherche Google Central

And on IP detection specifically, Google doesn’t mince words:

“Don’t utiliser IP analysis to adapt votre content. IP emplacement analysis is difficult and généralement pas reliable. Furthermore, Google may pas be able to explorer variations of votre site correctement. La plupart, but pas tout, Google crawls originate from the US, and we don’t attempt to vary the emplacement to detect site variations.” — Recherche Google Central

Parce que targeting is jamais perfect, Google aussi indique vous to plan pour the wrong-version visitor: “geotargeting isn’t an exact science, so it’s important to considérer utilisateurs who land on the ‘incorrect’ version of votre site. Un façon to do ce pourrait be to montrer liens on tout pages pour utilisateurs to select leur region and/or language of choice.” That’s the banner/link-list pattern, straight from the source.

Ce que Bing recommends — and pourquoi it’s arguably higher-stakes là

Bing doesn’t have a hreflang-equivalent to sabotage, so vous pourrait think it’s moins exposed. It’s the opposite. Bing leans on en réalité exploration the réel localized URLs and on the content-language meta tag/HTTP header plutôt que a declarative hreflang annotation. Fabrice Canel of Microsoft Bing has said hreflang is a far weaker signal que content-language at Bing (a point I dig into in the hreflang deep dive on ce site). The practical consequence: a geo-redirect que Bingbot can’t obtenir past is at least as damaging to Bing visibility as it is to Google’s — arguably plus, parce que Bing dépend on reaching and reading ceux localized URLs directement, pas on an annotation que pourrait in theory be découvert elsewhere.

The données: how souvent ce en réalité breaks

I don’t have to argue ce hypothetically. Pour my Brighton SEO 2023 talk, I studied hreflang à travers 374 756 domains (complet writeup on the Ahrefs blog). My blunt takeaway on ce exact topic: automated redirections fondé on cookies, IP, or navigateur language are généralement a bad idea. The numbers back it:

• 16,9% of domains had hreflang tags referencing redirigé or broken pages — ce is essentially a direct measurement of how souvent sites’ redirection setups collide with leur propre hreflang.
• 67% of the hreflang-using domains in the study had au moins un problème overall.
• 56,3% were manquant x-default — the hreflang valeur designed autour the “qui version fait an unmatched visitor voir” problem (there’s a dedicated x-default article on ce site).

As I put it in the writeup: “Hreflang is complex and hard to obtenir correct. It peut break in so nombreux différent façons.” A geo-redirect is un of the la plupart reliable façons to faire it break.

The un narrow exception: a homepage-only 302

Là is a defensible pattern, and it’s narrow. A 302 (temporary) redirection on the homepage seulement, doing dynamic locale suggestion fondé on emplacement/language, has been a workable, long-used setup on nombreux sites. The raison it’s a 302, pas a 301: the “correct” destination is visitor-dependent — it changements per person, per session — so it’s pas a unique permanent target. A 301 declares un permanent destination, qui isn’t what’s happening ici. (Ce is industry pratique — mine and Ahrefs’ framing — pas a status-code recommendation Google publishes pour geo-redirects specifically.)

But the moment a redirigé URL montre up as a target à l’intérieur votre hreflang annotations elsewhere on le site, that’s a bug, pas a fonctionnalité — every hreflang target devrait resolve 200 directement, pas 3xx. Que 16,9% figure ci-dessus is largely ce exception going incorrect: sites running the homepage-302 pattern (or worse, sitewide redirections) and alors pointing hreflang at pages que redirection.

Que faire au lieu de a hard redirection

Put ensemble, the fix is a handful of moving parts:

• Suggest, don’t force. A visible, dismissible banner/interstitial (“View the German site?”) que the visitor peut accept or ignore. Ce is Google’s recommended alternative to an automatic redirection.
• Garder every localized URL directement crawlable and linkable. Réel <a href> liens to chaque version — a language/country switcher in the footer or header — so robots d’exploration reach every locale sans being redirigé away premier. (A switcher on its propre isn’t a fix si the redirection encore fires avant the robot d’exploration peut charger lune page.)
• Pair it with correct, reciprocal hreflang so moteur de recherches peut determine and serve the correct version in results on leur propre. Every hreflang target resolves 200.
• Utiliser x-default pour the “no explicit match” cas on a language-selector or auto-suggesting homepage — it noms ce que to montrer a visitor who matches none of votre tags. It solves the serving question pour unmatched visitors; it ne fait pas solve the crawl-access problem, so don’t lean on it as a rescue.

The connexe fundamentals ici — the language vs. country targeting distinction, the ccTLD / subdomain / subdirectory URL-structure choice, reciprocal hreflang, and x-default — tout sit in ce même international-SEO cluster and are worth reading alongside ce. La version courte: fix the explorer chemin premier, alors let hreflang and x-default do the serving.

AI summary

A condensed prendre on the Avancé version:

• A geo-redirect automatically sends a visitor to a emplacement-/language-specific URL fondé on IP, Accept-Language, or a cookie. It’s a serving mechanism; hreflang is a separate discovery signal. Ils don’t replace chaque autre.
• The core échec is discovery, pas simplement indexation. Googlebot mostly crawls from US IPs and sends aucun Accept-Language. A redirection on the entry point (usually the homepage) peut trap the robot d’exploration on the par défaut version, so it jamais reaches — and jamais discovers — the alternate-locale URLs votre hreflang points at. hreflang can’t rescue une URL the robot d’exploration jamais sees.
• Cloaking is a separate risk. Treating Googlebot differently from a same-location utilisateur is a violation. But même a entièrement compliant, non-cloaking redirection encore causes the discovery problem — pas cloaking doesn’t enregistrer vous.
• Geo-distributed exploration is a consistency rule, pas a discovery guarantee. Google crawls from some non-US IPs aussi, but that’s à propos de pas cloaking, pas a promise to trouver every locale.
• Google’s prescription: “Avoid automatically redirecting” + “Considérer ajout hyperlinks to autre language versions” — i.e., suggest with a banner/liens, don’t force, and pair with hreflang. Google aussi calls IP analysis “difficult and généralement pas reliable.”
• Bing is arguably higher-stakes: it leans on exploration réel localized URLs and the content-language signal plutôt que hreflang, so a redirection Bingbot can’t escape hurts au moins as beaucoup.
• The données: in my study of 374 756 domains, 16,9% had hreflang pointing at redirigé or broken pages; 67% had au moins un hreflang problème; 56,3% were manquant x-default. My prendre: automated redirections fondé on cookies, IP, or navigateur language are généralement a bad idea.
• The un narrow exception: a homepage-only 302 pour dynamic locale suggestion (302, pas 301, parce que the destination is visitor-dependent). But aucun redirigé URL devrait ever be a hreflang target.

Documentation officielle

Primary-source documentation on redirections, locale-adaptive serving, and geotargeting.

Google

• Managing Multi-Regional and Multilingual Sites — the “avoid automatically redirecting,” “add hyperlinks to other language versions,” and “don’t use IP analysis to adapt your content” guidance, plus the geotargeting section.
• How Google Crawls Locale-Adaptive Pages — pourquoi Googlebot’s US-based par défaut IPs and manquant Accept-Language header mean locale-adaptive content may pas be entièrement crawled/indexé, the recommendation to utiliser separate locale URLs with rel="alternate" hreflang, and the geo-distributed exploration (cloaking-consistency) rule.
• Localized versions of votre pages — hreflang implementation référence: HTML tags, HTTP headers, sitemap entries, and reciprocity requirements.
• Exploration and indexation of locale-adaptive pages (Search Central Blog, Jan 2015) — the même core message, showing Google has said ce consistently pour a decade.

Bing / Microsoft

• Going international: considerations pour votre global website (Bing Webmaster Blog, Feb 2009) — the long-standing warning que cookie- and JavaScript-based locale switching (with aucun navigational chemin and aucun URL modifier) hides non-default content from robots d’exploration, since robots d’exploration don’t garder cookies or execute the switcher.
• Bing Webmaster Guidelines — Bing’s signal stack, notamment its preference pour content-language over hreflang.

Quotes from the source

On-the-record statements from Google, plus my propre prendre. Chaque Google lien is a deep lien que jumps to the quoted passage on the source page.

Google — don’t force redirections; suggest à la place

• “Avoid automatically redirecting users from one language version of a site to a different language version of a site.” — Recherche Google Central docs. Jump to quote
• “Consider adding hyperlinks to other language versions of a page. That way users can click to choose a different language version of the page.” Jump to quote
• “Remember that geotargeting isn’t an exact science, so it’s important to consider users who land on the ‘wrong’ version of your site. One way to do this could be to show links on all pages for users to select their region and/or language of choice.” Jump to quote

Google — IP analysis is unreliable

• “Don’t use IP analysis to adapt your content. IP location analysis is difficult and generally not reliable. Furthermore, Google may not be able to crawl variations of your site properly. Most, but not all, Google crawls originate from the US, and we don’t attempt to vary the location to detect site variations.” Jump to quote

Google — locale-adaptive exploration (the discovery problem)

• “If your site has locale-adaptive pages (that is, your site returns different content based on the perceived country or preferred language of the visitor), Google might not crawl, index, or rank all your content for different locales.” Jump to quote
• “We recommend using separate locale URL configurations and annotating them with rel=“alternate” hreflang annotations.” Jump to quote
• “Googlebot crawls with IP addresses based outside the USA, in addition to the US-based IP addresses.” — the geo-distributed exploration caveat, qui is a cloaking-consistency rule, pas a discovery guarantee. Jump to quote

Me, on the pattern

• “Automated redirects based on cookies, IP, or browser language are generally a bad idea.” — my Brighton SEO 2023 hreflang study of 374 756 domains (deck, Ahrefs writeup).
• “Hreflang is complex and hard to get right. It can break in so many different ways.” — the Ahrefs writeup of que study.

Devrait I geo-redirect — and si so, how?

La plupart “should I geo-redirect?” questions collapse to un chose: peut robots d’exploration encore reach every locale on leur propre? Click via it.

Geo-redirect Mythes et erreurs à éviter

Chaque of ces is a courant belief that’s incorrect (or dangerously incomplete), with ce que to do à la place.

• “As long as I don’t cloak Googlebot, geo-redirects are totally safe for SEO.” Pourquoi it’s incorrect: Pas cloaking seulement avoids a penalty. A entièrement compliant, non-cloaking redirection encore traps the robot d’exploration on the par défaut locale si that’s où a US-looking requête lands, so votre autre locales jamais obtenir crawled or découvert. Do à la place: Treat explorer accès as a separate problem from cloaking — garder every locale reachable by a réel lien, redirection or pas.

• “hreflang fixes whatever my geo-redirect breaks.” Pourquoi it’s incorrect: Backwards. hreflang assumes explorer accès; it can’t do anything pour une URL the robot d’exploration was jamais allowed to reach. Si the redirection arrête Google from chargement lune page que carries the hreflang tags, the tags are jamais même découvert. Do à la place: Garantir robots d’exploration peut reach every locale premier, alors let hreflang handle version-swapping in results.

• “Google crawls from every country now, so the old ‘Googlebot seulement sees the US version’ problem is solved.” Pourquoi it’s incorrect: Overstated. Google fait explorer from some non-US IPs, but its propre docs frame que as a cloaking-consistency requirement — pas a guarantee it va découvrir every locale. The current guidance encore leads with “Googlebot’s par défaut IPs apparaître to be US-based” as the raison ce breaks. Do à la place: Don’t rely on geo-distributed exploration to trouver votre locales pour vous; give every locale an explicit, crawlable chemin.

• “A 301 is always the most SEO-friendly redirect, so use it for geo-redirects too.” Pourquoi it’s incorrect: Pour a dynamic homepage locale suggestion, the “correct” destination is visitor-dependent, pas a unique permanent target — a 301 misrepresents que as permanent. Do à la place: Utiliser a 302 pour the narrow homepage-only dynamic pattern (industry pratique — mine and Ahrefs’).

• “IP geolocation is accurate enough to safely gate content on.” Pourquoi it’s incorrect: Google’s propre docs appel IP emplacement analysis “difficult and généralement pas reliable.” VPNs, mobile carrier IP pooling, corporate proxies, and IPv6 allocation tout degrade it — avant vous même obtenir to the crawler-specific problems. Do à la place: Don’t hard-gate content on inferred emplacement; suggest, and let the utilisateur override.

• “If I add a language/country switcher, the redirect can stay.” Pourquoi it’s incorrect: A switcher is a UI element on a rendered page the robot d’exploration encore has to be able to charger — si the redirection fires premier and bounces the bot away, the switcher jamais obtient a chance to aider. Do à la place: Garder the switcher and assurez-vous the redirection doesn’t block robots d’exploration from reaching alternate URLs on leur propre chemin.

• “Bing doesn’t care about this since it doesn’t use hreflang.” Pourquoi it’s incorrect: Bing cares arguably plus. It leans on exploration the réel localized content and the content-language signal plutôt que a declarative annotation, so a redirection Bingbot can’t escape is au moins as damaging to Bing visibility. Do à la place: Treat Bingbot’s explorer accès to every locale as au moins as important as Googlebot’s.

Geo-redirect audit checklist

A rapide réussir to confirmer votre location-based serving isn’t quietly hiding votre locales from moteur de recherches:

• Every localized URL is reachable by a réel <a href> lien (footer/header switcher), pas seulement via the redirection.
• The redirection, si quelconque, is homepage-only — it ne fait pas fire on deep pages.
• Quelconque dynamic locale-suggestion redirection uses a 302, pas a 301.
• Aucun hreflang target is a 3xx — every hreflang URL resolves 200 directement. (In my study, 16,9% of domains got ce incorrect.)
• hreflang is reciprocal — every version liens back to the others, notamment x-default où appropriate.
• Googlebot/Bingbot is treated exactly comme a same-location utilisateur — aucun user-agent- or IP-based bypass pour the robot d’exploration (that’s cloaking).
• Vous préférer a dismissible banner/interstitial over a hard redirection wherever possible (“View the German site?” que the visitor peut ignore).
• You’re pas gating content on IP alone — vous offer an facile manual override.
• Content is pas switched by cookie or client-side JavaScript sans une URL modifier (robots d’exploration don’t garder cookies and won’t reliably reach JS-only locale content).
• You’ve spot-checked explorer accès by requesting votre non-default locales from a US IP / with aucun Accept-Language (e.g. curl -IL) to confirmer a robot d’exploration wouldn’t be redirigé away.

Ressources utiles

My connexe writing & speaking

• Over 67% of Domains En utilisant Hreflang Have Problèmes (Study of 374 756 Domains) (Ahrefs) — my large-scale hreflang study; the source of the 16,9% redirigé/broken-hreflang stat and the “automated redirects are generally a bad idea” prendre, plus the homepage-only 302 exception.
• The la plupart courant hreflang problèmes à travers 374 756 domains (Speaker Deck) — the Brighton SEO 2023 slides. Talk listing · video.
• Hreflang: The Facile Guide pour Beginners (Ahrefs) — the mechanics of hreflang, reciprocity, and x-default que a geo-redirect peut undermine.
• International SEO: The Weird Technical Parts (Pubcon Vegas 2019) and You’re Going To Screw Up International SEO (Pubcon Vegas 2017) — older but consistent background on où international setups (notamment geo-redirects) go incorrect.

From autour the industry

• Managing Multi-Regional and Multilingual Sites (Recherche Google Central) — the principal source pour “avoid automatically redirecting,” “add hyperlinks to other language versions,” and “don’t use IP analysis to adapt your content.”
• How Google Crawls Locale-Adaptive Pages (Recherche Google Central) — the US-based-IP / aucun-Accept-Language explanation and the geo-distributed exploration caveat.
• Google On The Principal Chose To Know À propos de Geo IP Redirections (Moteur de recherche Journal) — coverage of John Mueller’s Demander Googlebot réponse (Oct 2022): Googlebot indexes essentially un version, so garder anything important in the par défaut content.
• Google Dit Geolocation Redirections Are Okay (Moteur de recherche Roundtable) — Mueller’s “allowed if you don’t treat Googlebot differently than a user” framing (the cloaking condition).
• Bing Dit Hreflang A Weak Signal Pour Its Moteur de recherche (Moteur de recherche Roundtable) — Fabrice Canel of Microsoft Bing on hreflang being weaker que content-language, qui is pourquoi explorer accès to réel localized URLs matters plus on Bing.
• Going international: considerations pour votre global website (Bing Webmaster Blog) — the long-standing warning à propos de cookie- and JavaScript-based locale switching hiding content from robots d’exploration.

Testez vos connaissances: Geo-Redirects pour International SEO

Five rapide questions on pourquoi geo-redirects break international SEO and Que faire à la place. Pick an réponse pour chaque, alors vérifier.