IP-Based Redirects: Why Auto Country Redirects Hurt Crawling

IP-based redirects send Googlebot to whichever version matches the country its IP address seems to come from. The result? Your other country or language versions may never get crawled or indexed. So if your site has regional editions, pushes visitors to one of them based on IP, and some of those editions just aren’t showing up in Google, this is almost certainly why. Below: what goes wrong, how to confirm it, and what Google wants you to do instead.

Where does Googlebot crawl from?

Mostly the US. Googlebot’s default IP addresses appear to be based in the USA, according to Google’s guide to locale-adaptive pages. It does crawl from IPs outside the USA too, but the US ones are the default. And here’s the part people miss: its requests carry no Accept-Language header at all. A redirect keyed to browser language has nothing to go on. So for a site that redirects by country, the crawler looks like a US visitor most of the time. Simple as that.

How IP-based redirects hide your country versions

Send every US IP to the US or English version, and the crawler rarely (or never) reaches the rest. Google has a name for this setup: locale-adaptive pages, where the same URL returns different content depending on the country or language it assumes the visitor has. Google’s guidance on managing multi-regional sites warns that automatic redirects between language versions can stop both users and search engines from seeing all of them. What it usually looks like in practice:

• only one version of the site is indexed
• local editions are missing from local search results
• crawling never discovers the other versions
• hreflang alternates point to URLs the crawler can’t reach

Why you should not make an exception for Googlebot

Tempting, I know. Just whitelist the bot and move on, right? No. Showing Googlebot something different from what a user in the same country would see is cloaking, and it doesn’t fix anything anyway. Google’s rule is to treat the crawler like any other visitor from the country it appears to come from. That goes for blocks too: if US users are blocked, Googlebot on a US IP should be blocked as well. The actual fix is structural. Every version reachable from any IP, no special lane for the crawler.

Geo redirect SEO done right: what Google recommends instead

The short version: give each version its own URL, let people choose with a banner or a language switcher, and tie the versions together with hreflang. Step by step:

1. Give each country or language version its own URL.
2. Don’t force a redirect from any URL.
3. Show a banner suggesting the local version instead of redirecting.
4. Put a language switcher on every page.
5. Add hreflang annotations between equivalent pages.

ccTLDs, subdomains or subfolders? Weigh the pros and cons Google lists (there’s no universally right answer here). Our guide to country targeting site structures compares them side by side. One thing to keep in mind: a generic domain like .com has no built-in location. If you want it to target a country, you have to set that explicitly with one of the methods Google describes.

How to check whether redirect by country is blocking crawling

Easy test. Request each version’s URL from a US IP, with no Accept-Language header, and see what comes back. The version you asked for, or a redirect? Then go through this:

• the status code and redirect target of every version’s URL
• the URL Inspection result in Search Console for each version
• whether each hreflang alternate returns content without redirecting

Visitors (or your own tests) landing in the wrong country? Then your IP database may simply be wrong, and fixing wrong IP geolocation is a separate job. Either way, remove or soften the redirect rules in your origin or NGINX config and show a banner pointing to the local version instead.

Server location and IP addresses: what still matters

Where your site is served from is a different question from where you redirect visitors. And it doesn’t replace separate URLs and hreflang. Google notes that with ccTLDs the server location doesn’t matter, while subdomains and subfolders let each version run from a different server location. With Jalvo geotargeting you choose whether a site is served from EU or US IP addresses through its NGINX reverse proxy, and your visitors are never redirected. Running several language editions? Here’s how multilingual networks on EU IPs are set up.

Bottom line. IP-based redirects keep Googlebot, which crawls mostly from US addresses, away from every version except the one it gets pushed to. Crawlable URLs for each version, a banner or language switcher for visitors, and hreflang between equivalent pages. That’s what lets Google index all of them.

FAQ