The Complete Guide to SEO-Safe Geo Redirects

Geo redirects are the most common form of geo-targeting: send visitors from country A to page B. Simple in concept, but catastrophic for SEO if done wrong. This guide covers everything you need to know.

The golden rule: 302, never 301

A 301 redirect tells search engines “this page has permanently moved.” If you 301-redirect based on location, Google will eventually replace your original page in search results with the redirect target. Your main page disappears.

A 302 redirect says “this page is temporarily redirecting.” Google keeps your original page indexed and understands that different visitors might see different content. This is exactly what you want for geo-targeting.

GeoSwap exclusively uses 302 redirects for all geo-targeting. This is non-configurable by design — we won't let you shoot yourself in the foot.

How Googlebot interacts with geo-targeting

Googlebot crawls from data centers with IPs that don't map to a specific country in standard geo databases (MaxMind, IP2Location). This creates a natural safety mechanism:

• Explicit country rules: “If visitor is from Germany, redirect to /de” — Googlebot isn't from Germany, so it sees your default page and indexes it normally.
• Exclusion rules: “If visitor is NOT from the US, redirect to /international” — Googlebot's country is unknown (not US), so it matches this rule and gets redirected. Your US page may be de-indexed.

Cache-Control headers matter

If your server sends Cache-Control: public on geo-varying responses, CDNs and browsers may cache the redirected version and serve it to visitors from other countries. Always use:

Cache-Control: private, no-store

GeoSwap's Cloudflare Worker sets these headers automatically on every geo-targeted response.

Hreflang tags: the missing piece

Even with perfect 302 redirects, Google needs help understanding the relationship between your country-specific pages. That's where hreflang tags come in:

<link rel="alternate" hreflang="en-us" href="https://example.com/" />
<link rel="alternate" hreflang="de" href="https://example.com/de" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

GeoSwap auto-generates hreflang tags based on your redirect rules. When you create a redirect from the US to /us and from France to /fr, we automatically produce the correct hreflang markup. You can also use our hreflang generator to create them manually.

Common mistakes to avoid

1. Using 301 instead of 302: Permanent redirects cause page de-indexing.
2. Redirecting based on exclusion: “Not in X” rules catch Googlebot.
3. No hreflang tags: Google can't connect your regional pages without them.
4. Missing x-default: Always include an x-default hreflang for your fallback page.
5. GeoRedirect chains: US → /en → /en-us creates a redirect chain. Each hop loses link equity and slows page load.
6. Forgetting mobile: Test redirects on mobile devices too — some geo databases resolve mobile IPs differently.

Testing your setup

GeoSwap includes a built-in rule test simulator in the dashboard. Select a country, state, or city, and instantly see which redirect rule fires. The simulator flags SEO warnings for exclusion rules before you publish.

Geo redirects don't have to be scary. Use 302s, prefer explicit targeting, add hreflang tags, and test before publishing. For deeper guidance, read our SEO best practices guide and use the bot checker to verify that crawlers can access your content. Or just use GeoSwap — we handle all of this automatically.